| 1 |
I've experienced this problem before. The developers insist the ebuild |
| 2 |
is absolutely correct, but it doesn't always attempt to migrate conf |
| 3 |
changes to /etc/udev. |
| 4 |
|
| 5 |
The easiest way to fix this problem permanently is to |
| 6 |
$ sudo rm /etc/udev/{permissions,rules}.d/50-* |
| 7 |
$ sudo emerge -av udev |
| 8 |
|
| 9 |
This will blow away the default udev conf files that are causing you |
| 10 |
problems, then re-emerge udev. The updated defaults will be installed in |
| 11 |
the right place. This assumes you haven't touched the 50-* files (you |
| 12 |
put all custom changes in 10-local, right). |
| 13 |
|
| 14 |
-Chris |
| 15 |
|
| 16 |
|
| 17 |
On 16:46 Sat 18 Feb , James wrote: |
| 18 |
> Hello, |
| 19 |
> |
| 20 |
> /dev/null is acting weird. The permissions have recently changes |
| 21 |
> on a system I sync regularly. I can change the permissions back |
| 22 |
> to 666, but every time the system reboots, dev null resets to: |
| 23 |
> crw-rw---- 1 root 1, 3 Jan 20 10:05 /dev/null |
| 24 |
> |
| 25 |
> How to I make permanent changes so that /dev/null is 666 again? |
| 26 |
> |
| 27 |
> Surely this is not part of some security issue that I missed? |
| 28 |
> |
| 29 |
> James |
| 30 |
> |
| 31 |
> |
| 32 |
> |
| 33 |
> -- |
| 34 |
> gentoo-user@g.o mailing list |
| 35 |
> |
| 36 |
|
| 37 |
-- |
| 38 |
Christopher Cowart |
| 39 |
Unix Systems Administrator |
| 40 |
Residential Computing, UC Berkeley |
| 41 |
"May all your pushes be popped" |
Archives