From owner-freebsd-current@FreeBSD.ORG Tue Jan 31 20:17:41 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E336A16A420; Tue, 31 Jan 2006 20:17:41 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 716CC43D53; Tue, 31 Jan 2006 20:17:41 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k0VKGgqL036518; Tue, 31 Jan 2006 13:16:42 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 31 Jan 2006 13:16:54 -0700 (MST) Message-Id: <20060131.131654.134137067.imp@bsdimp.com> To: sam@errno.com From: "M. Warner Losh" In-Reply-To: <43DFC2D5.7040706@errno.com> References: <20060131.121559.127178102.imp@bsdimp.com> <20060131195637.U95776@fledge.watson.org> <43DFC2D5.7040706@errno.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 31 Jan 2006 13:16:43 -0700 (MST) Cc: rizzo@icir.org, rwatson@freebsd.org, current@freebsd.org, small@freebsd.org Subject: Re: [RFC] what do we do with picobsd ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2006 20:17:42 -0000 In message: <43DFC2D5.7040706@errno.com> Sam Leffler writes: : 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. 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. Warner