[gentoo-user] odd /dev/null beharvior

[gentoo-user] odd /dev/null beharvior

[James]

Hello,

/dev/null is acting weird. The permissions have recently changes
on a system I sync regularly. I can change the permissions back
to 666, but every time the system reboots, dev null resets to:
crw-rw----  1 root 1, 3 Jan 20 10:05 /dev/null

How to I make permanent changes so that /dev/null is 666 again?

Surely this is not part of some security issue that I missed?

James



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] odd /dev/null beharvior

[Rafael Bugajewski]

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

18. Februar 2006 17:46, James:

> /dev/null is acting weird. The permissions have recently changes
> on a system I sync regularly. I can change the permissions back
> to 666, but every time the system reboots, dev null resets to:
> crw-rw----  1 root 1, 3 Jan 20 10:05 /dev/null
>
> How to I make permanent changes so that /dev/null is 666 again?
>
> Surely this is not part of some security issue that I missed?

Hi James,

I hope the following two lines will help you:

rafael@hoppsie / $ grep null /etc/udev/rules.d/50-udev.rules
KERNEL=="null",         NAME="%k", MODE="0666"

I think it's rather a misconfiguration than a security issue.

Greets,

Rafael Bugajewski

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] odd /dev/null beharvior

[Christopher Cowart]

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

I've experienced this problem before. The developers insist the ebuild
is absolutely correct, but it doesn't always attempt to migrate conf
changes to /etc/udev.

The easiest way to fix this problem permanently is to
$ sudo rm /etc/udev/{permissions,rules}.d/50-*
$ sudo emerge -av udev

This will blow away the default udev conf files that are causing you
problems, then re-emerge udev. The updated defaults will be installed in
the right place. This assumes you haven't touched the 50-* files (you
put all custom changes in 10-local, right).

-Chris


On 16:46 Sat 18 Feb     , James wrote:
> Hello,
> 
> /dev/null is acting weird. The permissions have recently changes
> on a system I sync regularly. I can change the permissions back
> to 666, but every time the system reboots, dev null resets to:
> crw-rw----  1 root 1, 3 Jan 20 10:05 /dev/null
> 
> How to I make permanent changes so that /dev/null is 666 again?
> 
> Surely this is not part of some security issue that I missed?
> 
> James
> 
> 
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 

-- 
Christopher Cowart
Unix Systems Administrator
Residential Computing, UC Berkeley
"May all your pushes be popped"

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: odd /dev/null beharvior

[James]

Christopher Cowart <ccowart <at> rescomp.berkeley.edu> writes:


> The easiest way to fix this problem permanently is to
> $ sudo rm /etc/udev/{permissions,rules}.d/50-*
> $ sudo emerge -av udev

> This will blow away the default udev conf files that are causing you
> problems, then re-emerge udev. The updated defaults will be installed in
> the right place. This assumes you haven't touched the 50-* files (you
> put all custom changes in 10-local, right).

Nope,


I'll give this a whirl and let you know....

thanks,

James

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: odd /dev/null beharvior

[James]

Christopher Cowart <ccowart <at> rescomp.berkeley.edu> writes:


> The easiest way to fix this problem permanently is to
> $ sudo rm /etc/udev/{permissions,rules}.d/50-*
> $ sudo emerge -av udev

> This will blow away the default udev conf files that are causing you
> problems, then re-emerge udev. The updated defaults will be installed in
> the right place. This assumes you haven't touched the 50-* files (you
> put all custom changes in 10-local, right).


Nope, Here's what I get:

!!! Digest verification Failed:
!!!    /usr/portage/sys-fs/udev/files/udev.permissions
!!! Reason: Filesize does not match recorded size

>>> Please ensure you have sync'd properly. Please try 'emerge sync' and
>>> optionally examine the file(s) for corruption. A sync will fix most cases.


Now I've unmerge udev, and sync'd twice....

Ideas?


James



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: odd /dev/null beharvior

[Christopher Cowart]

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

Sounds like this is related to the bug that's in an earlier thread.

Do as root:
# ebuild `equery which udev` digest

This will update the digest for now. The changes will be overwritten the
next time you sync portage, but it won't matter til the next time you
emerge udev. At which time, hopefully they'll have it fixed in portage.

-Chris


On 02:30 Tue 21 Feb     , James wrote:
> Christopher Cowart <ccowart <at> rescomp.berkeley.edu> writes:
> 
> 
> > The easiest way to fix this problem permanently is to
> > $ sudo rm /etc/udev/{permissions,rules}.d/50-*
> > $ sudo emerge -av udev
> 
> > This will blow away the default udev conf files that are causing you
> > problems, then re-emerge udev. The updated defaults will be installed in
> > the right place. This assumes you haven't touched the 50-* files (you
> > put all custom changes in 10-local, right).
> 
> 
> Nope, Here's what I get:
> 
> !!! Digest verification Failed:
> !!!    /usr/portage/sys-fs/udev/files/udev.permissions
> !!! Reason: Filesize does not match recorded size
> 
> >>> Please ensure you have sync'd properly. Please try 'emerge sync' and
> >>> optionally examine the file(s) for corruption. A sync will fix most cases.
> 
> 
> Now I've unmerge udev, and sync'd twice....
> 
> Ideas?
> 
> 
> James
> 
> 
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 

-- 
Christopher Cowart
Unix Systems Administrator
Residential Computing, UC Berkeley
"May all your pushes be popped"

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: odd /dev/null beharvior

[James]

Christopher Cowart <ccowart <at> rescomp.berkeley.edu> writes:


> Sounds like this is related to the bug that's in an earlier thread.

> Do as root:
> # ebuild `equery which udev` digest

>>> Generating digest file...
<<< udev-079.tar.bz2
>>> Generating manifest file...
<<< ChangeLog
<<< files/05-udev-early.rules-078
<<< files/05-udev-early.rules-079
<<< files/digest-udev-068-r1
<<< files/digest-udev-069
<<< files/digest-udev-070-r1
<<< files/digest-udev-071
<<< files/digest-udev-072
<<< files/digest-udev-073
<<< files/digest-udev-077
<<< files/digest-udev-077-r1
<<< files/digest-udev-077-r2
<<< files/digest-udev-077-r3
<<< files/digest-udev-077-r4
<<< files/digest-udev-077-r5
<<< files/digest-udev-078
<<< files/digest-udev-079
<<< files/digest-udev-079-r1
<<< files/digest-udev-081
<<< files/digest-udev-081-r1
<<< files/digest-udev-084
<<< files/udev-021-udev_add_c-gcc295-compat.patch
<<< files/udev-050-udev_volume_id.patch
<<< files/udev-parisc-path_id-again.patch
<<< files/udev-parisc-path_id.patch
<<< files/udev-start-077-r2.sh
<<< files/udev-start-077-r4.sh
<<< files/udev-start-077.sh
<<< files/udev-start-079.sh
<<< files/udev-start.sh
<<< files/udev-stop.sh
<<< files/udev.conf
<<< files/udev.conf.post_024
<<< files/udev.conf.post_046
<<< files/udev.conf.post_050
<<< files/udev.conf.post_059
<<< files/udev.conf.post_081
<<< files/udev.hotplug.empty
<<< files/udev.permissions
<<< files/udev.rules
<<< files/udev.rules-018
<<< files/udev.rules-064-r1
<<< files/udev.rules-077
<<< files/udev.rules-077-r1
<<< files/udev.rules-077-r5
<<< files/udev.rules-078
<<< files/udev.rules-084
<<< files/udev.rules.post_012
<<< metadata.xml
<<< udev-068-r1.ebuild
<<< udev-069.ebuild
<<< udev-070-r1.ebuild
<<< udev-071.ebuild
<<< udev-072.ebuild
<<< udev-073.ebuild
<<< udev-077-r1.ebuild
<<< udev-077-r2.ebuild
<<< udev-077-r3.ebuild
<<< udev-077-r4.ebuild
<<< udev-077-r5.ebuild
<<< udev-077.ebuild
<<< udev-078.ebuild
<<< udev-079-r1.ebuild
<<< udev-079.ebuild
<<< udev-081-r1.ebuild
<<< udev-081.ebuild
<<< udev-084.ebuild
>>> Computed message digests.

> This will update the digest for now. The changes will be overwritten the
> next time you sync portage, but it won't matter til the next time you
> emerge udev. At which time, hopefully they'll have it fixed in portage.

WEll in 'unmerge' the udev, so now I have to keep the system online
until an emerge sync brings a new, installable udev. I even tried to
got back to udev-079, but that would not install either....

ideas? which bug do I watch for resolution?


James

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: odd /dev/null beharvior

[Christopher Cowart]

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]

According to: http://bugs.gentoo.org/show_bug.cgi?id=123249

The problem has been resolved. You should try
# emerge sync
# emerge -C udev
# rm -f /etc/udev/permissions.d/50-udev.permissions
# rm -f /etc/udev/rules.d/50-udev.rules
# emerge -av udev

If you still experience digest problems, reopen that bug and include any
relevant information.

-Chris
 

-- 
Christopher Cowart
Unix Systems Administrator
Residential Computing, UC Berkeley
"May all your pushes be popped"

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]