Re: udev runtime data will move from /dev/.udev/ to /dev/.run/udev/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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, 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

Scott
--
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


[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux