From: Matt Mackall <mpm@selenic.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] ndevfs - a "nano" devfs
Date: Sat, 25 Jun 2005 15:15:16 -0700 [thread overview]
Message-ID: <20050625221516.GD14426@waste.org> (raw)
In-Reply-To: <20050624081808.GA26174@kroah.com>
On Fri, Jun 24, 2005 at 01:18:08AM -0700, Greg KH wrote:
> Now I just know I'm going to regret this somehow...
>
> Anyway, here's yet-another-ramfs-based filesystem, ndevfs. It's a very
> tiny:
> $ size fs/ndevfs/inode.o
> text data bss dec hex filename
> 1571 200 8 1779 6f3 fs/ndevfs/inode.o
> replacement for devfs for those embedded users who just can't live
> without the damm thing. It doesn't allow subdirectories, and only uses
> LSB compliant names. But it works, and should be enough for people to
> use, if they just can't wean themselves off of the idea of an in-kernel
> fs to provide device nodes.
>
> Now, with this, is there still anyone out there who just can't live
> without devfs in their kernel?
>
> Damm, the depths I've sunk to these days, I'm such a people pleaser...
Hmm. I'm not pleased. Perhaps you're pleasing the wrong people?
What we really need is a short HOWTO that covers:
- Do you really need a dynamic /dev?
- How to embed a static /dev in your embedded kernel with initramfs
- How to add a dynamic /dev to your kernel with udev
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-06-25 22:15 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 8:18 [ANNOUNCE] ndevfs - a "nano" devfs Greg KH
2005-06-24 12:23 ` Michael Tokarev
2005-06-24 15:16 ` Greg KH
2005-06-24 15:40 ` Michael Tokarev
2005-06-24 16:26 ` Greg KH
2005-06-24 14:32 ` Bill Gatliff
2005-06-24 15:17 ` Steven Rostedt
2005-06-24 15:20 ` Greg KH
2005-06-24 17:10 ` Michael Tokarev
2005-06-24 17:10 ` Bill Gatliff
2005-06-28 7:40 ` Greg KH
2005-06-24 19:05 ` Mike Bell
2005-06-24 21:55 ` J.A. Magallon
2005-06-24 19:22 ` Alexey Dobriyan
2005-06-25 0:57 ` Kyle Moffett
2005-06-25 7:37 ` Denis Vlasenko
2005-06-28 7:41 ` Greg KH
2005-06-28 19:56 ` Tom Rini
2005-06-28 21:08 ` Olaf Hering
2005-06-28 21:25 ` Tom Rini
2005-06-28 22:08 ` Michael Tokarev
2005-06-28 22:23 ` Tom Rini
2005-06-25 22:15 ` Matt Mackall [this message]
2005-06-25 23:43 ` Greg KH
2005-06-26 8:23 ` Russell King
2005-06-28 3:36 ` Greg KH
2005-06-27 7:19 ` Mike Bell
2005-06-27 22:35 ` Dmitry Torokhov
2005-06-27 23:26 ` Mike Bell
2005-06-28 7:40 ` Greg KH
2005-06-28 9:08 ` Mike Bell
2005-06-28 9:21 ` Arjan van de Ven
2005-06-28 9:40 ` Mike Bell
2005-06-28 21:49 ` Jim Crilly
2005-06-28 22:23 ` Mike Bell
2005-06-28 23:43 ` Jim Crilly
2005-06-29 0:12 ` Mike Bell
2005-06-29 0:39 ` David Lang
2005-06-29 0:53 ` Mike Bell
2005-06-28 12:00 ` Oliver Neukum
2005-06-28 20:08 ` Greg KH
2005-06-29 6:41 ` Oliver Neukum
2005-06-29 16:06 ` Greg KH
2005-06-29 16:22 ` Oliver Neukum
[not found] ` <200506270819.20108.arnd@arndb.de>
2005-06-28 3:46 ` Greg KH
[not found] <OF831AC472.851744FE-ON8025702A.004A57EC-8025702A.004B5AE9@sophos.com>
2005-06-24 15:23 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-06-24 15:32 tvrtko.ursulin
2005-06-24 16:27 ` Greg KH
2005-06-27 15:21 Adam J. Richter
2005-06-27 23:27 ` J.A. Magallon
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=20050625221516.GD14426@waste.org \
--to=mpm@selenic.com \
--cc=greg@kroah.com \
--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