All of lore.kernel.org
 help / color / mirror / Atom feed
From: Allin Cottrell <cottrell@wfu.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: systemd 183 and /lib/udev/devices/
Date: Sun, 27 May 2012 20:51:33 +0000	[thread overview]
Message-ID: <alpine.LFD.2.01.1205271647120.9130@myrtle> (raw)
In-Reply-To: <alpine.LNX.2.01.1205271034530.1246@waverley.dhcp.wfu.edu>

On Sun, 27 May 2012, Kay Sievers wrote:

> On Sun, May 27, 2012 at 4:46 PM, Allin Cottrell <cottrell@wfu.edu> wrote:
>> 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?
>
> The only one still known is the parport driver, where cups might rely
> on module-autoloading by accessing of /dev/lp0.
>
> There are around 3 users in the world which need that. :)

Fine, I'm not one of them.

>> I'm currently running systemd 44 and udev 182 (without init 
>> scripts) and I have "pts" and "shm" under /lib/udev/devices/. 
>> [...]
>
> How can you run udev without an init script?

I mean with a scriptless systemd setup.

Allin Cottrell

  parent reply	other threads:[~2012-05-27 20:51 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
2012-05-27 20:00 ` Greg KH
2012-05-27 20:14 ` Kay Sievers
2012-05-27 20:51 ` Allin Cottrell [this message]
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.LFD.2.01.1205271647120.9130@myrtle \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.