public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Valette <eric.valette@free.fr>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: updating kernel to 2.6.13-rc1 from 2.6.12 + CONFIG_DEVFS_FS + empty /dev
Date: Sat, 02 Jul 2005 09:22:20 +0200	[thread overview]
Message-ID: <42C640AC.1020602@free.fr> (raw)
In-Reply-To: <20050702053711.GA5635@kroah.com>

Greg KH wrote:

> Why?  Why not put it in ROM with your kernel image, look at how the
> kernel build process does it with the "built-in" initramfs.

Well, nowadays, most system have only flash because ROM does not enable
to do firmware upgrade. Second, putting it in the kernel or as a
separate flash section or in an initrd does not change the problem :
something has to be stored on non volatile memory whereas you do not
need that for devfs (except devfs code itself of course) but then you
have udev instead of devfs...

> I boot my boxes with nothing in /dev and have been for almost a year
> now.  udev works just fine for this, and so do some other programs that
> work like udev does.

Nothing in /dev but with initramfs. Same cost...

BTW : valette@tri-yann->df /dev
Filesystem           1K-blocks      Used Available Use% Mounted on
tmpfs                    10240      2876      7364  29% /dev


2 MB RAM on my PC???  I must be missing something.

Thanks for your time nayway.

-- eric


  reply	other threads:[~2005-07-02  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 21:03 updating kernel to 2.6.13-rc1 from 2.6.12 + CONFIG_DEVFS_FS + empty /dev Eric Valette
2005-06-29 22:40 ` Greg KH
2005-06-30 13:12   ` eric.valette
2005-06-30 15:54     ` Greg KH
2005-06-30 20:27       ` Eric Valette
2005-07-02  5:37         ` Greg KH
2005-07-02  7:22           ` Eric Valette [this message]
2005-07-02  8:22             ` Willy Tarreau
2005-07-02  9:09               ` Eric Valette
2005-07-02 10:03                 ` Willy Tarreau
2005-07-02 20:13                   ` Mike Bell
2005-07-02 23:03                     ` Willy Tarreau

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=42C640AC.1020602@free.fr \
    --to=eric.valette@free.fr \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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