Re: Persistent module storage [was Linux 2.4 Status / TODO page]

From: Gerhard Mack (gmack@innerfire.net)
Date: Mon Nov 06 2000 - 20:20:21 EST

Next message: Horst von Brand: "Re: Persistent module storage [was Linux 2.4 Status / TODO page]"
Previous message: Rick Lindsley: "Comprehensive list of locks available?"
In reply to: James A. Sutherland: "Re: Persistent module storage [was Linux 2.4 Status / TODO page]"
Next in thread: James A. Sutherland: "Re: Persistent module storage [was Linux 2.4 Status / TODO page]"
Reply: James A. Sutherland: "Re: Persistent module storage [was Linux 2.4 Status / TODO page]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Then none of this is relevant to you, since you can't unload any modules! And
> now you're the one doing the trolling... WTF do you think module code is
> supposed to do when you don't use modules?!
>

Simple ... I'd rather the hardware was set to 0 on startup but I know what
problems that presents to modules..

And no it wasn't the driver doing it afik. Sound card starts on max volume
as soon as it's initialised.

Gerhard

-- Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/

Next message: Horst von Brand: "Re: Persistent module storage [was Linux 2.4 Status / TODO page]"
Previous message: Rick Lindsley: "Comprehensive list of locks available?"
In reply to: James A. Sutherland: "Re: Persistent module storage [was Linux 2.4 Status / TODO page]"
Next in thread: James A. Sutherland: "Re: Persistent module storage [was Linux 2.4 Status / TODO page]"
Reply: James A. Sutherland: "Re: Persistent module storage [was Linux 2.4 Status / TODO page]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Nov 07 2000 - 21:00:21 EST