<quote>randominternet: ask yourself if you really need runlevels?</quote>
There are two basic runlevel controls in the Unix/Linux world, the System V way, and BSD way. They both have there own pros and cons, and I am not going to debate them here. The way init scripts and run levels work is well defined. It is even part of the Linux Standards Base, which defines how Linux distributions are supposed to work for 3rd party vendors, application developers, etc. Take a good look at http://refspecs.linux-foundation.org/LSB_3.2.0/LSB-Core-generic/LSB- Core-generic/tocsysinit.html and http://refspecs.linux- foundation.org/LSB_3.2.0/LSB-Core-generic/LSB-Core- generic/runlevels.html. If there are no separate runlevels, then standardization has been thrown out the window. <quote>randominternet: you can easily add a "grep /proc/cmdline trigger" into an if statement to control any rc script</quote> The end user shouldn't have to do this. With the "BSD way" everything could be thrown into one directory (as opposed to rc1.d, rc2.d, etc.) or it could be just 1 central rc script. However, there is still a separation of runlevels and controlling what each runlevel does. -- Fail to enter rc1.d by putting 1 in bootparam in edgy https://bugs.launchpad.net/bugs/85014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
