* Mark L. Kahnt (kahnt@hosehead.dyndns.org) [021021 08:11]: > If you are going to get into shuffling around these items, I would > suspect that long-term package management considerations *might* be > better respected if you use update-rc.d(8) to make your changes, rather > than just diving in and renaming files that are *managed* by dpkg. No; this is a common misconception. update-rc.d just fiddles with the symlinks, the same way you can manually with mv, rm, and ln. It's purpose is to make it easier for packages' install/rm scripts to manage the links; IMHO it's easier for humans to just use mv, rm, and ln, rather than the somewhat obtuse syntax of this non-standard tool to accomplish the same exact thing. It's the same as update-inetd; it's more easily scriptable, but not easier for humans to use than 'vi /etc/inetd.conf'. initscripts are conf files, and any package that tramples them is broken. They are "managed" by dpkg only so far as it is aware that they are config files. It will not replace any existing ones, BUT it will replace them if they are entirely missing. Renaming, deleting, etc will be fine, and your choices will be respected across an upgrade, provided that you leave at least one S or K link for the package in at least one rc?.d directory. good times, Vineet -- http://www.doorstop.net/ -- "Extremism in the defense of liberty is no vice. Moderation in the pursuit of justice is no virtue." -- Barry Goldwater
Attachment:
pgpPGm80saCv2.pgp
Description: PGP signature