linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Greg KH <greg@kroah.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
	KML <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: devfsd/2.6.0-test1
Date: 21 Jul 2003 16:52:22 +0200	[thread overview]
Message-ID: <1058799142.5132.5.camel@workshop.saharacpt.lan> (raw)
In-Reply-To: <20030721143645.GA9480@kroah.com>

On Mon, 2003-07-21 at 16:36, Greg KH wrote:
> On Mon, Jul 21, 2003 at 12:48:56AM +0200, Martin Schlemmer wrote:
> > On Sun, 2003-07-20 at 19:17, Andrey Borzenkov wrote:
> > > > Also, read the threads on the list about udev/hotplug - apparently
> > > > devfsd is going out ...
> > > 
> > > as long as you have memory-based /dev you need devfsd even if it is called 
> > > differently.
> > >
> > 
> > I have not looked at it myself, but as far as I have it, you do not
> > mount /dev, and just need udev/hotplug/libsysfs (not sure on libsysfs).
> > Currently udev still call mknod, but I think Greg said he will fix that
> > in the future.
> 
> What's wrong with calling mknod?
> 
> I did say I thought about calling sys_mknod directly from udev, but
> that's just a minor change.  Is that what you were referring to?
> 

Yep.  Nothing major - I just want to remember somebody moaning
about too much overhead with udev spawning for every event in
/dev.


Cheers,

-- 
Martin Schlemmer



  reply	other threads:[~2003-07-21 14:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 17:17 devfsd/2.6.0-test1 Andrey Borzenkov
2003-07-20 22:48 ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-21 11:09   ` devfsd/2.6.0-test1 Rusty Russell
2003-07-21 14:36   ` devfsd/2.6.0-test1 Greg KH
2003-07-21 14:52     ` Martin Schlemmer [this message]
2003-07-21 15:02       ` devfsd/2.6.0-test1 Greg KH
     [not found] <200307172145.14681.arvidjaar@mail.ru>
2003-07-18 10:49 ` devfsd/2.6.0-test1 Mark Watts
  -- strict thread matches above, loose matches on Subject: below --
2003-07-17  9:17 devfsd/2.6.0-test1 Mark Watts
2003-07-17 10:02 ` devfsd/2.6.0-test1 Thierry Vignaud
2003-07-17 11:07   ` devfsd/2.6.0-test1 Mark Watts
2003-07-17 12:10 ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-17 22:39   ` devfsd/2.6.0-test1 Bill Davidsen
2003-07-20 16:27     ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-23 21:28       ` devfsd/2.6.0-test1 bill davidsen

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=1058799142.5132.5.camel@workshop.saharacpt.lan \
    --to=azarah@gentoo.org \
    --cc=arvidjaar@mail.ru \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).