GSoC Miniaturise NetBSD - initial testing

[Lloyd Parkes-2]

Hi all,
A feature-incomplete version of my project is now available for  
interested parties to test. The README file at http://home.must-have-coffee.gen.nz/svn/software/miniaturise/README 
  will tell you how use to this code with the NetBSD source tree.  
There are some sample configurations for i386 and evbarm.

The system as it stand right now will be able to build bootable disk  
images, ISO images and tgz files containing arbitrary packages from  
the NetBSD distribution. If there are features you want to see, that  
don't seem to be implemented, and aren't in the TODO file, then send  
me an email.

Cheers,
Lloyd

[matthew sporleder]

On Sun, Jul 5, 2009 at 10:39 PM, Lloyd
Parkes<lloyd@...> wrote:

> Hi all,
> A feature-incomplete version of my project is now available for interested
> parties to test. The README file at
> http://home.must-have-coffee.gen.nz/svn/software/miniaturise/README will
> tell you how use to this code with the NetBSD source tree. There are some
> sample configurations for i386 and evbarm.
>
> The system as it stand right now will be able to build bootable disk images,
> ISO images and tgz files containing arbitrary packages from the NetBSD
> distribution. If there are features you want to see, that don't seem to be
> implemented, and aren't in the TODO file, then send me an email.
>

Do you have some stats on how small you got it?  I should have an SD
card for testing just this sort of thing in the next few weeks.

[Lloyd Parkes-2]

On 7/07/2009, at 1:53 AM, matthew sporleder wrote:

> Do you have some stats on how small you got it?  I should have an SD
> card for testing just this sort of thing in the next few weeks.

It all really depends on what features you want. Some of the more  
basic packages in syspkgs are quite large, so my PICO image, where I  
only wanted /sbin/init and /bin/sh ended up being several MB because  
syspkgs pulls in all of /bin and /sbin. The contents of the syspkgs  
can be rearranged, I noticed that the firmware files got put into  
their own syspkgs package recently.

I'll soon be implementing the ability to trim individual files from  
packages, but using that to remove all but one file from a package  
doesn't seem right to me.

Cheers,
Lloyd