From: Wolfgang Denk <wd@denx.de>
To: Walser Martin <walser.martin@rw.hirschmann.at>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: what files should be included in initrd
Date: Wed, 09 May 2001 09:02:07 +0200 [thread overview]
Message-ID: <20010509070212.1FF202814D@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 09 May 2001 07:49:35 +0200." <040944A92C91D211954D00C095EE82680168FF32@POST>
In message <040944A92C91D211954D00C095EE82680168FF32@POST> you wrote:
>
> sorry for this question, but it's the first time I try to use linux on my
It's a good question, but it has been asked many, many times before.
See http://penguinppc.org/usr/embedded/howto/PowerPC-Embedded-HOWTO-13.html#ss13.2
and http://www.linux.org/docs/ldp/howto/Bootdisk-HOWTO/buildroot.html
> I'm using PPCBoot and the MontaVista kernel. Both work fine, but I don't
> know how to make a initrd image.
See "Documentation/initrd.txt" in your Linux source directory.
> Can someone give me a short overwiew on how to build such an image and what
> files should be included?
You include those files you need in your embedded system. The minimum
(without any tricks and modifications to the Linux kernel) is a
special file for /dev/console (c 5 1) and a regular file with your
statically linked application that is started as init process.
See ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SIMPLE-PPCBOOT-ramdisk for
an example - this is a PPCBoot image ready for use; you can use
dd if=SIMPLE-PPCBOOT-ramdisk bs=64 skip=1 of=ramdisk.image.gz
to create a "normal" ramdisk image.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"There are three principal ways to lose money: wine, women, and engi-
neers. While the first two are more pleasant, the third is by far the
more certain." - Baron Rothschild, ca. 1800
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-09 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 5:49 what files should be included in initrd Walser Martin
2001-05-09 7:02 ` Wolfgang Denk [this message]
2001-05-09 13:44 ` Mark Phillips
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=20010509070212.1FF202814D@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=walser.martin@rw.hirschmann.at \
/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;
as well as URLs for NNTP newsgroup(s).