From: Bill Nottingham <notting@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: eth3 becoming /sys/class/net/dev22358
Date: Wed, 31 Jan 2007 16:58:59 +0000 [thread overview]
Message-ID: <20070131165859.GF26542@nostromo.devel.redhat.com> (raw)
In-Reply-To: <slrnes14nq.q2m.mykleb@99RXZYP.ibm.com>
Jan Frode Myklebust (MYKLEB@no.ibm.com) said:
> As HWADDR in ifcfg-eth* seems to be more of a safety-net, what's the
> recommended way of getting stable eth* names on RHEL4? Creating udev-rules
> for all servers seems too much... It would be nice if there were a simple
> "save-current eth*-mac mapping" function that would be restored upon boot.
The answer *is* to add HWADDR to the config files.
Bill
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2007-01-31 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 13:00 eth3 becoming /sys/class/net/dev22358 Jan-Frode Myklebust
2007-01-31 15:25 ` Jan-Frode Myklebust
2007-01-31 16:24 ` Bill Nottingham
2007-01-31 16:36 ` Linas Vepstas
2007-01-31 16:37 ` Jan Frode Myklebust
2007-01-31 16:57 ` Jan Frode Myklebust
2007-01-31 16:58 ` Bill Nottingham [this message]
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=20070131165859.GF26542@nostromo.devel.redhat.com \
--to=notting@redhat.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).