From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lennart Poettering Date: Thu, 17 Mar 2011 14:39:55 +0000 Subject: Re: udev runtime data will move from /dev/.udev/ to /dev/.run/udev/ Message-Id: <20110317143955.GA21600@tango.0pointer.de> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Thu, 17.03.11 13:24, Andrey Borzenkov (arvidjaar@gmail.com) wrote: > > 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. =A0Modern distros > > have a tmpfs mounted on /var/run at all phases of the boot, >=20 > 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). >=20 > So the question is - is all of this still going to work without this > bind mount? For now I don't think too many things will break if /var/run is not a tmpfs, and if /var/run is not bind mounted to /dev/.run. But sooner or later this will probably break... Lennart --=20 Lennart Poettering - Red Hat, Inc.