From: Lennart Poettering <lennart@poettering.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev runtime data will move from /dev/.udev/ to /dev/.run/udev/
Date: Thu, 17 Mar 2011 14:39:55 +0000 [thread overview]
Message-ID: <20110317143955.GA21600@tango.0pointer.de> (raw)
In-Reply-To: <AANLkTi=P5wbg5nO7ufsM-7ZntxunX4+HX18wpGnyjSkh@mail.gmail.com>
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. 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?
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
--
Lennart Poettering - Red Hat, Inc.
next prev parent reply other threads:[~2011-03-17 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 17:25 udev runtime data will move from /dev/.udev/ to /dev/.run/udev/ Kay Sievers
2011-03-15 17:38 ` Marco d'Itri
2011-03-15 23:07 ` Kay Sievers
2011-03-15 23:09 ` Marco d'Itri
2011-03-15 23:14 ` Kay Sievers
2011-03-16 0:09 ` Scott James Remnant
2011-03-16 0:20 ` Kay Sievers
2011-03-16 0:23 ` Scott James Remnant
2011-03-16 0:34 ` Scott James Remnant
2011-03-16 0:55 ` Kay Sievers
2011-03-16 1:11 ` Greg KH
2011-03-16 1:14 ` Scott James Remnant
2011-03-17 10:24 ` Andrey Borzenkov
2011-03-17 14:39 ` Lennart Poettering [this message]
2011-03-18 22:12 ` Scott James Remnant
2011-03-19 5:23 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110317143955.GA21600@tango.0pointer.de \
--to=lennart@poettering.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).