From owner-freebsd-small@FreeBSD.ORG Tue Jan 31 20:03:13 2006 Return-Path: X-Original-To: small@freebsd.org Delivered-To: freebsd-small@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F61116A422; Tue, 31 Jan 2006 20:03:13 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C3BC43D5C; Tue, 31 Jan 2006 20:03:08 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k0VK2to7006930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Jan 2006 12:02:56 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43DFC2D5.7040706@errno.com> Date: Tue, 31 Jan 2006 12:04:37 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <20060131105224.A57698@xorpc.icir.org> <20060131.121559.127178102.imp@bsdimp.com> <20060131195637.U95776@fledge.watson.org> In-Reply-To: <20060131195637.U95776@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: rizzo@icir.org, current@freebsd.org, small@freebsd.org Subject: Re: [RFC] what do we do with picobsd ? X-BeenThere: freebsd-small@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2006 20:03:13 -0000 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