mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Cormack <justin@street-vision.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Ed Sweetman <ed.sweetman@wmich.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: devfs to be obsloted by udev?
Date: 03 Sep 2003 10:38:48 +0100	[thread overview]
Message-ID: <1062581929.30060.197.camel@lotte.street-vision.com> (raw)
In-Reply-To: <200309022219.02549.bzolnier@elka.pw.edu.pl>

On Tue, 2003-09-02 at 21:19, Bartlomiej Zolnierkiewicz wrote:
> 
> initramfs

which seems to have been postponed to 2.7.


> On Tuesday 02 of September 2003 16:09, Ed Sweetman wrote:
> > It appears that devfs is to be replaced by the use of udev in the not so
> > distant future.  I'm not sure how it's supposed to replace a static /dev
> > situaton seeing as how it is a userspace daemon.  Is it not supposed to
> > replace /dev even when it's completed?  I dont see the real benefit in
> > having two directories that basically give the same info.  Right now we
> > have something like that with proc and sysfs although not everything in
> > proc makes sense to be in sysfs and both are virtual fs's where as /dev
> > is a static fs on the disk that takes up space and inodes and includes
> > way too many files that a system may not use.  If udev is to take over
> > the job of devfs, how will modules and drivers work that require device
> > files to be present in order to work since undoubtedly the udev daemon
> > will have to wait until the kernel is done booting before being run.
> >
> > I'm just not following how it is going to replace devfs and thus why
> > devfs is being abandoned as mentioned in akpm's patchset. Or as it
> > seems, already has been abandoned.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2003-09-03  9:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 14:09 Ed Sweetman
2003-09-02 18:20 ` Greg KH
2003-09-02 14:32   ` Ed Sweetman
2003-09-02 18:44     ` Greg KH
2003-09-02 23:56     ` Kurt Wall
2003-09-02 20:19 ` Bartlomiej Zolnierkiewicz
2003-09-03  9:38   ` Justin Cormack [this message]
2003-09-03 18:41     ` Greg KH
2003-09-03 19:06       ` Bryan O'Sullivan
2003-09-03 19:17       ` Sam Ravnborg
2003-09-03 21:09         ` Bryan O'Sullivan

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=1062581929.30060.197.camel@lotte.street-vision.com \
    --to=justin@street-vision.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=ed.sweetman@wmich.edu \
    --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

all inboxes | Powered by JetHome®