#2057: Udev-120
------------------------------------------+---------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [email protected]
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0
Component: Book | Version: SVN
Severity: normal | Resolution:
Keywords: |
------------------------------------------+---------------------------------
Comment (by Bryan Kadzban):
Replying to [comment:10 [EMAIL PROTECTED]:
> We don't really need to configure persistent rules for a network device
until after the first boot, do we?
Wouldn't that be nice. ;-)
Section 7.13 (Configuring the network Script) requires the user know the
interface name that will be assigned to the NIC when the system boots,
because that's what the ifconfig.XXXX directory's name is based on. And
if there's more than one ethX device, then the assignment will be (or at
least, can be) random.
The real problem is that the more recent you get with udev, the more of
the logic gets pushed out from the script and into the rules file. This
isn't really bad, but when the newest daemon won't start inside chroot
(because the host's daemon is running), and nothing will be able to
interpret the rules in a compatible way, it's a problem.
(Looks like there have been a few useful changes made since -120, as well.
Not that we want to wait even longer, but -121 might be good.)
I've been waffling back and forth between the following options for
several months now:
1. Patch udev so it's able to start up inside a chroot, even if the
host's udev is running. Involves adding an --in-chroot option to udevd,
then firing it up for the shortest time possible (just long enough to
{{{udevadm trigger --subsystem-match=net}}} and {{{udevadm settle}}}) to
create the rules. The issue would be whether we want to build udev twice
(once with the patch, then install it, then create the rules, then go back
and recompile / reinstall it without the patch), or we want to keep the
extra code hanging around in udevd forever. But we don't have to copy all
the logic that's already in udevd into anywhere else with this option.
2. Write a script that copies the device whitelist from the current rules
file, and gets updated every time the list of environment variables used
for communication (see write_net_rules) changes. Possibly tons of
maintenance, but this is entirely independent of udev; no patching or
anything crazy like that.
(I've tried posting the patch to upstream once; nobody commented. It's
attached.)
Opinions here?
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2057#comment:11>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
