Alexander E. Patrakov wrote:
Anyway, let me introduce udev-100 first - it (unfortunately) has the original non-educational CD-ROM rule generator in the recommended set of rules. The voting suggestion above holds only if we decide to ignore it, preferring Jim's viewpoint (in his opinion, a program that writes rules for itself is wrong). I disagree with that opinion, but don't want to force my disagreement upon others. Additionally, our work on showing the users the two styles of persistent rules (identity persistence and location persistence) is going to be lost if we adopt the stock generators.
Can we not have our cake and eat it too? By which I mean, can we not use the stock generators explaining which of the styles of the persistent rules it uses and also showing an example of the other style?
If I understand the code correctly, write_net_rules uses identity persistence and write_cd_rules uses location persistence, so suitable examples of both might already exist.
If we decide to go with stock generator rules, something has to be done with multiple network interfaces, because it is not nown which of them will get eth0 on the first boot (but the name will be the same on all subsequent reboots).
That's rather unfortunate!
Possible solutions: * Defer network configuration until after the reboot
I'd prefer not to do this, as we have managed to get away with avoiding a reboot up until now.
Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
