From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 22:04:14 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 945D616A420; Wed, 1 Feb 2006 22:04:14 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE93F43D70; Wed, 1 Feb 2006 22:04:09 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 01 Feb 2006 14:04:09 -0800 Message-ID: <43E13058.7020708@elischer.org> Date: Wed, 01 Feb 2006 14:04:08 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dario Freni References: <3281.1138742578@critter.freebsd.dk> <43E127A5.9060503@freesbie.org> In-Reply-To: <43E127A5.9060503@freesbie.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: small@freebsd.org, rizzo@icir.org, Poul-Henning Kamp , rwatson@freebsd.org, "M. Warner Losh" , current@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: Wed, 01 Feb 2006 22:04:14 -0000 Dario Freni wrote: >Poul-Henning Kamp ha scritto: > > >>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. >> >> >> > >Actually, FreeSBIE 2 toolkit covers both approaches. It is successfully >used in embedded enviroments. pfSense (www.pfsense.com) use it either >for creating an install livecd as well as embedded images for >soekris-like machines. It can perfectly act as NanoBSD (the only >difference is the partitioning scheme which is trivial to reproduce by >customizing FreeSBIE's image script). > >Nobody of you mind importing the toolkit in the source tree? :) > > on the contrary i thin it should be there.. *somewhere*. the question is, "where?" I thought that's why you have access?