| 1 |
On Wed, Jun 28, 2006 at 03:04:55AM +0000, Penguin Lover James squawked: |
| 2 |
> Well I put udev in my /etc/portage/package.keyworks to get the latest |
| 3 |
> version, thinking that might fix the problem. It do not. |
| 4 |
|
| 5 |
I don't think that's necessary. It works perfectly fine on my system |
| 6 |
with udev-087. |
| 7 |
|
| 8 |
Could something else be setting the MODE/GROUP lines for those |
| 9 |
devices? How'bout grepping for tty and null in other rule files? |
| 10 |
|
| 11 |
What about /etc/conf.d/rc? Maybe you can toggle RC_DEVICES="udev" and |
| 12 |
set RC_DEVICE_TARBALL="no"? (or maybe setting it to "yes" might give |
| 13 |
you a work around?) |
| 14 |
> |
| 15 |
> |
| 16 |
> |
| 17 |
> # egrep tty 50-udev.rules <shows these lines> |
| 18 |
> |
| 19 |
<snip> |
| 20 |
> |
| 21 |
> Want to suggest specific changes to which lines? |
| 22 |
|
| 23 |
The lines look the same as mine. Assuming you've been deligent about |
| 24 |
updating the config files in /etc, I don't see a reason why the |
| 25 |
default rule files provide by udev would be different. |
| 26 |
|
| 27 |
> It looks as though the (mode) permissions and groups are getting |
| 28 |
> set per the udev files? |
| 29 |
|
| 30 |
Are they? I thought your problem is that the permissions and groups |
| 31 |
were set different from what was specified in the rule files... |
| 32 |
|
| 33 |
Best, |
| 34 |
|
| 35 |
W |
| 36 |
-- |
| 37 |
Two people turned in problem set 12 without indicating their names! |
| 38 |
This is true scholarship, done for it's own sake and not for |
| 39 |
material advantage, like a grade. |
| 40 |
It is an honor to be associated with such nobility of soul. |
| 41 |
~Prof. Kirk T. McDonald, DeathEM'03 |
| 42 |
Sortir en Pantoufles: up 18 days, 6:34 |
| 43 |
-- |
| 44 |
gentoo-user@g.o mailing list |
Archives