Alex Merry wrote: > There's no real way to get around this without setting up the network > after rebooting.
Not entirely true. If you decide before the reboot which form of
persistence you want to use, set up that script, and:
for file in /sys/class/net/*/uevent ; do
echo "add" >$file
done
or:
udevtrigger --attr-match=address
(while udevd is running inside chroot, so it only updates the rules
files inside chroot... hmm, that's a problem), then you'll get your
persistent rules written before the reboot.
But since running udevd inside chroot is an issue, there's still another
way to get around it: Just generate the "target" rule manually. I.e.,
let the user take the place of the persistent rule generator. (This is
the same setup as we have today: we tell the user "now generate a rule
for your NIC that matches on either MAC address or location; here are a
couple samples:". The only change would be to add some text before that
explaining that when the user adds another NIC or another CD, the
rule-generating rule(s) will automatically give it a persistent name,
and if they *replace* their old NIC, its name will not be available).
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
