public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jon Portnoy <avenj@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] udev implementation
Date: Tue, 21 Oct 2003 03:49:08 -0400	[thread overview]
Message-ID: <20031021074908.GA17002@cerberus.oppresses.us> (raw)
In-Reply-To: <20031021074313.GB16951@netswarm.net>

On Tue, Oct 21, 2003 at 09:43:13AM +0200, Christian Birchinger wrote:
> You're totaly right. udev is really not usable yet. I was happy
> when i first saw the planed features. But once i got the
> FAQ/Docs i was really disapointed. And this disapointment
> increased after i downloaded the tarball.
> 
> I highly suggest not moving to udev yet. Even if devfs is marked
> obsolete in kernel it's far better than udev which is in alpha
> state. Ofcourse one day we will ne forced to adopt udev so it's
> not a bad idea to check it out etc. but please don't switch to
> it now. It's really not ready and causes far more problems than
> devfs.
> 

As far as I know, there are currently no plans to move to udev as 
default for a while.

We do, however, have to have support for it, especially for archs like 
AMD64 - 2.4.23-pre* removes devfs for AMD64 due to bugs.

I, personally, think udev sucks and will really miss devfs.

-- 
Jon Portnoy
avenj/irc.freenode.net

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-10-21  7:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  5:56 [gentoo-dev] udev implementation C. Brewer
2003-10-21  6:17 ` Jon Portnoy
2003-10-21 15:14   ` C. Brewer
2003-10-21 17:09     ` Jon Portnoy
2003-10-21  7:43 ` Christian Birchinger
2003-10-21  7:49   ` Jon Portnoy [this message]
2003-10-21  8:01 ` Ernst Herzberg
2003-10-21 20:36 ` Martin Schlemmer
2003-10-21 21:45   ` C. Brewer
2003-10-22  2:33     ` Mike Frysinger
2003-10-22  2:50       ` C. Brewer
2003-10-22  4:27     ` Martin Schlemmer

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=20031021074908.GA17002@cerberus.oppresses.us \
    --to=avenj@gentoo.org \
    --cc=gentoo-dev@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