mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch for Documentation/initrd.txt?
Date: Fri, 28 Jul 2006 16:58:40 +0300	[thread overview]
Message-ID: <200607281658.40771.a1426z@gawab.com> (raw)
In-Reply-To: <44C9244B.1020708@zytor.com>

H. Peter Anvin wrote:
> Al Boldi wrote:
> > H. Peter Anvin wrote:
> >> Al Boldi wrote:
> >>> Thanks for your very useful docPatch!
> >>>
> >>> OT, but your docPatch made me think of another way to init the kernel;
> >>> via tmpfs, i.e. initTmpFS.
> >>>
> >>> Can anybody see how that could be useful?
> >>
> >> Useful, yes, but this has turned out to be fairly complex.
> >
> > Sounds like somebody tried this before?
>
> Several people, yes.

This http://marc.theaimsgroup.com/?l=linux-kernel&m=107013630212011&w=4 looks 
rather trivial.

What am I missing here?

> >> tmpfs needs
> >> a *LOT* more of the system to be fully operational than ramfs, and the
> >> rootfs is initialized very early on, since one of its purposes is to
> >> eliminate special cases.
> >
> > So would it be possible to remap rootfs from ramfs to tmpfs, once tmpfs
> > is initialized, without actually doing another cpio?
>
> That sounds nasty.

I would call it an obvious hack, if it is necessary at all.  Plus it's only 
to kickstart things.

BTW, your pxebooter is great!

Thanks!

--
Al


  reply	other threads:[~2006-07-28 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 17:26 Al Boldi
2006-07-27 18:52 ` H. Peter Anvin
2006-07-27 20:35   ` Al Boldi
2006-07-27 20:38     ` H. Peter Anvin
2006-07-28 13:58       ` Al Boldi [this message]
2006-07-27 20:19 ` Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2006-07-27 13:17 Tom Horsley

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=200607281658.40771.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=hpa@zytor.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

Powered by JetHome