On Thu, Nov 12, 2009 at 09:03:59AM -0600, Raphael Geissert wrote: > Michael Hanke wrote: > [...] > > > > Can anyone please point me to the problem and its solution? > > > > When making changes to the runlevels either via update-rc.d or the lsb > header, the init script needs to be removed first (via update-rc.d, as > simply removing the symlink won't work in the case of file-rc).
Ah! Thanks a lot, that explains it. > In other words: you need to check if the user is upgrading from an affected > version (probably anything lt the new version) and then do an update-rc.d > remove. All that before the #DEBHELPER# mark so that the rest is done for > you. > > And like Rogéiro Brito said, remove the S runlevel. First of all, S is only > used by some special cases where the script only needs to be run once, > second, syslog daemons are only available from post-rcS (which at some > point would render your package uninstallable because of unmet init script > dependencies). Well, the respective package is a firewall. I'd say it should run once in S pretty much right after networking becomes available. It may even not be necessary to run it again when switching to a runlevel other then 0 1 6, correct? So instead of removing S I should remove 2 3 4 5, I guess. Additionally, as you mentioned syslog is not available at that early stage. The question is now whether I should sacrifice the startup log-message for the sake of establishing the firewall as early as possible -- or not? Oppinions very much appreciated! Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
