From owner-freebsd-current@FreeBSD.ORG  Tue Jan 31 19:56:08 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 3656D16A420;
	Tue, 31 Jan 2006 19:56:08 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4A9E543D45;
	Tue, 31 Jan 2006 19:56:06 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 4D46246BE7;
	Tue, 31 Jan 2006 14:55:57 -0500 (EST)
Date: Tue, 31 Jan 2006 19:57:57 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20060131.121559.127178102.imp@bsdimp.com>
Message-ID: <20060131195637.U95776@fledge.watson.org>
References: <20060131105224.A57698@xorpc.icir.org>
	<20060131.121559.127178102.imp@bsdimp.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: rizzo@icir.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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2006 19:56:08 -0000


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.

Robert N M Watson