From owner-freebsd-small@FreeBSD.ORG Tue Jan 31 21:35:32 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 5F0C016A422; Tue, 31 Jan 2006 21:35:32 +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 4A65C43D68; Tue, 31 Jan 2006 21:35:27 +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 k0VLYg1S039908; Tue, 31 Jan 2006 14:34:43 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 31 Jan 2006 14:34:54 -0700 (MST) Message-Id: <20060131.143454.76964518.imp@bsdimp.com> To: phk@phk.freebsd.dk From: "M. Warner Losh" In-Reply-To: <3281.1138742578@critter.freebsd.dk> References: <20060131.131654.134137067.imp@bsdimp.com> <3281.1138742578@critter.freebsd.dk> 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 14:34:43 -0700 (MST) Cc: small@freebsd.org, sam@errno.com, rwatson@freebsd.org, current@freebsd.org, rizzo@icir.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 21:35:32 -0000 In message: <3281.1138742578@critter.freebsd.dk> "Poul-Henning Kamp" writes: : In message <20060131.131654.134137067.imp@bsdimp.com>, "M. Warner Losh" writes: : >In message: <43DFC2D5.7040706@errno.com> : > Sam Leffler 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. I tend to agree. For our build system, we take the additive approach without the crunchgen step... Given the price points for various parts on new projects I'm working on, we may need to move more towards a crunchgen and/or pure RAM disk... Having different alternatives helps us a lot and makes it easy to continue to deploy FreeBSD systems. Warner