linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: recent changes to udev
Date: Thu, 10 Nov 2005 01:39:31 +0000	[thread overview]
Message-ID: <1131586772.21401.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20051108184308.GB7254@vrfy.org>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

On Tue, 2005-11-08 at 19:43 +0100, Kay Sievers wrote:

>   /lib/udev/devices/
>      Real device nodes! Created with mknod, with the proper
>      permissions and ownership set. A bunch of symlinks and
>      nodes as a workaround for virtual devices or "broken"
>      kernel drivers. The whole content of this directory will
>      be copied over to the tmpfs mounted /dev at every boot
>      time.
>      If the user or a package has the need for a static node,
>      just place it there and it will be in /dev forever.
>      The reason for real nodes instead of a config file is that
>      using the "natural" interface to device nodes like mknod
>      chown, chmod is much easier to use than to invent another
>      file format. Also extendend attributes and ACL's may work
>      that way.
> 
Amusingly Debian policy currently forbids shipping device nodes in debs,
despite dpkg's reasonable support for them including dealing with
security implications.

I've dropped links.conf in the Ubuntu package though and am just going
to ship default device nodes in the package.

Scott
-- 
Scott James Remnant
scott@ubuntu.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-11-10  1:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 18:43 recent changes to udev Kay Sievers
2005-11-09 13:31 ` Dennis Veatch
2005-11-09 17:11 ` Kay Sievers
2005-11-09 17:41 ` Dennis Veatch
2005-11-10  1:39 ` Scott James Remnant [this message]

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=1131586772.21401.1.camel@localhost.localdomain \
    --to=scott@ubuntu.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).