From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: Greg KH <greg@kroah.com>,
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, 02 Feb 2004 21:14:57 +0200 [thread overview]
Message-ID: <1075749297.6931.25.camel@nosferatu.lan> (raw)
In-Reply-To: <20040202181229.GB28007@mail.shareable.org>
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
On Mon, 2004-02-02 at 20:12, Jamie Lokier wrote:
> 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?
>
My general experience is that it does work fine in most cases, except
maybe sound and net which you need your aliases.
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-02 19:15 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
2004-02-02 19:14 ` Martin Schlemmer [this message]
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=1075749297.6931.25.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=greg@kroah.com \
--cc=jamie@shareable.org \
--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