>> I guess a debconf message explaining that the dependencies have to be >> changed to change the boot order would be in order. > > I don't think this suffices. Every maintainance script that moves some startup > links to a different level was supposed to check first whether those links are > still in the default level and not touch them if they weren't. Why can't we > expect the same from insserv?
That is impossible. insserv can't find out [1] which set of runlevels and priorities are the default for a given package, as we have no database for that in Debian (contrary e.g. to Fedora/Redhat, which encode the default runlevel/priorites in each init script header). Only each individual package knows, which it's default runlevels/priorities are. That's another shortcoming unfortunately of our current system. Cheers, Michael [1] At least I don't know of a sane way how to do that. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
