In message <[EMAIL PROTECTED]>, John Ackermann N8UR writes: >Brendan Minish said the following on 12/29/2006 09:11 AM: > >> I have an install of freeBSD6.1 running in vmware to use as a build >> staging platform and I think I can manage the custom kernel build >> (although a peek at someone else's config would be useful.) etc >> i have also manged to get nanoBSD to build for me but the resultant >> build file is huge. how do I go about pruning the nanoBSD to only what >> is needed? > >Hi Brendan -- > >PHK is the definitive source of answers about nanoBSD, but I think the >image size is actually tuned to the size of the CF card that's >specified, so if you spec'd a 512MB card, you'll an image that size >(actually, two identical images that add up to that size). Most of the >image is empty space. I think the actual code size is less than 64MB.
The code size depends how much of FreeBSD you disable in the nanobsd build. If you don't disable anything, I think each code image needs about 180-200 MB so a 512MB card is perfect for getting airborne quickly. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ time-nuts mailing list [email protected] https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
