linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Prakash kanthi <pkanthi@yahoo.com>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Smallest Initrd (ram disk)
Date: Fri, 27 Dec 2002 01:22:39 +0100	[thread overview]
Message-ID: <20021227002244.B4C9FC6139@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 26 Dec 2002 14:47:30 PST." <20021226224730.21626.qmail@web41210.mail.yahoo.com>


In message <20021226224730.21626.qmail@web41210.mail.yahoo.com> you wrote:
>
> If i want to build a smallest possible initrd, can you

The  smallest  possible  ramdisk  would  probably  contain  just  the
/dev/directory  with  an  entry  for  /dev/console,  and a statically
linked application program by the name of /sbin/init or so.

> suggest where i can get it from or how i can build it?

See  Documentation/initrd.txt  that  comes  with  your  Linux  kernel
sources.

> I am working with a custom made PPC405 based board
> with just 8MB RAM.

8 MB is a lot. You  can  run  pretty  complex  systems  there  -  for
example, the default ramdisk size for the SELF package is 4 MB, about
half  of  which  is  unused. See the ELF package as included with our
ELDK,  or  see  ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/  for  am
older (and smaller) version.

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
"What is wanted is not the will to believe, but the will to find out,
which is the exact opposite." - Bertrand Russell, _Sceptical_Essays_,
1928

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

      parent reply	other threads:[~2002-12-27  0:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 16:10 After Uncompresseing Linux..., what's next James Don
2002-12-19 16:39 ` Tom Rini
2002-12-20 16:14 ` Prakash kanthi
2002-12-20 16:32   ` Prakash kanthi
2002-12-20 16:49     ` Jim Potter
2002-12-20 17:02       ` Jim Potter
2002-12-20 16:38   ` Gary Thomas
2002-12-20 16:48     ` Prakash kanthi
2002-12-20 16:52       ` Gary Thomas
2002-12-20 17:06         ` Prakash kanthi
2002-12-20 17:22           ` Gary Thomas
2002-12-20 21:59           ` Serious Problem: " Prakash kanthi
2002-12-20 16:47   ` Jim Potter
2002-12-26 22:47   ` Smallest Initrd (ram disk) Prakash kanthi
2002-12-26 22:55     ` Jim Potter
2003-01-13  2:15       ` Prakash kanthi
2003-01-13  7:55         ` Wolfgang Denk
2003-01-14 18:42           ` ramdisk mount problem Prakash kanthi
2003-01-14 18:57             ` Wolfgang Denk
2003-01-15  8:33             ` Frederic Soulier
2003-01-16  4:49               ` Ramdisk details; execve("/bin/sh") output Prakash kanthi
2003-01-16  5:57                 ` Hi Anish
2003-01-16  8:00                   ` Hi Wolfgang Denk
2003-01-16  8:06                 ` Ramdisk details; execve("/bin/sh") output Wolfgang Denk
2002-12-27  0:22     ` 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=20021227002244.B4C9FC6139@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=pkanthi@yahoo.com \
    /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).