Graham, If the "/etc/udev/rules.d/70-persistent-net.rules" file does *not* exist then the interface order at boot is determined by the order of the "/etc/rc.modules" network module modprobe's, top to bottom. The "/etc/udev/rules.d/70-persistent-net.rules" file will be automatically created by udev and will have priority on future boots.
Yes, you can swap interface names my swapping the NAME= values in the "/etc/udev/rules.d/70-persistent-net.rules" file. This all happens before the network interfaces are brought up. Lonnie On Jun 25, 2012, at 4:08 PM, Graham S. Jarvis wrote: > Hello again everybody, > > getting into much more detail regarding this issue of interfaces, networks > and > domains here's something else for the Wiki..... > (On the http://doc.astlinux.org/userdoc:tt_change_net_hardware page perhaps) > > > I was thinking about how to rename eth1 and eth2 so that I didn't have to > move > the cables. > > This would be very useful if you are re-configuring a remote machine - if a > little adventurous to be doing this remotely ;) > > I remembered that I had done this before and so I took a look at my > /etc/udev/rules.d/70-persistent-net.rules file: > > # PCI device 0x100b:0x0020 (natsemi) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:00:24:c4:3f:cc", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth0" > > # PCI device 0x100b:0x0020 (natsemi) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:00:24:c4:3f:ce", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth2" > > # PCI device 0x100b:0x0020 (natsemi) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:00:24:c4:3f:cd", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth1" > > This is a Net4801 so I assume that the MAC addresses are normally sequential > (as > above - ...:cc = eth0, ...:cd = eth1 , ...:ce = eth2) > > BUT, > If I remember right this is also going to be the _order_ that the interfaces > are > brought up. > > > How does this affect the boot progress? > Can it be that the boot process expects interfaces to be present that haven't > yet come up? > > And then a little more tricky.... > What happens if someone edits this file, deletes all the lines and saves an > empty file? > i.e. on next boot the file exists but is empty > > > Just a few (more) thoughts..... > > -Graham- > PS: I've been having some boot problems with this machine so I'll try > deleting > /etc/udev/rules.d/70-persistent-net.rules and see if it's the same as the > above > when it re-boots and whether there is an "up" order issue. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
