In article <linux.kernel.389FF4D6.72FDB9EC@mandrakesoft.com>,
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>david parsons wrote:
>> I'd be tempted to just leave the modules they way they work now,
>> because in most cases module loading lets you shoot yourself in the
>> foot (except, for no apparent reason, ethernet modules, where a lot
>> of 'em won't autoprobe because The Computer Knows What's Best.
>> Sigh.) today, and someone may actually want to take advantage of
>> one module stepping all over anothers address space.
>
>modern ethernet hardware is PCI, and autoprobes. though I do agree --
>typically one should specify ethXX assign with "alias ethXX my_driver"
>in conf.modules.
(digressing wildly)
That's assuming that your system does (shudder) demand-loading
of ethernet drivers.
This is not always the case; I put all the ethernet drivers into
modules for Mastodon, but I load all of them when the system starts
up so I can automatically detect eth0. It's difficult to
autodetect ethernet cards when you first have to know all the
details about them.
____
david parsons \bi/ I hate the ``The Computer Doesn't Think Modules Should
\/ AutoProbe. Trust The Computer. The Computer Is Your
Friend!'' message.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:13 EST