From: Piter PUNK <piterpunk@unitednerds.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Moving Ubuntu to upstream udev rules
Date: Sat, 20 Dec 2008 08:12:52 +0000 [thread overview]
Message-ID: <494CA904.7040300@unitednerds.org> (raw)
In-Reply-To: <1229669228.14012.30.camel@quest>
Kay Sievers wrote:
> On Fri, 2008-12-19 at 06:47 +0000, Scott James Remnant wrote:
>> additionally, we place these in the "audio" group
>>
>> SUBSYSTEM="rtc", GROUP="audio"
>
> Hmm, that sounds like a really weird workaround of some audio problem.
> Is this really what we want. :)
Only to know... why rtc in "audio" group?
>> ramdisk -> ram0
>> js* -> input/js* - aren't these different kernel drivers?
>
> I have no idea. Maybe remove them? Harald?
ramdisk -> ram0 --> link is on devices.txt
js -> input/js --> probably is wrong. js and input/js are from
different drivers
>> ftape -> qft0
devices.txt
>> permissions
>>
>> dri/card* 666 ???!!!
I think this is overwrited by xorg.conf setting i don't have any
rule changing this permission and ther permissions here are 660:
crw-rw---- 1 root video 226, 0 2008-12-20 03:33 /dev/dri/card0
I guess 660 is the default of Xorg without an Mode directive
in DRI section in xorg.conf. The "video" group here is from
one of few slackware custom rules. (maybe another one that
can vanishes in the air?)
>> tty 620 instead of 600? your ttys are writable?
>
> No idea. Just change it?
good to use "wall" and "write".
>> groups
>
>> no dialout group? - this may be Debianish, but we rely on it
>> nvram in group kmem not nvram?
Hmmmm... no dialout and no nvram group here.
nvram really needs an exclusive group?
> Thanks for doing this, lookingm forward to a more unified setup!
Closer and closer -:)
Piter PUNK
next prev parent reply other threads:[~2008-12-20 8:12 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 [this message]
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
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=494CA904.7040300@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).