On 06/05/2009 05:36 PM, Bill Nottingham wrote:
Hans de Goede (hdegoede redhat com) 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, so since that we've udev rules taking care of stable eth# names it might be the easiest to just store the eth# names (easiest for the initscripts that is). But first I'll checkout what fcoe-utils has to offer wrt config files and initscripts. Regards, Hans
Bill _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list redhat com https://www.redhat.com/mailman/listinfo/anaconda-devel-list