From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Greg KH <greg@kroah.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: udev for dummies
Date: Sun, 14 Dec 2003 20:36:57 +0200 [thread overview]
Message-ID: <1071427017.17146.2.camel@nosferatu.lan> (raw)
In-Reply-To: <20031212213148.GA24643@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On Fri, 2003-12-12 at 23:31, Greg KH wrote:
> On Thu, Dec 11, 2003 at 11:16:04PM +0100, J.A. Magallon wrote:
> > Hi all...
> >
> > I am starting to use 2.6, and I really would like to use udev.
> > But I can't find a doc about how to move from taditional heavily
> > populated /dev to new method.
> >
> > Any pointer ?
>
> Did you read the README in udev's package?
>
> Anyway, I don't really recommend using udev for management of your /dev
> at this moment in time. In order to do this we need some more
> intregration of udev into the early boot process. People are working on
> this, but it will be a bit of time before it works properly, sorry.
>
It does work nicely to manage /dev if /dev is well populated as you
would have for a non-devfs system (yes, it does sort of defeat the
point, but the extra functionality of udev like changing the name
of a specific usb device, etc, makes up for the current 'bloat of
this approach).
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-14 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 22:16 udev for dummies J.A. Magallon
2003-12-11 22:59 ` David T Hollis
2003-12-12 2:49 ` Chris Friesen
2003-12-12 21:32 ` Greg KH
2003-12-12 4:43 ` Bob
2003-12-12 21:31 ` Greg KH
2003-12-14 18:36 ` Martin Schlemmer [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=1071427017.17146.2.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=greg@kroah.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.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