mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Segaud <matt@minas-morgul.org>
To: root@chaos.analogic.com
Cc: Paulo Marques <pmarques@grupopie.com>,
	Mildred Frisco <mildred.frisco@gmail.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: making a linux kernel with no root filesystem
Date: Thu, 21 Oct 2004 21:44:15 +0200	[thread overview]
Message-ID: <87d5zbc0vk.fsf@barad-dur.crans.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0410210757040.10239@chaos.analogic.com> (Richard B. Johnson's message of "Thu, 21 Oct 2004 08:10:14 -0400 (EDT)")

"Richard B. Johnson" <root@chaos.analogic.com> disait dernièrement que :

> On Thu, 21 Oct 2004, Paulo Marques wrote:
>
> Let me add the basics that the kernel expects to execute
> /sbin/init. This means that there must be a root file-system
> to contain it. However, it can be a RAM-disk. That's how
> initrd works. /sbin/init can be a program that you write
> that does everything you need yout system to do. It can
> fork off multiple tasks, etc. Just don't accidentally call
> exit() or return from main()!

but initrd needs a FS code linked in :)
the only way to have no fs linked in the kernel, is to use initramfs,
i.e. rootfs as the real root.
The solution to the problem is to provide the basics of a system in
the newc cpio format (see in Documentation/early-userspace/) which
will require no FS code linked in (huh, I guess RAMFS is needed ;)),
tweak usr/Makefile to get it use the in-place initramfs_data.cpio.gz and
put the cpio archive in usr. (I do this way because the initramfs_list
"mechanics" never succeeded in getting me a working kernel :)) 

-- 
"I know how hard it is for you to put food on your family."

George W. Bush
January 27, 2000
During a campaign speech in Nashua, New Hampshire.


  reply	other threads:[~2004-10-21 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21  9:46 Mildred Frisco
2004-10-21 10:05 ` Mildred Frisco
2004-10-21 10:44   ` Paulo Marques
2004-10-21 12:10     ` Richard B. Johnson
2004-10-21 19:44       ` Mathieu Segaud [this message]
2004-10-21 11:53 ` Denis Vlasenko
2004-10-21 19:20   ` Geert Uytterhoeven

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=87d5zbc0vk.fsf@barad-dur.crans.org \
    --to=matt@minas-morgul.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mildred.frisco@gmail.com \
    --cc=pmarques@grupopie.com \
    --cc=root@chaos.analogic.com \
    /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®