Michael Meskes wrote: > On Wed, Aug 26, 2009 at 03:22:51PM +0200, Michael Biebl wrote: >>> 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 > > Sorry, don't see the problem. If a package were to change its own old links it > will have the right levels hardcoded in the postinst. Why can't insserv do the
Isn't it obvious? Only each package alone knows exactly which runlevels/priorities it's defaults are, insserv doesn't. Do you suggest that insserv should grep for update-rc.d calls in postinst for packages that install an init script to find out the default runlevel/priorities of a given package? That sounds error prone to me, as there might be multiple update-rc.d calls (e.g. in case of upgrade scenarios) in such a postinst. Cheers, Michael -- 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
