Assignment of network interface names at boot time
From: Tiago Manuel Nunes Marques
Date: Mon Mar 23 2009 - 14:41:32 EST
Hi all,
I don't know if this would be more appropriate to submit
as a bug report but I would like to know where I could
start tackling this issue instead of submitting a bug
report.
I administer a small cluster which I have now started to
migrate to diskless root but I seem to be having problems
with the network interfaces, which, on boot, are randomly
assigned eth0 or eth1. This is a behavior that I didn't
experienced in 2.6.24 but 2.6.26 has some patches that I
would like to have.
UDEV rules are not a solution, since I need to boot from
the interface, hopefully having a way to define the same
interface to all the machines, for instance: have lower
MAC interfaces be eth0, boot from them, having the network
administrator change these interfaces for the PXE network,
if necessary. Right now, sometimes the test machine boots,
sometimes it gives eth0 to the other interface and fails
to mount the root filesystem.
Where can I start, as this been tackled yet? I searched
google but found no one with the same issues.
Best regards,
Tiago Marques
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/