From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Alsa module configuration Date: Mon, 02 Sep 2002 15:40:21 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <20020902132257.644DF1448F@Cantor.suse.de> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20020902132257.644DF1448F@Cantor.suse.de> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Paul Davis Cc: Andy Wingo , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Mon, 02 Sep 2002 09:24:20 -0400, Paul Davis wrote: > > >About OSS configuration, it was explained separately in another part > >after the sentence above. > > but we don't provide any such script ... without it and without the > modules.conf entries, any OSS program will fail, right? well, you can load the modules manually, of course :) recently i came to believe that loading the oss modules in the init script would make the life easier. then we can delete all these complex things. the only necessary configuration is an alias alias snd-card-0 snd-xxxxx and others are not necessary. even the alias above can be omitted if alsasound init script reads another configuration file such like /etc/sysconfig/sound and retrieves the driver modules from it. nevertheless, the two entries i referred to are irrelevant with OSS. as long as you're using alsasound init script, they are not needed, although you may get annoying messages from the kernel if you access to an unexisting device (but this also happens e.g. when you access to /dev/mixer3 which is not aliased). Takashi ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390