From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: Question about initramfs
Date: Tue, 15 Mar 2005 08:31:43 +0500 [thread overview]
Message-ID: <d15ksi$n22$1@sea.gmane.org> (raw)
In-Reply-To: 4235C0A1.3050508@jg555.com
Jim Gifford wrote:
> Question: Initramfs is going to replace initrd, but I haven't seen
> anyone explain how to copy modules that are built during the build
> process moved into the initramfs archive. Has somebody done, this or is
> this still a work in progress?
Easy.
1) Unpack a vanilla kernel and build and install it as you usually do for a
system that doesn't need initramfs.
make menuconfig
make
make modules_install
cp arch/i386/boot/bzimage /boot/linux-2.6
2) Make a temporary directory (say, "initramfs") and put all files that you
want to go to your initramfs there. Don't forget the "/init" file, it is
used as a starting point for initramfs.
3) Make the initramfs image:
cd initramfs
find . | cpio -o -H newc | gzip -9 >/boot/initramfs-2.6.cpio.gz
4) Add /boot/linux-2.6 and /boot/initramfs-2.6.cpio.gz to your LILO or GRUB
as you would normally do with a kernel image and the initrd:
image=/boot/linux-2.6
label="Linux"
initrd=/boot/initramfs-2.6.cpio.gz
root=/dev/hda1 # if your initramfs "/init" script understands this
read-only # if your initramfs "/init" script understands this
5) Upon reboot, the kernel will automatically determine that the image is
really an initramfs, not an initrd.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2005-03-15 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 16:49 Question about initramfs Jim Gifford
2005-03-15 3:31 ` Alexander E. Patrakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-28 8:54 question " bott
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='d15ksi$n22$1@sea.gmane.org' \
--to=patrakov@ums.usu.ru \
--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