Date: Tue, 31 Jan 2006 21:22:58 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "M. Warner Losh" <imp@bsdimp.com> Cc: small@freebsd.org, rwatson@freebsd.org, current@freebsd.org, rizzo@icir.org Subject: Re: [RFC] what do we do with picobsd ? Message-ID: <3281.1138742578@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 31 Jan 2006 13:16:54 MST." <20060131.131654.134137067.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3281.1138742578>