public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Segaud <matt@minas-morgul.org>
To: "Harald Dunkel" <harald.dunkel@t-online.de>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: udev: what's up with old /dev ?
Date: Wed, 13 Oct 2004 15:08:23 +0200	[thread overview]
Message-ID: <87vfde3gvs.fsf@barad-dur.crans.org> (raw)
In-Reply-To: <416C4E15.9000503@t-online.de> (Harald Dunkel's message of "Tue, 12 Oct 2004 23:35:17 +0200")

"Harald Dunkel" <harald.dunkel@t-online.de> disait dernièrement que :

> Greg KH wrote:
>> On Tue, Oct 12, 2004 at 10:16:54PM +0200, Harald Dunkel wrote:

> Sorry, somewhere in this thread I had clicked the wrong
> reply button.
>
> Talking about initramfs: I am still trying to become
> familiar with this stuff. I have found a lot of small
> pieces of information (still reading), and the cpio
> stuff in the kernel usr directory. But I have 2 questions:
>
> Why is the initramfs built at the beginning of the
> kernel build procedure? Wouldn't it be more reasonable
> to build it when all kernel modules are available?

because for now, the initramfs built into the kernel is quasi-empty and
isn't used as-is.

>
> And why is it compiled into the kernel at all? The
> README in Documentation/early-userspace says
>
> <quote>
> "Early userspace" is a set of libraries and programs that provide
> various pieces of functionality that are important enough to be
> available while a Linux kernel is coming up, but that don't need to be
> run inside the kernel itself.
> </quote>

the last statement just says it does not run in _kernelspace_ but in
_userspace_. 
it has to be in the kernel.
I use it to mount my dm-crypt'd / and no initrd is needed.
(well as I wasn't able to get a small cryptsetup binary, my kernels
are ~1850kB worth of size)

> So why compile it into the kernel? IMHO it would be more
> flexible to load the early-userspace stuff similar to initrd
> via the grub command line. Compiling it into the kernel
> could be optional.

huh, well initrd is / that is mounted over the so-called _rootfs_
initramfs is here to _be_ that rootfs. So no pivot_root needed and the run-it
program included in klibc tarballs takes care of wiping-out everything that
could waste memory into the initramfs before mounting the real /. 
If it was to compiled out of the kernel, it would just be an initrd....

rootfs is _needed_ for mounting the real root, so is initramfs.

have a nice day,

Mathieu

-- 
"My pan plays down an unprecedented amount of our national debt."

George W. Bush
February 27, 2001
>From a speech concerning the proposed federal budget.


  reply	other threads:[~2004-10-13 13:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 22:08 udev: what's up with old /dev ? J.A. Magallon
2004-10-10 22:51 ` Zack Weinberg
2004-10-10 23:15   ` Hacksaw
2004-10-10 23:25     ` J.A. Magallon
2004-10-11  0:06       ` Hacksaw
2004-10-11 19:13       ` Denis Vlasenko
2004-10-11  9:14     ` Felipe Alfaro Solana
2004-10-11 10:29       ` Arkadiusz Miskiewicz
2004-10-11 12:02         ` Felipe Alfaro Solana
2004-10-11 11:11       ` Hacksaw
2004-10-11 12:04         ` Felipe Alfaro Solana
2004-10-11 20:06           ` Hacksaw
2004-10-11 20:51             ` Bartlomiej Zolnierkiewicz
2004-10-11 21:28               ` Hacksaw
2004-10-12  0:19 ` Greg KH
2004-10-12  8:11   ` Harald Dunkel
2004-10-12 16:58     ` Greg KH
     [not found]       ` <416C26B4.6040408@t-online.de>
     [not found]         ` <20041012185733.GA31222@kroah.com>
     [not found]           ` <416C3BB6.4040200@t-online.de>
     [not found]             ` <20041012203022.GB32139@kroah.com>
2004-10-12 21:35               ` Harald Dunkel
2004-10-13 13:08                 ` Mathieu Segaud [this message]
2004-10-13 14:13                   ` Harald Dunkel
2004-10-13 14:33                     ` Mathieu Segaud
  -- strict thread matches above, loose matches on Subject: below --
2004-10-10 22:41 Michael Thonke
2004-10-11  7:19 Zack Weinberg

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=87vfde3gvs.fsf@barad-dur.crans.org \
    --to=matt@minas-morgul.org \
    --cc=greg@kroah.com \
    --cc=harald.dunkel@t-online.de \
    --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