linux-mips
[Top] [All Lists]

Re: Building a stand-alone FS on a very limited flash (newbie question)

To: linux-mips@linux-mips.org
Subject: Re: Building a stand-alone FS on a very limited flash (newbie question)
From: Johannes Stezenbach <js@convergence.de>
Date: Tue, 10 Jun 2003 14:26:09 +0200
In-reply-to: <20030609165612.GE32450@rembrandt.csv.ica.uni-stuttgart.de>
Mail-followup-to: Johannes Stezenbach <js@convergence.de>, linux-mips@linux-mips.org
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.GSO.4.44.0306061234410.4045-100000@hydra.mmc.atmel.com> <Pine.GSO.3.96.1030609164009.2806n-100000@delta.ds2.pg.gda.pl> <20030609154408.GA1781@nevyn.them.org> <3EE4C5CF.3050607@galileo.co.il> <20030609165612.GE32450@rembrandt.csv.ica.uni-stuttgart.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.4i
Thiemo Seufer wrote:
> Baruch Chaikin wrote:
> > 
> > I'm using MIPS kernel 2.4.18 with NFS file system mounted on a RedHat 
> > machine. This works fine, but is unsuitable for system deployment. Do 
> > you have hints for me where to start, in order to put the file system on 
> > flash? The platform I'm using is very limited - only one MTD block of 
> > 2.5 MB is available for the file system, out of a 4 MB flash:
> >    0.5 MB is allocated for the firmware code
> >    1.0 MB for the compressed kernel image
> >    2.5 MB for the (compressed?) file system
> > 
> > For example, I've noticed LibC itself is ~5 MB !
> 
> You'll need a smaller libc, dietlibc comes to mind.
> http://www.dietlibc.org/

The diet libc is the first choice when you want it lean and mean.
Best used in combination with Busybox (patch necessary because the
Busybox uses GNU extensions and BSD cruft which the diet libc maintainer
refuses to implement) or embutils (http://fefe.de/).

OTOH, if you want shared library support, stable/working threads or iconv()
you must look elsewhere...


Johannes

<Prev in Thread] Current Thread [Next in Thread>