On Fri, Jun 01, 2001 at 10:51:37PM -0700, Eric G. Miller wrote:
> On Sat, Jun 02, 2001 at 12:00:29AM -0500, will trillich wrote:
> > is there a DEBIAN-happy way to permanently remove an
> > /etc/init.d/* service? this wholesale 'rm' stuff sounds hacky
> > for such a streamlined apt-friendly distribution. what's the
> > debian way of purging-inits-for-posterity?
>
> dpkg --purge <package>
>
> With Potato, I seemed to remember I couldn't really get rid of the
> package that contained portmap for some reason (a dependency or
> something) but I always just had "exit 0" at the top of the init.d
> script since I never needed RPC. Seems portmap's in it's own package in
> Sid (unstable).
>
> The init scripts are only removed if you purge the package that "owns"
> it. Occasionally people might want to hack the Debian supplied init
> scripts, so dpkg doesn't muck with them too much, except on a "purge".
>
> Also, the init scripts usually test that the program they're about to
> start still exists. So, obviously the service won't be run (nor will
> the script error).
>
> As far as update-rc.d goes; if a package is updated and at least one
> symlink already exists in one of the /etc/rc?.d dirs, then symlinks
> won't be modified. Otherwise, the scripts don't have a way to
> differentiate between a clean install and an update. If no symlinks
> exist, it is assumed an "install" is occurring and the default symlinks
> should be created (which may not be what you want!). Make sense?
i spoze i should've been more clear--
is there a debian-friendly way to permanently disable
a startup (/etc/init.d/*) service so's some future
"apt-get dist-upgrade" doesn't resurrect it from the grave?
if so, how?
if not, maybe we should have an "update-rc.d disable <xyz>"
feature? (until which time we'll "mv" or "rm" by hand any such
links in /etc/rc?.d/*, i suppose.)
--
DEBIAN NEWBIE TIP #16 from Will Trillich <[EMAIL PROTECTED]>
:
Why are *.rpm (RED HAT PACKAGES) considered spawn of Satan?
Because the Debian package system is a lot more sophisticated
than the one Red Hat uses; lots more inter-dependency information
is built in to a *.deb package. If you bypass that with an *.rpm
file, you're taking chances with your system. Try to "apt-get
install <debian-only>" packages if possible. (Also check out the
"alien" package if you must.)
Also see http://newbieDoc.sourceForge.net/ ...
