From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ramfs - is it necessary ???
Date: Thu, 22 Feb 2007 09:45:26 +0200 [thread overview]
Message-ID: <200702220945.26551.alan@linuxholdings.co.za> (raw)
In-Reply-To: <200702211825.41801.bss03@volumehost.net>
On Thursday 22 February 2007, Boyd Stephen Smith Jr. wrote:
> On Wednesday 21 February 2007, "pat" <pat@xvalheru.org> wrote about
> 'Re:
>
> [gentoo-user] ramfs - is it necessary ???':
First, I think the OP is confused between ramfs and initramfs.Not quite
the same thing...
But the thread has become about initramfs so we'll stick with that
> > OK, so I have to search for ramfs. What tool is used to create
> > initramsf file for boot or how to compile it into kernel and how to
> > use it with grub ???
>
> Each distro has their own, although I think they were mostly spawned
> from mkinitrd from RedHat. I believe genkernel now creates initramfs
> (as opposed to initrd) files, and may have support for compiling the
> initramfs into the kernel.
genkernel will create an initramfs if you ask it to. The 'all'
and 'initrd' arguments build the initramfs, as in
genkernel all
genkernel initrd
Yes, the initrd argument does indeed build an initramfs and not an
initrd....
And the OP should keep in mind that the initrd format was dumped many
many kernel versions ago and these days we use initramfs,
> grub/lilo/xen loads an initramfs exactly the same as an initrd -- the
> kernel determines how to use the uncompressed data by looking for a
> cpio header.
>
> > Yes, start with kernel documentation ... but something quicker ???
> > :-)
>
> Not that I've found.
True. The only sane docs around I've ever found about this is
Documentation/earlyuserspace.txt - it's a tough read, but it's all
there
alan
--
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?
Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-22 7:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 22:42 [gentoo-user] ramfs - is it necessary ??? pat
2007-02-21 23:16 ` Boyd Stephen Smith Jr.
2007-02-22 0:08 ` pat
2007-02-22 0:25 ` Boyd Stephen Smith Jr.
2007-02-22 0:41 ` pat
2007-02-22 10:07 ` Boyd Stephen Smith Jr.
2007-02-22 7:45 ` Alan McKinnon [this message]
2007-02-22 10:08 ` Boyd Stephen Smith Jr.
2007-02-22 10:56 ` Dirk Heinrichs
2007-02-22 11:05 ` Alan McKinnon
2007-02-22 18:12 ` Neil Bothwick
2007-02-23 7:11 ` Dirk Heinrichs
2007-02-23 9:36 ` Neil Bothwick
2007-02-22 0:13 ` Hemmann, Volker Armin
2007-02-22 0:29 ` Boyd Stephen Smith Jr.
2007-02-22 0:39 ` pat
2007-02-22 1:50 ` Hemmann, Volker Armin
2007-02-22 10:08 ` Boyd Stephen Smith Jr.
[not found] ` <200702220958.49233.alan@linuxholdings.co.za>
2007-02-22 10:08 ` Boyd Stephen Smith Jr.
2007-02-22 7:50 ` Alan McKinnon
2007-02-22 8:14 ` Neil Bothwick
[not found] ` <200702221108.31090.alan@linuxholdings.co.za>
2007-02-22 9:18 ` pat
[not found] ` <200702220411.04512.bss03@volumehost.net>
2007-02-22 12:02 ` pat
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=200702220945.26551.alan@linuxholdings.co.za \
--to=alan@linuxholdings.co.za \
--cc=gentoo-user@lists.gentoo.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