linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Moving Ubuntu to upstream udev rules
Date: Sat, 20 Dec 2008 11:30:11 +0000	[thread overview]
Message-ID: <20081220113011.GA25293@bongo.bofh.it> (raw)
In-Reply-To: <1229669228.14012.30.camel@quest>

On Dec 20, Piter PUNK <piterpunk@unitednerds.org> wrote:

> Only to know... why rtc in "audio" group?
Because it was needed by mplayer and it's a good approximation of users
with local console access.

> Re nvram group, I don't see why it shouldn't be root or kmem - is
> there a legitimate reason why a normal user should have write access
> to /dev/nvram?
I remember some thinkpad-specific application, for a start.

-- 
ciao,
Marco

  parent reply	other threads:[~2008-12-20 11:30 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 [this message]
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
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=20081220113011.GA25293@bongo.bofh.it \
    --to=md@linux.it \
    --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).