This administrator indeed did read the documentation and also did check that the boot order in rsS made sense and reasonably resembles what exists on a pristine system.
This administrator also stated so in the initial bug report. Therefore, it seems that your affirmation about someone not having read the documentation is purely gratuitous at best and downright insulting at worst. I maintain my position that this should have gone to Experimental, not Unstable, and that it should have a priority of "Extra" not "Optional". As for you affirmations that the package assumes nothing, this is wrong. Upstream's README and the manual page clearly state what they expect to see in any init script to determine the boot dependencies. Most Debian packages' init don't provide the information required, which therefore means that a lot of override files must be created and that without the overrides a system can and in this case indeed did go into a state where it was not bootable. This being said... After some manual fiddling with the boot order, I eventually got something bootable again. My rcS is currently as follow: README S03hotplug S06sudo S01hostname.sh S03ifupdown-clean S06udev-mtab S01hwclockfirst.sh S03procps.sh S06urandom S01keymap.sh S04mountall.sh S07hwclock.sh S02bootlogd S04setkey S07pppd-dns S02checkroot.sh S04udev S08hotplug-net S02hdparm S05ifupdown S08mountnfs.sh S02module-init-tools S06bootmisc.sh S08networking S02modutils S06console-screen.sh S08ntpdate S03checkfs.sh S06dns-clean S43portmap S03discover S06nviboot S70xfree86-common This leaves a lot to be desired, though, as things like hwclockfirst complain that some procfs bits are not available (which makes sense, since procfs is taken care of much later). There are still a few other error messages from various daemons as well. Another issue (of severity "normal") is that Debian boot scripts are not quite expected to cleanly run in parallel yet, which results in boot messages overlapping each other into an unreadable garbage, with one script's "Launching daemon NAME..." showing up in between another script's message and its "done." statement, etc. Petter, don't get me wrong: I see a lot of potential in this package, but I really do believe that it should have gone into Experimental first, just like any other package that messes with other applications' boot order should, and be thoroughly tested there until everyone is satisfied that this is safe to upload into unstable. -- Martin-Éric Racine http://q-funk.iki.fi
