From owner-freebsd-current@FreeBSD.ORG Wed Jun 22 11:03:38 2005 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 3602716A41C for ; Wed, 22 Jun 2005 11:03:38 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0480C43D53 for ; Wed, 22 Jun 2005 11:03:37 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id D0DB446BAB; Wed, 22 Jun 2005 07:03:36 -0400 (EDT) Date: Wed, 22 Jun 2005 12:06:40 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Marcin Jessa In-Reply-To: <20050621205730.5ef76166.lists@yazzy.org> Message-ID: <20050622120405.H26664@fledge.watson.org> References: <20050619155228.Y6413@fledge.watson.org> <66959.1119209763@critter.freebsd.dk> <20050619213612.GD8597@over-yonder.net> <20050621132608.GF738@obiwan.tataz.chchile.org> <20050621205730.5ef76166.lists@yazzy.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Jeremie Le Hen , current@FreeBSD.org, fullermd@over-yonder.net Subject: Re: Summary: experiences with NanoBSD, successes and nits on a Soekris 4801 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, 22 Jun 2005 11:03:38 -0000 On Tue, 21 Jun 2005, Marcin Jessa wrote: > You can read how it's done on NetBSD: > http://www.wifibsd.org/support/netbsd-on-cf.txt > > We do similar things with FreeBSD, but in opposite to nanobsd, picobsd > and such we dont do any crunching of binaries, we just use dynamically > linked libraries. This makes live a lot of easier (ever tried to crunch > openssl?). FYI, while PicoBSD does crunch binaries, NanoBSD does not. > Also the rootfs on FreeBSD can be loaded as a module by loader or > "inserted" into the kernel. PicoBSD and i guess NanoBSD use the second > option. PicoBSD does do this, but NanoBSD doesn't. NanoBSD is basically a modified version of our diskless environment, in that it relies on a standard layout tree, with the exception that it uses populated memory file systems for /var and /etc. As we see storage device size increase, we're seing embedded environments use more and more standard installs, and likewise, the FreeBSD CD install environment move over also (it now uses a live file system). Robert N M Watson