Le 15/01/2012 13:48, Matt Burgess a écrit : > "The rules to create persistent network interface and cdrom link > rules automatically in /etc/udev/rules.d/ have been disabled by > default. Explicit configuration will be required for these use > cases, udev will no longer try to write any persistent system > configuration from a device hotplug path." > > This causes jhalfs to bail out during chapter 7's general network > configuration when we try to generate those rules files. For the time > being, I'll work around it with '--enable-rule_generator' passed to > configure, as I don't know what upstream's intention is with that > functionality. > Hi, As of jhalfs, it'd be better to disable the line:
cat /etc/udev/rules.d/70-persistent-net.rules Maybe with a role='nodump' in<screen>, since it is not needed in jhalfs. Actually, I recently tried to run jhalfs on Fedora 16, in a virtual machine. I do not master all the aspects of VM, so the network interface name passed by the kernel was 'p2p1' instead of 'eth0'. It made the rule for creating persistent network interface fail, so jhalfs bailed out at the 'cat' line. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
