[LFS Trac] #2057: Udev-122

Bryan Kadzban bryan at kadzban.is-a-geek.net
Tue May 20 17:11:08 PDT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Bruce Dubbs wrote:
> If a system has more than one network card that could be identified 
> with the same prefix, (eth0, eth1, etc).  We would like to like to 
> configure udev within chroot so it will maintain the same 
> relationship of ethx to the specific network card that currently 
> exists upon reboot.  This is not currently possible in the newer udev
> instantiations without a patch developed by Bryan.
> 
> Other distros like RH, SuSE, Debian, don't even try it.

Pretty much.  The reason other distros don't try it is because their
installation method is so different from ours, but that's more or less
irrelevant to the summary.  :-)

> In my mind, this is a very specialized need.  It appears that Bryan 
> has come up with a methodology (or two!)

...three, now, and I think the third one is pretty good.  ;-)

> IMO, the way to address this is not with a complex set of rules for 
> the book or a patch and multiple build method, but a warning about 
> the issue and a pointer to a hint or wiki entry to handle the 
> specific problem for those few people that need it.

Now that's not a bad idea.  That more or less matches up with what
Alexander was saying earlier today in the ticket about the problem
having multiple solutions.  (In his words, the problem is:

> configuring the network interfaces (i.e., getting the correct udev 
> rules and writing the corresponding interface configuration files)

- -- and I'd agree.)  It's also similar to his comments about providing
examples of ways to solve the problem (whether those are at the other
end of a wiki link, or a hint link, or right in the book; it probably
doesn't matter a ton), rather than dictating one solution.  I do like
that.

(I should note that the patch wouldn't require building udev twice; it
won't hurt anything to have the option sitting around unused.  It just
wouldn't be very clean.  But having the patch at all isn't the best
solution for everyone, either.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIM2icS5vET1Wea5wRA2W4AJsFwjzliziPtFGl6/3Ku6yq8dWn9gCeLQ9P
bXXsttg8RnX1a0ROIXUrWL8=
=R0ek
-----END PGP SIGNATURE-----



More information about the lfs-dev mailing list