From: Jamie Lokier <jamie@shareable.org>
To: Greg KH <greg@kroah.com>
Cc: Martin Schlemmer <azarah@nosferatu.za.org>,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: module-init-tools/udev and module auto-loading
Date: Mon, 2 Feb 2004 18:12:29 +0000 [thread overview]
Message-ID: <20040202181229.GB28007@mail.shareable.org> (raw)
In-Reply-To: <20040202052100.GA21753@kroah.com>
Greg KH wrote:
> Rusty had it correct in that you need to try to load for the type of
> module:
> alias eth1 tulip
> alias usb-controller usb-ohci
> and so on. That's the much better way.
Shouldn't these things be autodetected?
"alias usb-controller" is a poor example. Shouldn't the kernel
automatically load drivers for all USB controllers that are found?
(On my system, there's more than one type, which makes "alias
usb-controller" even uglier).
"alias eth1" may be necessary to bind discovered NICs with the right
interface names, but it's unfortunate. One system where I had "alias
eth0 ..." failed to boot after a kernel upgrade when the named driver
no longer supported that network card (a different driver took over
support).
-- Jamie
next prev parent reply other threads:[~2004-02-02 18:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 22:31 module-init-tools/udev and module auto-loading Martin Schlemmer
2004-02-02 0:10 ` Rusty Russell
2004-02-02 19:02 ` Martin Schlemmer
2004-02-03 0:55 ` Rusty Russell
2004-02-03 4:55 ` Martin Schlemmer
2004-02-03 17:48 ` Martin Schlemmer
2004-02-03 19:33 ` viro
2004-02-03 20:47 ` Martin Schlemmer
2004-02-03 20:53 ` viro
2004-02-03 21:34 ` Martin Schlemmer
2004-02-04 1:22 ` Rusty Russell
2004-02-04 2:04 ` viro
2004-02-04 3:43 ` Rusty Russell
2004-02-02 5:21 ` Greg KH
2004-02-02 18:12 ` Jamie Lokier [this message]
2004-02-02 19:14 ` Martin Schlemmer
2004-02-02 19:13 ` Martin Schlemmer
-- strict thread matches above, loose matches on Subject: below --
2004-02-02 7:20 "Andrey Borzenkov"
2004-02-02 7:34 ` Greg KH
2004-02-03 15:00 "Andrey Borzenkov"
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040202181229.GB28007@mail.shareable.org \
--to=jamie@shareable.org \
--cc=azarah@nosferatu.za.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox