Date: Tue, 31 Jan 2006 12:04:37 -0800 From: Sam Leffler <sam@errno.com> To: Robert Watson <rwatson@freebsd.org> Cc: rizzo@icir.org, current@freebsd.org, small@freebsd.org Subject: Re: [RFC] what do we do with picobsd ? Message-ID: <43DFC2D5.7040706@errno.com> In-Reply-To: <20060131195637.U95776@fledge.watson.org> References: <20060131105224.A57698@xorpc.icir.org> <20060131.121559.127178102.imp@bsdimp.com> <20060131195637.U95776@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > > On Tue, 31 Jan 2006, M. Warner Losh wrote: > >> Given how intertwingled picobsd is to the underly OS, I think you are >> going to have a hard time getting to #3. #2 is fine with me. > > > My feelings here are pretty much the same -- I'm skeptical about the > continued ability to maintain PicoBSD outside CVS in a long-term way, > given tight integration with the source tree. People can and do > maintain there own versions of FreeBSD releases and wrappers (FreeSBIE > is presumably the most successful example), but it's a lot of work, and > if there's trouble finding enough hands for the current PicoBSD, it > doesn't seem likely it will get more hands somewhere else. My derivative of thewall project is similar to picobsd in it's approach and it might be worth combining the two. I've kept mine reasonably up to date and believe it works for 4.x, 5.x, and 6.x systems. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43DFC2D5.7040706>