From mboxrd@z Thu Jan 1 00:00:00 1970 From: Piter PUNK Date: Sat, 20 Dec 2008 08:12:52 +0000 Subject: Re: Moving Ubuntu to upstream udev rules Message-Id: <494CA904.7040300@unitednerds.org> List-Id: References: <1229669228.14012.30.camel@quest> In-Reply-To: <1229669228.14012.30.camel@quest> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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