From: "Marco d'Itri" <md@linux.it>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev runtime data will move from /dev/.udev/ to /dev/.run/udev/
Date: Tue, 15 Mar 2011 23:09:17 +0000 [thread overview]
Message-ID: <20110315230917.GA13932@bongo.bofh.it> (raw)
In-Reply-To: <AANLkTi=P5wbg5nO7ufsM-7ZntxunX4+HX18wpGnyjSkh@mail.gmail.com>
On Mar 16, Kay Sievers <kay.sievers@vrfy.org> 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.
> > This looks complex and requiring coordination among multiple packages.
> > Where is the documentation of everything which needs to be done by the
> > surrounding boot scripts?
> I can't know, or document anything. The init scripts I maintain do not
> know anything about /dev/.udev/.
I am talking about this new /dev/.run/ thing. Where is it documented?
--
ciao,
Marco
next prev parent reply other threads:[~2011-03-15 23:09 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 [this message]
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
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=20110315230917.GA13932@bongo.bofh.it \
--to=md@linux.it \
--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).