From: Hans de Goede <hdegoede@redhat.com>
To: Discussion of Development and Customization of the Red Hat Linux
Installer <anaconda-devel-list@redhat.com>
Cc: initramfs <initramfs@vger.kernel.org>
Subject: Re: Issues with dracut and network device naming
Date: Mon, 31 Aug 2009 13:17:41 +0200 [thread overview]
Message-ID: <4A9BB155.8020106@redhat.com> (raw)
In-Reply-To: <1251470171.1305.144.camel@perihelion.bos.jonmasters.org>
Hi all,
On 08/28/2009 04:36 PM, Jon Masters wrote:
> On Fri, 2009-08-28 at 14:14 +0200, Hans de Goede wrote:
>
>> When using iscsi for example, an interface name (usually eth#) is
>> specified on the dracut cmdline, but if a machine has multiple nics
>> the probe order done by dracut may very well differ as the one
>> which was used during install when the dracut cmdline gets generated.
>
> It's worth talking to Prarit about this stuff because he's looking into
> persistent network device naming issues in general. I'm sure you know,
> but there's a generic DMI extension that allows you to determine from
> the system what the PCI slot->device name mapping should be so that e.g.
> moving the disk from one system to another doesn't affect the naming.
>
> Of course this only works on systems with the requisite SMBUS/DMI
> extension *but* it will (eventually) be a nice solution to the naming
> issues and worth working with him on if you're not already.
>
Hmm, well I really want to have something in place soon, and currently
all Fedora persistent network device naming is done based on MAC.
But I would like to keep possibilities like this open for the future, so
I'll go ahead and implement Seewer's suggeston to use a separate cmdline
arg for this called ifname, for now we will then have / use:
ifname=eth0:aa:bb:cc:dd:ee:ff
But in the future it could also be something like for example:
ifname=eth0:/sys/devices/bus/pci/00:00:00:01.5
Regards,
Hans
next prev parent reply other threads:[~2009-08-31 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 12:14 Issues with dracut and network device naming Hans de Goede
2009-08-28 12:43 ` Harald Hoyer
[not found] ` <4A97D0F9.9020302-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-08-28 12:45 ` Seewer Philippe
2009-08-28 14:16 ` Hans de Goede
[not found] ` <4A97E6CA.2020200-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-08-28 15:25 ` Seewer Philippe
[not found] ` <4A97F6E6.4040206-omB+W0Dpw2o@public.gmane.org>
2009-08-28 20:55 ` Victor Lowther
2009-08-31 11:20 ` Hans de Goede
[not found] ` <4A97CA1A.5080606-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-08-28 14:36 ` Jon Masters
2009-08-31 11:17 ` Hans de Goede [this message]
[not found] ` <4A9BB155.8020106-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-08-31 13:32 ` Victor Lowther
2009-08-31 15:16 ` Jon Masters
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=4A9BB155.8020106@redhat.com \
--to=hdegoede@redhat.com \
--cc=anaconda-devel-list@redhat.com \
--cc=initramfs@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 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.