[ELDK] Pruning Filesystem

[Batsayan Das]

The other way is

Download busybox and cross compile and install it say in a directory named 
"rootfs". This step will create  bin, sbin, usr etc. 
run crosstool-targetcomponents-ldd on any of the binaries generated in 
step 1, now you can find out the libraries required, create "lib" 
directory and  copy those libraries along with soft links to the "lib" 
directory of your root file system 
compile kernel and install modules in the "roofs" directory. 
create **empty** tmp, var, mnt,  sys directories inside "rootfs" directory
Now create etc, and put some basic files "inittab", and "init.d/rcS" 

Now your "rootfs" is ready. 

Regards,
Batsayan Das
Tata Consultancy Services
Mailto: batsayan.das at tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty.   IT Services
                        Business Solutions
                        Outsourcing
____________________________________________



From:
Dave Rensberger <David.Rensberger at ambientcorp.com>
To:
"eldk at lists.denx.de" <eldk at lists.denx.de>
Date:
10/06/2010 06:50 PM
Subject:
Re: [ELDK] Pruning Filesystem
Sent by:
eldk-bounces at lists.denx.de



>[ELDK] Pruning Filesystem
>
>" Any pointers?  Is 60MB attainable?  Has anyone successfully pruned
>away the ELDK in this fashion?"


A couple of years ago, my company required me to use DENX, and I ran into 
the issue that you're seeing and solved it in exactly the way that you 
describe (pruned the filesystem).  The reason I did this was because (in 
2008 anyway), the "Root File System Builder" didn't seem to work and I 
couldn't find any real documentation for it.   Maybe this has changed over 
the past couple of years. 

It was fairly easy.  What you basically want to do is prune the 
"crosstool-targetcomponents-ppc_4xx" package down to the bare essentials 
(basically down to just the standard C library and maybe a few other 
shared objects).   If you look at the contents of the package, it becomes 
pretty obvious what you don't want (header files, static libraries, 
toolchain components, gcj stuff).  I can send you my pruning script if 
you'd like.  We eventually got the base distribution well below 50MB, 
which I don't really consider "embedded sized", but it was good enough for 
my project's requirements.   I personally think this could all be a whole 
lot easier if the C-library were just partitioned into a separate package. 
  I the "Root File System Builder" works now, I'd be interested in hearing 
about it, but probably won't go back and change at this point, since we 
only use DENX in a legacy product at this point anyway.

--Dave 

_______________________________________________
eldk mailing list
eldk at lists.denx.de
http://lists.denx.de/mailman/listinfo/eldk


=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you