Re: Issues with dracut and network device naming

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

Jon.


--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux