From: Christopher Cowart <ccowart@rescomp.berkeley.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] odd /dev/null beharvior
Date: Sat, 18 Feb 2006 13:36:33 -0800 [thread overview]
Message-ID: <20060218213633.GC27035@rescomp.berkeley.edu> (raw)
In-Reply-To: <loom.20060218T174357-39@post.gmane.org>
[-- 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 --]
next prev parent reply other threads:[~2006-02-18 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 16:46 [gentoo-user] odd /dev/null beharvior James
2006-02-18 17:29 ` Rafael Bugajewski
2006-02-18 21:36 ` Christopher Cowart [this message]
2006-02-21 2:20 ` [gentoo-user] " James
2006-02-21 2:30 ` James
2006-02-21 23:50 ` Christopher Cowart
2006-02-22 2:39 ` James
2006-02-24 12:02 ` Christopher Cowart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060218213633.GC27035@rescomp.berkeley.edu \
--to=ccowart@rescomp.berkeley.edu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox