From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How do I use 2.6.14 and remove udev and go back to devfs
Date: Wed, 16 Nov 2005 16:59:47 -0700 [thread overview]
Message-ID: <7573e9640511161559r1a0f138fgac69c71aa079c45a@mail.gmail.com> (raw)
In-Reply-To: <1132180473.16153.12.camel@rattus>
On 11/16/05, William Kenworthy <billk@iinet.net.au> wrote:
> Yes udev works, however works well is something else entirely. Udev has
> been the bane of my life a number of times - at least with devfs I had a
> chance of working it out. It often seems like we take two steps back
> with every new approach, and take a lot of pain just to get back to
> where we were.
That's probably because you don't really see the value of udev.
Looking at my 10-local.rules, I have rules that:
1. ensure that whatever wireless card I decide to plugin becomes
"wlan", instead of eth0, ath0, or wlan0.
2. Makes all of my usb media devices (flash disks, 2.5in hard disks,
3.5in HDs, and media reader) show up at persistent nodes, instead of
sdX devices where X depends on what devices are connected and the
order that they are turned on.
Neither of the above is possible with a static configuration or devfs.
Yes, there are problems from time to time (like when all of the devfs
compatibility nodes were removed!). But I've never had a problem
debugging what udev was doing (set udev_log in udev.conf and watch
/var/log/messages).
-Richard
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-11-17 0:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 7:56 [gentoo-user] How do I use 2.6.14 and remove udev and go back to devfs Daevid Vincent
2005-11-16 8:16 ` Dirk Heinrichs
2005-11-16 8:22 ` W.Kenworthy
2005-11-16 8:42 ` Dirk Heinrichs
2005-11-16 8:49 ` Dirk Heinrichs
2005-11-16 9:19 ` brullo nulla
2005-11-16 9:33 ` Dirk Heinrichs
2005-11-16 16:26 ` Richard Fish
2005-11-16 22:34 ` William Kenworthy
2005-11-16 23:59 ` Richard Fish [this message]
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=7573e9640511161559r1a0f138fgac69c71aa079c45a@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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