local.start is not executed

[Corpse2]

I have a strange problem after I installed gentoo (stage 3 from universal liveCD)

I first had a problem with emerging packages, but I found on the forums that my use flags were not exported. After exporting the use flags, emerge worked.

I don't know why they are not exported at boottime, but this is not so much of a problem, at least that's what I thought.

I wanted to add the line to local.start which would solve my problem, but it appears that everything in local.start is not executed when the computer is booting.

I have the export and some aliases in there, but after booting the computer, I have to maually source the file:

Code: Select all

source /etc/conf.d/local.start

When looking into this problem, I checked if local was in the default runlevel.
Local is in the default runlevel, during boot I see "Starting local ... [OK]" and /etc/init.d/local contains the line to source local.start.

Searching the forums about problems with local.start allways seem to return 0 results (search for local.start, local, start, ...) like if these words are reserved.

So, how come local.start is not sourced and how to fix it?
Any info on the use flag exporting is also appreciated.

[TheKreep]

I have the same problem, and I'd also appreciate any help.

[NTT]

local.start is not meant for setting variables, any exports are valid for the duration of the local.start script. Ik you want to set environment variables for your profile put them in ~/.bash_profile or systemwide in /etc/profile.

[Cocker68]

1. Check, if local.start indeed won't be executed:
   Put something like this line

   Code: Select all

   echo "`/bin/date` local.start executed" >> /tmp/local.start.test

   into Your local.start-file. Then reboot, and check the test-file /tmp/local.start.test
2. I don't think local.start is the right place for what You want to do.
   
   Globally valid use-flags live in /etc/make.conf, packet-specific ones live in /etc/portage/package.use
   Aliases' best place is most probably in the user's (root's in Your case) .bashrc-file.

- Cocker :wq

[Corpse2]

1. Check, if local.start indeed won't be executed:
   Put something like this line

   Code: Select all

   echo "`/bin/date` local.start executed" >> /tmp/local.start.test

   into Your local.start-file. Then reboot, and check the test-file /tmp/local.start.test
2. I don't think local.start is the right place for what You want to do.
   
   Globally valid use-flags live in /etc/make.conf, packet-specific ones live in /etc/portage/package.use
   Aliases' best place is most probably in the user's (root's in Your case) .bashrc-file.

- Cocker :wq

the use flags are in make.conf, but only after I do

Code: Select all

export USE="gtk -qt ..."

I am able to emerge stuff. Otherwise I get

Code: Select all

C compiler cannot create executables

I will put them in /etc/profile as well.

I will check the local.start test immediately

[Corpse2]

hmm, it appears local.start is executed indeed, but commands like export and alias are not. If I put some service in there to start, it starts.

Anyone an idea why export and alias don't work here anymore? It used to work in the 2004.x ages, even though it does not belong there...

[Headrush]

local.start is not meant for setting variables, any exports are valid for the duration of the local.start script. Ik you want to set environment variables for your profile put them in ~/.bash_profile or systemwide in /etc/profile.

Or for system-wide stuff, check out the files in /etc/env.d/ directory for simple examples.

Don't forget to do an env-update and source /etc/profile if you add your own file.

[nixnut]

Moved from Installing Gentoo to Other Things Gentoo.
Not an installing gentoo problem.