From: Wolfgang Denk <wd@denx.de>
To: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Ramdisk trivial question
Date: Mon, 24 Nov 2003 12:49:36 +0100 [thread overview]
Message-ID: <20031124114941.6ADAFC5F5F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 24 Nov 2003 11:25:02 +0100." <005601c3b275$39446fd0$0700a8c0@pc005>
Dear Gianfranco,
in message <005601c3b275$39446fd0$0700a8c0@pc005> you wrote:
>
> The question is: The ELDK 2.01 package (which is currently being used in our
> system) is too large to be fitted into a ramdisk, while the minimum
> filesystem does not allow to be used in our midrange application. Does
What do you mean with "the minimum filesystem does not allow to be
used" ?
> anybody have or can indicate where can we find an almost complete filesystem
> scheme (for instance based on the ELDK packages)?
The ELDK contains the SELF package (SELF = Simple Embedded Linux
Framework) which is intended as a building stone for your own
application images. Instructions how to add files and/or change the
size of the filesystem and how to generate different image formats
(ramdisk, cramfs, JFFS2) can be fund in the DULG. See especially
http://www.denx.de/twiki/bin/view/DULG/HowToIncreaseSizeOfRamdisk
http://www.denx.de/twiki/bin/view/DULG/HowToAddFiles
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
...when fits of creativity run strong, more than one programmer or
writer has been known to abandon the desktop for the more spacious
floor. - Fred Brooks, Jr.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-11-24 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 10:25 Ramdisk trivial question Ing.Gianfranco Morandi
2003-11-24 11:01 ` Jaap-Jan Boor
2003-11-24 11:49 ` Wolfgang Denk [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=20031124114941.6ADAFC5F5F@atlas.denx.de \
--to=wd@denx.de \
--cc=gianfranco.morandi@euro-studio.it \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).