linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piter PUNK <piterpunk@unitednerds.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Moving Ubuntu to upstream udev rules
Date: Sun, 21 Dec 2008 21:52:56 +0000	[thread overview]
Message-ID: <494EBAB8.4000206@unitednerds.org> (raw)
In-Reply-To: <1229669228.14012.30.camel@quest>

Kay Sievers wrote:
> On Fri, Dec 19, 2008 at 17:03, Kay Sievers <kay.sievers@vrfy.org> wrote:
> # is it /devsr0 or /dev/sdc0?
> SUBSYSTEM="block", KERNEL="sr[0-9]*", NAME="scd%n", SYMLINK+="sr%

I think it's OK. From devices.txt:

---
The prefix /dev/sr (instead of /dev/scd) has been deprecated.
( ... )
(in recommended links)
/dev/scd?       sr?             hard            Alternate SCSI CD-ROM name
---

The recommendation is to have a hardlink here. But i think symlink is OK.

> # rtc in group "audio"?
> SUBSYSTEM="rtc", GROUP="audio"

To me, this is still very bizarre.

> # which ones do we need, not need?
+ X0R -> null
+ ramdisk -> ram0
o ram -> ram1
x lirc -> lirc0
x vbi -> vbi0
+ radio -> radio0
x video -> video0
x fb -> fb0
+ ftape -> qft0
x sbpcd -> sbpcd0
o xpram* -> slram*

The ones with + are from devices.txt.

The links mark with x I thought they can still
be there. Is common to point the /dev/foo symlink
to the current /dev/fooN that's in use (usually
the first one, foo0). If user don't wants these links
he can always overwrite those links with custom rules
in /etc/udev/rules.d.

I don't know about the ones I mark with o.

> # group nvram needed?
> nvram GROUP="nvram"
> 
> # what are the right permissions?
> fuse GROUP="666"
> tty[0-9]* GROUP="600"

I like tty with MODE="0620". But 600 isn't bad.

The udev rules shipped with fuse-2.7.4 have
MODE="0666" in there. Maybe isn't better to leave
this to fuse package?

Piter PUNK

  parent reply	other threads:[~2008-12-21 21:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  6:47 Moving Ubuntu to upstream udev rules Scott James Remnant
2008-12-19 16:03 ` Kay Sievers
2008-12-19 16:10 ` Marco d'Itri
2008-12-20  8:12 ` Piter PUNK
2008-12-20  8:41 ` Robby Workman
2008-12-20 11:30 ` Marco d'Itri
2008-12-20 18:33 ` Dan Nicholson
2008-12-21 12:39 ` Kay Sievers
2008-12-21 12:42 ` Kay Sievers
2008-12-21 12:53 ` Kay Sievers
2008-12-21 13:07 ` Marco d'Itri
2008-12-21 14:29 ` Kay Sievers
2008-12-21 21:52 ` Piter PUNK [this message]
2008-12-22  2:00 ` Kay Sievers
2008-12-22  8:41 ` Harald Hoyer
2008-12-22  8:53 ` Harald Hoyer
2008-12-22  9:39 ` Scott James Remnant
2008-12-22 10:00 ` Bernhard Walle
2008-12-22 11:57 ` Marco d'Itri
2008-12-22 12:37 ` Kay Sievers
2008-12-22 12:39 ` Scott James Remnant
2008-12-22 12:40 ` Kay Sievers
2008-12-22 12:42 ` Kay Sievers
2008-12-22 12:43 ` Kay Sievers
2008-12-22 13:57 ` Kay Sievers
2008-12-25 23:26 ` Karel Zak
2008-12-25 23:39 ` Kay Sievers
2008-12-26  0:26 ` Karel Zak
2008-12-26  0:48 ` Kay Sievers

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=494EBAB8.4000206@unitednerds.org \
    --to=piterpunk@unitednerds.org \
    --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).