Tiny Core Linux

Tiny Core Extensions => TCE Bugs => Topic started by: qopit on January 24, 2015, 09:26:06 PM

Title: linux-kernel-sources-env hard-coded for tc:staff
Post by: qopit on January 24, 2015, 09:26:06 PM
linux-kernel-sources-env.sh is hard coded for user `tc` and group `staff`.

If the `user=` or `host=` boot params have been set, the script does not work (although usage of sudo will get you the readable files).
Title: Re: linux-kernel-sources-env hard-coded for tc:staff
Post by: coreplayer2 on January 24, 2015, 09:34:22 PM
H'mmm interesting..

ok thanks for pointing that out, should be a quick fix.  I can understand user= but host= ??
Title: Re: linux-kernel-sources-env hard-coded for tc:staff
Post by: qopit on January 25, 2015, 09:29:46 PM
Not sure what I was thinking.  It is definitely just user.  Forget host.  Switching tc to $USER is all that is needed, as you say.

I just needed to do it for Corepure64 which seems to differ from the other script(s) in that it disallowed running as root (my earlier workaround).
Title: Re: linux-kernel-sources-env hard-coded for tc:staff
Post by: coreplayer2 on January 26, 2015, 02:27:11 AM
There is a new version uploaded to the repo today which is now compatible with tc6 corepure64 and x86, although this issue has not been addressed you might try the updated version in the meantime and perhaps not receive the error..?
Title: Re: linux-kernel-sources-env hard-coded for tc:staff
Post by: qopit on January 29, 2015, 09:50:08 PM
Sorry for the delay in responding... I didn't have notify on for this thread.

The problem definitely still exists in the new version.  Not a big deal.  I just run this before executing the script and all is well:

Code: [Select]
sudo sed -i "s|tc.staff|\$USER:staff|" `which linux-kernel-sources-env.sh`

Note that the script uses both `tc.staff` and `tc:staff` notation on chown.  I didn't even know you could spec with `tc.staff`.  I always use `tc:staff` form.
Title: Re: linux-kernel-sources-env hard-coded for tc:staff
Post by: coreplayer2 on January 30, 2015, 03:57:43 AM
Ok I see the issue now.  I'll fix that ASAP, thanks.  But I'm curious why not try booting without the user=  boot-code  as a temporary measure, would it have saved you all the inconvenience of writing a one-liner script to accomplish the same thing?

Will advise when updated


Sent from my iPad using Tapatalk HD