On Sun, Jun 03, 2012 at 03:00:27PM -0700, Bryan Kadzban wrote: > > One more thing though, thinking about it, is that we will need the > > systemd-tmpfiles tool because udev is not going to support the > > /lib/udev/devices directory any longer for creating custom devices, so > > you might want to still build and install all of the parts of that for a > > standalone udev build if doing so doesn't bring in more dependencies. > > I'd rather not replace "cp -a /lib/udev/devices/* /dev" in a boot script > with a binary that nothing else uses, plus its configuration (which > doesn't use nodes in /lib/udev/devices like what has been the udev ABI > for *years*, but instead uses a list of device descriptions), plus any > systemd-level libraries it may or may not need in the future. Actually other things could use it because of /tmp and /run and creating/removing files/directories there on bootup. > If a system is already running systemd, then systemd-tmpfiles may or may > not be the best place to do this (the ABI change is a problem for those > systems, unless I'm missing something in the *tmpfiles* manpages). But > if systemd is not running, then sticking to the previous ABI explicitly > is the right way to go I think. Unless you don't have a previous abi. Gentoo relies on udev copying things from /lib/udev/devices, which is gone with this version of udev, so we need the new abi. So, how about an extra switch --enable-tmpfiles-d that will toggle on or off whether that is built on a standalone udev build? William
Attachment:
pgpLCxJ2iW4pW.pgp
Description: PGP signature
