Mike Johnston schrieb: > Thank you. > That would work however, I want to make 30 instances for 30 machines. I need > to generate the 70-persistent-net.rules file so each machine has fixed > interface names.
you don't need a 70-persistent-net.rules file. as you are writing in plural, you have more then 1 interface on each machine? if not, just forget about - the single interface will always be eth0. if you have more than 1, but with different chipsets, you can either create specific rules for udev or have 1 interface in the kernel (will be eth0) and the rest as modules, forcing the modules to be loaded in a given sequence resulting in the same order each time you boot. i'm having a board here with 2 onboard nics (realtec, but with abit mac-prefix 00-50-8d). the mac differs by 1 in the very last digit. booting without rules is 50% chance to have the nics the way you want. in this situation you really need to have the 70..rules-file! > What I don't understand is that if its a symlink on read/write partition it > consistently keeps adding to the file. If it's not a symlink but a real > file, it doesn't regenerate and stays a fixed size. > How does it know this? im not shure, but i guess it might be a feature (or bug) in the /lib/udev/rule_generator.functions i guess the directory is not writeable, just the linked file is. you can change the write_net_rules to not check for writeable or use another path for the locking-file by copying and renaming the fuctions from rule_generator.function to write_net_rules and modify it to your needs. tobias -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
