Re: privilege that rc.local runs under?

[Justin Honold <jhonold@bigfoot.com>]

Matt Van Mater wrote:

> Most documentation including the faq recommend that you build, install 
> and actually be running a new kernel before trying to build, install and 
> run the new system.

i don't believe it's necessary - just that it's more of a precautionary 
measure when doing an interactive build.  if the kernel doesn't compile 
or work to your liking, you can then boot the old one.

> I was planning on making a new kernel, rebooting 
> with it, and then continuing with the make, build, install of the system 
> automatically upon reboot without having to call some 'make system' 
> script by hand.  My solution is to insert a few lines in rc.local that 
> run after a new kernel is installed and rebooted, and delete the 
> temporary lines when completed.

since you're not doing this interactively, i fail to see the point in 
booting to the new kernel before completing the build.  as for deleting 
the temporary lines, you can use cp instead of sed.

> The difference between our implementations is that using mine means that 
> if you get to the point where you run crunch, you know you have a 
> working build (since you are operating under that build), where you are 
> trusting that as long as everything compiles then the system should work 
> ok.  Neither method is a good way of testing that the build worked 
> flawlessly, but oh well :)

the safety in my method is that i manually reboot and evaluate the 
system before issuing the updates to other systems.