From: Paul Bender <pebender@san.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: systemd 183 and /lib/udev/devices/
Date: Sun, 27 May 2012 18:20:43 +0000 [thread overview]
Message-ID: <4FC2707B.2010807@san.rr.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1205271034530.1246@waverley.dhcp.wfu.edu>
On 5/27/2012 10:39 AM, Bryan Kadzban wrote:
> Tom Gundersen wrote:
>> On Sun, May 27, 2012 at 4:46 PM, Allin Cottrell<cottrell@wfu.edu>
>> wrote:
>>> 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?
>>
>> The mountpoints are created by systemd[0], so no need to do anything
>> to make this work.
>
> So... machines without systemd are screwed, unless they resurrect the
> bootscripts that copied these nodes, from way back before udevd started
> to do it itself?
Yes.
Whenever someone decides to violate the separation of utilities that
make Unix like distributions so powerful, the end user is harmed. This
is what the people behind systemd has chosen to do, yet falsely claim
otherwise (after all, if you cannot use udev without building the rest
of systemd, they are not separate).
Given its current direction, I suspect that systemd will suffer the some
fate as Hal. That is, it will become something that the community
rejects because it attempted to absorb everything. Unfortunately, end
users suffer in the mean time.
The sooner we fork udev, the better.
next prev parent reply other threads:[~2012-05-27 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 14:46 systemd 183 and /lib/udev/devices/ Allin Cottrell
2012-05-27 14:50 ` 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 [this message]
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=4FC2707B.2010807@san.rr.com \
--to=pebender@san.rr.com \
--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).