From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ramfs - is it necessary ???
Date: Thu, 22 Feb 2007 04:08:23 -0600 [thread overview]
Message-ID: <200702220408.23312.bss03@volumehost.net> (raw)
In-Reply-To: <200702220945.26551.alan@linuxholdings.co.za>
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
On Thursday 22 February 2007 01:45, Alan McKinnon wrote:
> 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...
Yeah, I hoped I cleared that up with my first reply.
> But the thread has become about initramfs so we'll stick with that
I think this is more what the OP was concerned about.
> And the OP should keep in mind that the initrd format was dumped many
> many kernel versions ago and these days we use initramfs,
I am fairly certain I was still using my custom initrd (not an initramfs)
until 2.6.17 -- I'm fairly sure 2.6.20 still *supports* initrd format, even
if initramfs is preferred now.
For the life of me, I always found it easier to get an initrd working
rather
than an initramfs -- the whole chroot/exec vs. pivot_root vs. switch_root
step always failed for me when using an initramfs (and the very same shell
script worked as an initrd). Also, a script-made initrd is still just a
compressed filesystem, easy to deal with, but a script-made initramfs
(particularly one made by genkernel) is not just a cpio archive, it's a
series of them separated by some !!!!KERNEL_MAGIC!!!! strings in the middle
of binary data -- nearly impossible to work with using standard tools.
At least, that's been my experience, others may have found the process
easier.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
New GPG Key! Old key expires 2007-03-25. Upgrade NOW!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-22 10:45 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
2007-02-22 10:08 ` Boyd Stephen Smith Jr. [this message]
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=200702220408.23312.bss03@volumehost.net \
--to=bss03@volumehost.net \
--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