From: Jonathan Liu <net147@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 5/6] udev: do not create /var/volatile/run in init script
Date: Sun, 26 May 2013 21:13:05 +1000 [thread overview]
Message-ID: <1369566786-20341-6-git-send-email-net147@gmail.com> (raw)
In-Reply-To: <1369566786-20341-1-git-send-email-net147@gmail.com>
Previously in udev init, /var/volatile/run had to be created after
mounting all tmpfs filesystems so that udevd can write to /var/run
(a symbolic link to /var/volatile/run). This is because udev is
started before populate-volatile.sh.
Now that /var/run is a symbolic link to /run (a tmpfs filesystem),
/var/volatile/run doesn't need to be created anymore.
Signed-off-by: Jonathan Liu <net147@gmail.com>
---
meta/recipes-core/udev/udev/init | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-core/udev/udev/init b/meta/recipes-core/udev/udev/init
index cd87f50..95f9c03 100644
--- a/meta/recipes-core/udev/udev/init
+++ b/meta/recipes-core/udev/udev/init
@@ -50,7 +50,6 @@ case "$1" in
[ -e /dev/pts ] || mkdir -m 0755 /dev/pts
[ -e /dev/shm ] || mkdir -m 1777 /dev/shm
mount -a -t tmpfs 2>/dev/null
- mkdir -p /var/volatile/run
mkdir -p /var/volatile/tmp
# cache handling
--
1.8.2.3
next prev parent reply other threads:[~2013-05-26 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 11:13 [PATCH 0/6] base-files: add /run directory from FHS 3 draft specification Jonathan Liu
2013-05-26 11:13 ` [PATCH 1/6] " Jonathan Liu
2013-05-26 11:13 ` [PATCH 2/6] systemd: do not create /var/volatile/run and /var/volatile/lock Jonathan Liu
2013-05-26 11:13 ` [PATCH 3/6] systemd: do not create symbolic link from /run to /var/run Jonathan Liu
2013-05-26 11:13 ` [PATCH 4/6] systemd: remove old /var/run workarounds Jonathan Liu
2013-05-26 11:13 ` Jonathan Liu [this message]
2013-05-26 11:13 ` [PATCH 6/6] udev: do not create symbolic link from /run to /var/run Jonathan Liu
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=1369566786-20341-6-git-send-email-net147@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.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