Re: Issues with dracut and network device naming

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

 



Hi,

On 08/28/2009 05:25 PM, Seewer Philippe wrote:


Hans de Goede wrote:
Hi,

On 08/28/2009 02:45 PM, Seewer Philippe wrote:

Harald Hoyer wrote:
[snip]
So I would like to propose another solution for this, allow specifying
both an interface-name and a mac with ip=, and then have the dracut
generated rules do the rename and init. This way problems 3) and 4)
above are solved, and we can easily also write the mac address to
grub.conf from anaconda when generating the ip= cmdline.
yes, sane solution .. +1
Yes, +1 as well. I'd vote for not doing this inside the ip= parameter,
but use something like ifname=iface:mac.


Hmm, I'm not so sure about that, it sure would be easier for the genrules
script to have all the info in one place, instead of having to piece
bits together.

Yes. But I think from a user's point of view, the ip= argument is
already overloaded. ifname= (or whatever) would be much clearer and easier.


See my relpy to Jon Masters mail about there in the future potentially being
other unique identifiers to persistenly name a NIC, given this I'm going to
implement a ifname=eth0:<unique-id> syntax, where for now the unique id will
be a mac, but this way we can easily use other unique-id strings in the future
(much more easily then when we put everything in the ip= syntax)

Regards,

Hans

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux