From: Greg KH <greg@kroah.com>
To: Stuart Lynne <sl@fireplug.net>, linux-kernel@vger.kernel.org
Subject: Re: How does "alias ethX drivername" in modules.conf work?
Date: Tue, 7 Aug 2001 22:45:00 -0700 [thread overview]
Message-ID: <20010807224500.A12601@kroah.com> (raw)
In-Reply-To: <20010807135135.J17723@fireplug.net> <20010807223625.A8330@nostromo.devel.redhat.com>
In-Reply-To: <20010807223625.A8330@nostromo.devel.redhat.com>; from notting@redhat.com on Tue, Aug 07, 2001 at 10:36:25PM -0400
On Tue, Aug 07, 2001 at 10:36:25PM -0400, Bill Nottingham wrote:
> Stuart Lynne (sl@fireplug.net) said:
> > So not being able to reliable map ethernet devices to names is a feature
> > not a bug ....
>
> With reasonable scriptage and 'nameif', it's doable. Only for
> ethernet at the moment, however (and I haven't actually implementing
> something that does this.) But it *is* doable.
With only adding one line to the current linux-hotplug scripts, a
co-worker of mine enabled reliable mapping that isn't dependent on pci
scanning, or hotplugging of pci cards. He used nameif and a table of
MAC addresses that map to the name he wanted.
greg k-h
next prev parent reply other threads:[~2001-08-08 5:45 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 20:51 How does "alias ethX drivername" in modules.conf work? Stuart Lynne
2001-08-08 2:36 ` Bill Nottingham
2001-08-08 5:45 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-08 13:59 Matt_Domsch
2001-08-03 21:29 Mark Atwood
2001-08-04 1:21 ` Chris Wedgwood
2001-08-04 1:32 ` Thomas Duffy
2001-08-04 2:31 ` Chris Wedgwood
2001-08-04 4:39 ` Jim Roland
2001-08-04 19:35 ` Riley Williams
2001-08-06 19:59 ` Thomas Duffy
2001-08-06 22:56 ` Riley Williams
2001-08-06 23:46 ` Andrzej Krzysztofowicz
2001-08-07 7:04 ` Riley Williams
2001-08-07 10:49 ` Andrzej Krzysztofowicz
2001-08-07 19:04 ` Riley Williams
2001-08-07 21:46 ` Mark Atwood
2001-08-07 22:33 ` Tim Jansen
2001-08-07 23:06 ` Josh Wyatt
2001-08-07 23:35 ` Riley Williams
2001-08-08 0:04 ` Josh Wyatt
2001-08-08 6:28 ` Riley Williams
2001-08-08 10:59 ` Alan Cox
2001-08-08 0:08 ` Mark Atwood
2001-08-08 6:40 ` Riley Williams
2001-08-08 8:41 ` Andrzej Krzysztofowicz
2001-08-08 10:52 ` Eric W. Biederman
2001-08-08 11:40 ` Andrzej Krzysztofowicz
2001-08-08 22:04 ` Riley Williams
2001-08-08 21:09 ` Riley Williams
2001-08-08 0:11 ` Mark Atwood
2001-08-08 6:47 ` Riley Williams
2001-08-08 0:16 ` Mark Atwood
2001-08-08 20:26 ` Riley Williams
2001-08-08 9:30 ` Andrzej Krzysztofowicz
2001-08-08 21:31 ` Riley Williams
2001-08-08 21:42 ` Alan Cox
2001-08-08 22:24 ` Horst von Brand
[not found] ` <9kpub6$8fu$1@ns1.clouddancer.com>
2001-08-09 20:05 ` Colonel
2001-08-10 6:32 ` Paul Gortmaker
2001-08-10 21:25 ` Riley Williams
2001-08-15 4:32 ` Paul Gortmaker
2001-08-04 4:33 ` Jim Roland
2001-08-04 4:48 ` Jim Roland
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=20010807224500.A12601@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sl@fireplug.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.