>From the busybox guys, you have buildroot too: http://buildroot.uclibc.org/
It now supports eabi (http://wiki.debian.org/ArmEabiPort) toolchains, and uclibc. I saw patches recently for glibc but not sure how good they are yet. It can produce a very small customized root file system, It is Make managed similar to the kernel kbuild (make menuconfig), and is fairly well supported. If you are looking for a good glibc distro, you could try the openembedded group (www.openembedded.org) derived from the Buildroot using a new python tool called bitbake. The specific distro for eabi already exists called Angstrom OE (http://angstrom-distribution.org) with prebuilt ipk feeds (http://angstrom-distribution.org/unstable/feed/ , 4000+ packages). The Montavista Development kit uses armv5te. The Angstrom distro of the OE doesn't handle small footprints yet but I've heard talks on the mailing list of such configuration, and isn't too hard to customize your own with some effort, but I feel more effort then Buildroot for now. The ipkg(http://handhelds.org/moin/moin.cgi/Ipkg) is package management tool for embedded system based on the debian pkg. It has the ability to produce root file system based on package decencies similar Montavista's Eclipse method. OE uses this method. Monvavista's root file system generator requires Eclipse, and I believe can only build via the command thru it's project based tools. I believe Debian just finished their first cut of eabi support feeds: http://www.mail-archive.com/[email protected]/msg06046.html originally bootstrapped from the Angstrom guys. I hope this is some good direction. Jim > -----Original Message----- > From: > [EMAIL PROTECTED] > ncidsp.com > [mailto:[EMAIL PROTECTED] nux.davincidsp.com] On Behalf Of Diego Dompe > Sent: Tuesday, January 23, 2007 10:06 AM > To: Andy Ngo > Cc: davinci-linux-open-source > Subject: Re: Small footprint filesystem > > As Lloyd suggested the best way to build a small file system > is by building it from scratch with busybox. > > We have build our own file system for Davinci with a > footprint of ~700kb compressed, and ~1.5MB decompressed with > ext2 and initrd. The catch here is that we are using our own > BSP with smaller footprint libraries (uclibc is around 800kb, > and gnu libc > 1.5MB last time I looked). It should be > possible to build a filesystem around 5MB with MV toolchain, > busybox, and a basic file system layout. > > Your minimal requirements are: > - busybox with a shell(msh), /sbin/init > - /etc with fstab, group, hostname, inittab, mtab, passwd, services > - /sys mounted with sysfs > - /proc mounted with procfs > - /bin with busybox files > - /sbin with busybox files > - /lib with minimal libraries: libc, libm, libpthread (?), > libdl, libgcc, libnsl, libresolv, libutil (those are the ones > on my toolchain, I think gnu libc also may need the plugins for PAM). > - /var > - /dev with console, random, urandom, kmem, mem, null, zero > (and ram0 if using initrd). You may add ttySX and other > devices if you wish, or configure busybox to use udev (mdev). > > That's your minimal requirements for a booting file system. > Hope it helps. > > Regards, > > Diego Dompe > RidgeRun Engineering > > On Jan 22, 2007, at 6:41 PM, Andy Ngo wrote: > > > Hi, > > > > > > The DVEVM board comes with a HUGE filesystem on the 2.5" > hard drive. > > On boot up, the Linux kernel mounts the partition > > > > (/dev/hda1) to be used as the root filesystem. The filesystem is > > 1.9GB! This is good for development purposes but when we have > > > > our custom board, we will only have a small flash memory to > store the > > filesystem. Do anyone have instructions on how to create > > > > small footprint filesystem (<16Mb)? I was planning to do a > top- down > > approach of eliminating all the files/directories > > > > (/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target) I > don't need > > until I get it to a manageable filesystem but I'm not sure > > > > what are needed and what aren't. Has anyone done this and have a > > recommendation? > > > > > > Also, the current "top" (procps) utility on the board is version > > 3.2.5; it doesn't support displaying individual threads of > a process; > > > > it only shows info about a process as a whole but not the thread. > > Version 3.2.6 has that capability; does anyone know how we > > > > can get that version? > > > > > > Thank! > > > > > > Regards, > > > > Andy > > > > _______________________________________________ > > Davinci-linux-open-source mailing list > > [email protected] > > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > > _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
