I think I was only to get this private response. -- Thomas Poindessous
--- Begin Message ---
- To: Thomas Poindessous <thomas@poindessous.com>
- Subject: Re: Bug#239414: /etc/init.d/discover not removed when package is removed
- From: Martin Leopold <leopold@diku.dk>
- Date: Mon, 22 Mar 2004 18:39:02 +0100
- Message-id: <405F24B6.7040404@diku.dk>
- In-reply-to: <[🔎] 20040322172637.GA5080@poindessous.com>
- References: <[🔎] 405F139C.3000008@diku.dk> <[🔎] 20040322172637.GA5080@poindessous.com>
Thomas Poindessous wrote:Trying to get rid of discover (it messed up my alsa driver) I learned that removing discover doesn't stop it from running - this can't be right. While I can se the sense in not removing configuation files it doen't make sense to leave the program running after I've removed it.discover is run only one time in a normal boot operation. It detects what modules you need and loads them. If you remove discover, you will remove the program. But if you don't reboot, modules loaded by discover aren't unloaded, and that's normal. So if discover was loading oss module instead of your alsa modules, once you remove it, please reboot. If your problem is something, please pardon me and please give extra explanations.The sequence of events: 1. apt-get remove discover 2. reboot 3. Upon booting discover is still run and istalls OSS drivers that I don't want 4. dpkg --purge discover removes everything 5. Reboot 6. Discover is not run and the alsa scripts loads my drivers
--- End Message ---