All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaap-Jan Boor <jjboor@aimsys.nl>
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:01:36 +0100	[thread overview]
Message-ID: <1069671695.31339.151.camel@linpc003.aimsys.nl> (raw)
In-Reply-To: <005601c3b275$39446fd0$0700a8c0@pc005>


Hi Gianfranco,

Isn't busybox a good option? A large part of your ramdisk
is filled with binaries and libraries (glibc is big)
which can be included in a single static binary (busybox)

Jaap-Jan

On Mon, 2003-11-24 at 11:25, Ing.Gianfranco Morandi wrote:
> Dear friends,
>
> in our project we have always used the NFS to run linux over an 8260 custom
> board. Now since the activity is almost stable we have tried to build the
> root filesystem on ramdisk. Obviously we have followed all the main rules
> which are contained into several good books, but an important choice is
> always left to the user: " what are the components of filesystem?". The
> answer to this of course depend on several factors which are not the scope
> of this e-mail.
>
> 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
> anybody have or can indicate where can we find an almost complete filesystem
> scheme (for instance based on the ELDK packages)?
>
> Any help would be apreciated
>
> Many thanks
>
> Gianfranco
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-11-24 11:01 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 [this message]
2003-11-24 11:49 ` Wolfgang Denk

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=1069671695.31339.151.camel@linpc003.aimsys.nl \
    --to=jjboor@aimsys.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.