[RFC] what do we do with picobsd ?
M. Warner Losh
imp at bsdimp.com
Tue Jan 31 13:35:32 PST 2006
In message: <3281.1138742578 at critter.freebsd.dk>
"Poul-Henning Kamp" <phk at phk.freebsd.dk> writes:
: In message <20060131.131654.134137067.imp at bsdimp.com>, "M. Warner Losh" writes:
: >In message: <43DFC2D5.7040706 at errno.com>
: > Sam Leffler <sam at errno.com> writes:
: >Since I've started working on the bring up on an ARM based board, I've
: >been wanting something that is easy to work with and that worked. I
: >think it would help us a lot in the embedded space if we had something
: >integrated into the base OS to do this stuff.
: I agree. I think we need to be much more inclusive in our concept of
: a 'release' than we are now.
: As I see it, PicoBSD with its "additive" approach would cover the
: low-capacity (<32 MB ?) range, NanoBSD with its "subtractive" approach
: takes over from there, FreeSBIE covers the "don't touch my disk"
: range and finally the full blown release as we know it.
I tend to agree. For our build system, we take the additive approach
without the crunchgen step... Given the price points for various
parts on new projects I'm working on, we may need to move more towards
a crunchgen and/or pure RAM disk... Having different alternatives
helps us a lot and makes it easy to continue to deploy FreeBSD systems.
More information about the freebsd-current