[gentoo-user] udev net persistent rules
When updating udev from a version without persistent rules to one which has them, how do I force the system to create 60-persistent-net.rules with the current ethn assignments *before* rebooting the system? I am updating remote systems using ssh, and had a problem whereby one system had reversed eth0 and eth1 after the upgrade. I want to make sure that upgrades to other systems do not have this problem by ensuring that the persistent net rules are created before rebooting after the upgrade (which also upgrades the kernel, hence the need for the reboot) -- [EMAIL PROTECTED] mailing list
[gentoo-user] udev net persistent rules
on Wednesday 05/02/2007 Graham Murray([EMAIL PROTECTED]) wrote When updating udev from a version without persistent rules to one which has them, how do I force the system to create 60-persistent-net.rules with the current ethn assignments *before* rebooting the system? I am updating remote systems using ssh, and had a problem whereby one system had reversed eth0 and eth1 after the upgrade. I want to make sure that upgrades to other systems do not have this problem by ensuring that the persistent net rules are created before rebooting after the upgrade (which also upgrades the kernel, hence the need for the reboot) I am pretty sure you can do /lib/udev/write_net_rules and that will create the file which you then can fix the mac addresses in the file. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
