Summary: | Request for addition to /sbin/functions.sh to make it possible to set the softlevel during execution of the boot runlevel | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Aspeli <optilude> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Aspeli
2003-12-22 16:59:42 UTC
I had another look and noticed I could set the runlevel to be started after boot by putting its name in /var/init.d/ksoftlevel. I created another 'boot' runlevel service which determines the correct runlevel, and writes the name of this to /var/init.d/ksoftlevel (effectively overwriting the value of ${DEFAULTLEVEL} from setup_defaultlevels(), which is stored in that file when /sbin/rc is called with the 'boot' option). This appears to work, but is it safe? Or is it simply a side-effect of the current implementation of /sbin/rc (which seems to use /var/init.d/ksoftlevel as a temporary store for the ${DEFAULTLEVEL} variable). Or put differently, is ksoftlevel intended to be used in this way? If not, why not? I also discovered that the simple modification requested above probably wouldn't work, because the setup_defaultlevels() function is only called when the 'boot' runlevel is first entered, so any modification that depends on services started during 'boot' would not have a chance to affect it. tracing old bugs here. i'm pretty certain this functionality is present in the system now, since you filed this bug in 2003. if not, please reopen. |