>Though I doubt we'd be able to convince core Debian to pick up our >init and rc system, I'd recommend having a look at the way that it >works. We designed it based on having used all the other systems and >deciding they weren't what we needed. Like the System V rc system, >there is a separate script for each facility, but unlike System V, >there is no arbitrary numbering to handle the ordering.
There is a debian package called file-rc, which replaces the rc?.d directories by one plain text config file (/etc/runlevel.conf) these are the first lines of /etc/runlevel.conf # This file was automatically generated by /usr/lib/file-rc/rclink2file.sh. You # can use your # favourite editor or "./update-rc.d" to modify it. # # Format: # <sort> <off-> <on-levels> <command> 05 - 1 /etc/init.d/single 05 - S /etc/init.d/keymaps.sh 05 - S /etc/init.d/keymaps-lct.sh 10 - 2,3,4,5 /etc/init.d/sysklogd 10 - S /etc/init.d/checkroot.sh 11 0,1,6 - /etc/init.d/cron 12 0,1,6 2,3,4,5 /etc/init.d/kerneld 19 0,1,6 2,3,4,5 /etc/init.d/bind 20 - 0,6 /etc/init.d/sendsigs ... 25 0,6 - /etc/init.d/hwclock.sh ... 90 - 0 /etc/init.d/halt 90 - 6 /etc/init.d/reboot and there are no other combinations of runlevels on my system. debian packeages do not modify this file or rc?.d symlinks directly, they use update-rc.d. I don't know if this helps or if I just don'T understand the discussion.
