From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: odd /dev/null beharvior
Date: Tue, 21 Feb 2006 02:20:08 +0000 (UTC) [thread overview]
Message-ID: <loom.20060221T031917-439@post.gmane.org> (raw)
In-Reply-To: 20060218213633.GC27035@rescomp.berkeley.edu
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
next prev parent reply other threads:[~2006-02-21 2:25 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
2006-02-21 2:20 ` James [this message]
2006-02-21 2:30 ` [gentoo-user] " 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=loom.20060221T031917-439@post.gmane.org \
--to=wireless@tampabay.rr.com \
--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