Willie Wong <wwong <at> Princeton.EDU> writes:
> On Wed, Jun 28, 2006 at 03:04:55AM +0000, Penguin Lover James squawked: > > Well I put udev in my /etc/portage/package.keyworks to get the latest > > version, thinking that might fix the problem. It do not. > I don't think that's necessary. It works perfectly fine on my system > with udev-087. Agreed. Since it did not fix the problem, I remerged udev-087-r1. > Could something else be setting the MODE/GROUP lines for those > devices? How'bout grepping for tty and null in other rule files? Good question. Nothing I have intentionally done. None of the other rules files in /etc/udev/rules.d contain any string matches as you suggest, except those listed in the previous resonse, found in 50-udev.rules. > What about /etc/conf.d/rc? Maybe you can toggle RC_DEVICES="udev" and > set RC_DEVICE_TARBALL="no"? (or maybe setting it to "yes" might give > you a work around?) Here's what I found: RC_DEVICES="auto" RC_DEVICE_TARBALL="no" I'm going to play around with these and test; results to follow. > > # egrep tty 50-udev.rules <shows these lines> > The lines look the same as mine. Assuming you've been deligent about > updating the config files in /etc, I don't see a reason why the > default rule files provide by udev would be different. yes, I rsync emerge and update regularly (daily) almost. > > It looks as though the (mode) permissions and groups are getting > > set per the udev files? > Are they? I thought your problem is that the permissions and groups > were set different from what was specified in the rule files... It was a rethorical question. I should have stated: It looks as though the (mode) permissions and groups are not getting set per the udev files, or did I miss something? James James -- gentoo-user@gentoo.org mailing list
