On Tue, 21 Nov 2000, Enrique Robledo Arnuncio wrote:
> On Tue, Nov 21, 2000 at 11:35:38AM +0100, [EMAIL PROTECTED] wrote: > > > No, both the program and the library should be under /usr, according > > > to the File-system Hierarchy Standard (you don't need them to boot, > > > restore, recover or repair the system). > > > > Except /etc/modules is read before mounting filesystems. > > Yes, but you should be able to let the awe_wave module be loaded first > as the kernel docs says, removing from modules.conf the post-install > line which runs sfxload, and run sfxload later from an /etc/init.d > script (with /usr mounted). Except, the "correct" way to use modutils IS to use the post-install line, because unused modules can be set to be periodically removed. A better solution would be to leave the post-install line and move the LOADING of awe_wave into /etc/init.d, after all FS' mounted. Or maybe we need a '/etc/modules.later' or something which would list modules not necessary for booting. I dunno. =) > > > This might be a "missing documentation" bug in the sfx-drv package, > > > though. > > (Sorry, I meant the awe-drv package) > > > At least. Or the script for loading the sound modules in /etc/init.d > > should be provided by sfx-drv (maybe). > > > > Yes. It would be a nice idea. ALSA works that way, BTW. > > On the other hand, we should be able to provide some useful sound > patches in order to be able to call sfxload from there. I don't know > if there are any DFSG compliant ones available... k
