public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirk Heinrichs <ext-dirk.heinrichs@nokia.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ramfs - is it necessary ???
Date: Thu, 22 Feb 2007 11:56:12 +0100	[thread overview]
Message-ID: <200702221156.12837.ext-dirk.heinrichs@nokia.com> (raw)
In-Reply-To: <200702220408.23312.bss03@volumehost.net>

[-- Attachment #1: Type: text/plain, Size: 2095 bytes --]

Am Donnerstag, 22. Februar 2007 schrieb ext Boyd Stephen Smith Jr.:

> 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).

Here's what I use in my initramfs' linuxrc:

# change roots
echo "initramfs: Switching to real root volume" 2>&1
find -xdev / -exec rm '{}' ';'
cd /newroot
mount --move . /
echo "initramfs: Starting init with options ${INIT_OPTS} ..."
exec chroot . /bin/bash <<- EOF >/dev/console
exec /sbin/init ${INIT_OPTS}
EOF

The only thing I didn't get to work so far is freeing the used space (that 
find command should do the job, but gives me som error msg).

> 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.

I just maintain /usr/src/initramfs which contains all the stuff that should 
go in, put the name of this directory into the kernel config 
(CONFIG_INITRAMFS_SOURCE="/usr/src/initramfs"), build the kernel. That's a 
very simple thing to do if you don't need to load any modules from within 
initramfs (I just do the evms_activate stuff) and will give you only one 
file to deal with.

/usr/src/initramfs itself is filled by a self-constructed script prior to 
building a new kernel.

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Hambornerstraße 55      | Web:  http://www.capgemini.com
D-40472 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-02-22 11:04 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.
2007-02-22 10:56           ` Dirk Heinrichs [this message]
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=200702221156.12837.ext-dirk.heinrichs@nokia.com \
    --to=ext-dirk.heinrichs@nokia.com \
    --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