Re: RFC: configuration file for storing persistent FCoE information

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

 



Hans de Goede (hdegoede@xxxxxxxxxx) said: 
>> Hans de Goede (hdegoede@xxxxxxxxxx) said:
>>>> Stepping back a bit... why does it need to know the device
>>>> name - can't it be automatically determined via route?
>>> Erm, no, FCoE does not use IP, it uses Fibre Channel protocols
>>> encapsulated in ethernet packets, this is all handled
>>> by the kernel, all rc.sysinit needs to do is tell the kernel:
>>> "go talk FCoE on that NIC"
>>
>> OK. Still, device names aren't persistent. Hardware addresses
>> are a better key, if possible.
>
> Agreed, but in the end we need to echo a eth# name to
> a sysfs file

... really? What happens when the name changes in the kernel? (I
assume it's actually storing the device index, or similar.)

Bill

_______________________________________________
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