On Tue, Nov 21, 2000 at 11:11:47AM -0800, [EMAIL PROTECTED] wrote:
> > 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 (w
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
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 mou
On Tue, 21 Nov 2000, Enrique Robledo Arnuncio wrote:
> On Tue, Nov 21, 2000 at 01:47:10PM +1100, Matthew Dalton wrote:
> > This begs the question: Can sfxload be considered a system file because
> > the system could attempt to run it after the root partition has been
> > mounted, but before the ot
On Tue, Nov 21, 2000 at 01:47:10PM +1100, Matthew Dalton wrote:
> This begs the question: Can sfxload be considered a system file because
> the system could attempt to run it after the root partition has been
> mounted, but before the other ones have been mounted? Should sfxload be
> installed to /
Hi all,
Apologies if I've sent this to the wrong lists.
I'm running kernel 2.4.0-test10 with a mostly potato system (modutils
2.3.19 compiled from woody*), and I have an AWE32 sound card (non-pnp).
I followed the instructions in the kernel documentation for the AWE32
(midi) to the letter, and it
6 matches
Mail list logo
