public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hanging out with fbsplash
Date: Thu, 14 Jul 2005 08:19:46 +0200	[thread overview]
Message-ID: <42D60402.4070103@asmallpond.org> (raw)
In-Reply-To: <42D5B150.9000502@gmail.com>

Zac Medico wrote:

>That sounds nice.  Do you use busybox for the root-on-loop-AES setup?  What is better about initramfs?  Do you have to compile the cpio archive into the kernel or is it just as good when you load it like an initrd?  I'm looking forward to the howto ;-).
>
>  
>

Well, I don't use busybox.  The main "problem" using an initrd with
loop-AES is that the memory used by the initrd can never be freed (I
think it can be swapped out though), and thus the reason you want to use
something small like busybox/dietlibc/klibc.  In my case, to make my
initrd small, I ended up using /bin and /lib directories on the /boot
partition to contain the majority of the programs needed by the /linuxrc
script.

But with an initramfs, you don't care as much about the memory problem,
because almost every byte of that can be reclaimed simply by rm -rf'ing
all of the files in the initramfs once you have the root filesystem
mounted and you have pivoted to it.

Thus the reason I don't use busybox...having a 10MB uncompressed
initramfs is not a problem.  I can have bash, glibc, and a bunch of
other regular utilities available before the root is mounted, and when I
am done with them, I simply delete the files and "umount -n -l" the
initramfs.

Oh, and it works either way, but I have a slight preference for
compiling the cpio into the kernel.  It keeps the init environment and
the kernel inexorably linked, and also lets me dump all ramdisk support
from my kernel config.

-Richard

-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2005-07-14  6:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42BEBB2A.40601@asmallpond.org>
     [not found] ` <42BF4F99.6020207@gmail.com>
2005-07-13 20:44   ` [gentoo-user] Hanging out with fbsplash Richard Fish
2005-07-13 21:54     ` John J. Foster
2005-07-14  0:26     ` Zac Medico
2005-07-14  6:19       ` Richard Fish [this message]

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=42D60402.4070103@asmallpond.org \
    --to=bigfish@asmallpond.org \
    --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