From: Allin Cottrell <cottrell@wfu.edu>
To: linux-hotplug@vger.kernel.org
Subject: systemd 183 and /lib/udev/devices/
Date: Sun, 27 May 2012 14:46:10 +0000 [thread overview]
Message-ID: <alpine.LNX.2.01.1205271034530.1246@waverley.dhcp.wfu.edu> (raw)
I see in the NEWS file:
"udev: /lib/udev/devices/ are not read anymore;
systemd-tmpfiles should be used to create dead device nodes as
workarounds for broken subsystems."
What sort of "broken subsystems" are we talking about here?
I'm currently running systemd 44 and udev 182 (without init
scripts) and I have "pts" and "shm" under /lib/udev/devices/.
There's no reference to /dev/pts or /dev/shm in fstab, but at
run time /dev/pts is populated and there's a tmpfs mounted on
/dev/shm. How can I tell whether I need the systemd-tmpfiles
workaround? Thanks.
Allin Cottrell
next reply other threads:[~2012-05-27 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 14:46 Allin Cottrell [this message]
2012-05-27 14:50 ` systemd 183 and /lib/udev/devices/ Tom Gundersen
2012-05-27 16:17 ` Allin Cottrell
2012-05-27 16:24 ` Tom Gundersen
2012-05-27 17:39 ` Bryan Kadzban
2012-05-27 18:20 ` Paul Bender
2012-05-27 20:00 ` Greg KH
2012-05-27 20:14 ` Kay Sievers
2012-05-27 20:51 ` Allin Cottrell
2012-05-28 4:45 ` Robby Workman
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=alpine.LNX.2.01.1205271034530.1246@waverley.dhcp.wfu.edu \
--to=cottrell@wfu.edu \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).