Date: Tue, 31 Jan 2006 13:28:56 -0800 From: Julian Elischer <julian@elischer.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: rizzo@icir.org, rwatson@freebsd.org, small@freebsd.org, current@freebsd.org Subject: Re: [RFC] what do we do with picobsd ? Message-ID: <43DFD698.7040508@elischer.org> In-Reply-To: <3281.1138742578@critter.freebsd.dk>
index | next in thread | previous in thread | raw e-mail
Poul-Henning Kamp wrote: >In message <20060131.131654.134137067.imp@bsdimp.com>, "M. Warner Losh" writes: > > >>In message: <43DFC2D5.7040706@errno.com> >> Sam Leffler <sam@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'd like to see us take the freesbie release into the tree somewhere (since it uses so many ports, maybe in ports, or maybe in tools)home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43DFD698.7040508>