On Wed, Mar 16, 2011 at 3:34 AM, Scott James Remnant <scott@xxxxxxxxxxxx> wrote: > On Tue, Mar 15, 2011 at 10:25 AM, Kay Sievers <kay.sievers@xxxxxxxx> wrote: > >> The maintainers of the commonly used early-boot tools agreed to use a >> /dev/.run/<package>/ dir instead, which will be provided by initramfs >> and systemd. After the basic bootup, the /dev/.run/ tmpfs mountpoint >> will be available at /var/run/. The /dev/.run/ directory is at that >> point just an "early-boot alias" for /var/run/, and all early-boot >> tools will have their data in /var/run/, just like any other service. >> In the end, there should be no custom .-dirs left in /dev, besides >> this "alias". >> > Kay has clarified in IM that the /dev/.run directory is bind-mounted > to /var/run later in the boot, so it's available at both paths always. > If other distros ignore that, then it's just a change of path for > udev. > > Which makes me wonder why this is necessary at all. Modern distros > have a tmpfs mounted on /var/run at all phases of the boot, there are several packages in Mandriva that install subdirectories in /var/run and simply expect them to be present at any time. My first try at tmpfs-mount /var/run under systemd was disaster. While I can fix all those packages to install tmpfiles.d under systemd, I do not see what can be sensibly done without (except extracting tmpfiles.d from systemd into separate package). So the question is - is all of this still going to work without this bind mount? > mounting > it in the initramfs, binding it to the target filesystem, and ensuring > that it remains mounted even if an intermediate /var is placed in the > way. > > So udev could simply use /var/run/udev all the time anyway > please, do not! For the reasons above ... -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
