Oh, I've been using update-rc.d remove instead of update-rc.d stop... So packages will not turn the services back on if there is a K symlink? Cool.
Thanks! P.S. please CC: any response to me, as I am not subscribed to debian-user ----- Forwarded message from Mircea Luca <[EMAIL PROTECTED]> ----- Date: Mon, 01 Jan 2001 15:57:58 -0800 From: Mircea Luca <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.0-prerelease i586) X-Accept-Language: en To: Rob <[EMAIL PROTECTED]> CC: debian-user@lists.debian.org Subject: Re: init scripts Rob wrote: > > Hello, > > Occasionally I install a Debian package that I > do not want to start everytime I boot. In this > situation, I usually use update-rc.d and either > stick the init script into a specific runlevel > or just remove it from all runlevels. > > This works fine, however, when I do an upgrade, > any packages that are upgraded will put the > symlinks back and I will have to remember to > use update-rc.d on each package that was upgraded. > > Since I use stable and track security, this > happens enough to be a major pain. > > Is there a "right" way to do this? I don't want > to put packages on hold or anything, because I > do want them to be upgraded, but I want my configuration > of the init system to be honored. > > Thanks in advance, > Rob Helmer > > P.S. Please CC: me as I am not currently subscribed > to debian-user > I usually make a K symlink in the same rc.d with the same nr. as the S eg. from my /etc/rcS.d K41portmap #made by myself S41portmap #made by netbase ----- End forwarded message -----
