From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: alsaconf checking for OSS modules Date: Tue, 27 Jul 2004 15:59:54 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <20040723165213.089db15b@mango.fruits.de> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20040723165213.089db15b@mango.fruits.de> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Florian Schmidt Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Fri, 23 Jul 2004 16:52:13 +0200, Florian Schmidt wrote: > > > Hi > > i think quite a bit of trouble could be saved if the alsaconf script > would check if any OSS modules are loaded. I think it's enough to spit > out an error to the user. rmmod'ing them would fail in most cases > anyways since users that use alsaconf usually run some desktop > environment like kde or gnome, too. And these like to keep the modules > busy with their mixer applets, sound servers, etc... > > What do you guys think? Well, it's not so easy to find out the running OSS module name. A possible solution would be to parse the output of lsmod and check the dependency of soundcore module. But, we need to take it into account that lsmod output format is different between 2.4 and 2.6. Sigh... Takashi ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click