From owner-freebsd-small@FreeBSD.ORG Thu Jul 26 18:49:03 2007 Return-Path: Delivered-To: small@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A94D116A419 for ; Thu, 26 Jul 2007 18:49:03 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.184]) by mx1.freebsd.org (Postfix) with ESMTP id 2500A13C45D for ; Thu, 26 Jul 2007 18:49:00 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so637676mue for ; Thu, 26 Jul 2007 11:48:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AHDV0p5TIGlq/lG9jUhRjSk6fVqNMh9xZRhEpsIDvF2MOeFZyaoChPg8iQ3nxDJhKjxyzp22U0YnZsYGdMluMF4EAFh/IrrKDckqzhThLHTdz6enT7RZOYwuykntWsdkgg7UjR+uoIZs1lH1+e2AIy3F9gJrU08wW/X027wBQSU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SHqBG+D50QOjcUJfsJ03JBDjz/oYoarnhbPFgSyr9EVRA7xDJ5N7CxD62iUq16dRe6Nt4PaPk5qgcEu+IwuBR5XIZjVYpqnaieT4EpXbOCkI/13yNIzt8HHpddSKbRpx21jN2/ydSgOUkyfLOoTCuhSKz+Hn8NLZVfoIpCNmosc= Received: by 10.82.134.12 with SMTP id h12mr1805637bud.1185474110793; Thu, 26 Jul 2007 11:21:50 -0700 (PDT) Received: by 10.82.174.13 with HTTP; Thu, 26 Jul 2007 11:21:50 -0700 (PDT) Message-ID: Date: Thu, 26 Jul 2007 15:21:50 -0300 From: "Eduardo Meyer" To: "Michael W. Lucas" In-Reply-To: <20070725022141.GA17703@bewilderbeast.blackhelicopters.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070725022141.GA17703@bewilderbeast.blackhelicopters.org> Cc: small@freebsd.org Subject: Re: What's our standard "stripped-down FreeBSD" tool? 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: Thu, 26 Jul 2007 18:49:03 -0000 On 7/24/07, Michael W. Lucas wrote: > Hi, > > Been researching building stripped-down versions of FreBSD for flash > drives and suchforth. It seems that we have three big contenders in > this area: > > Freesbie > NanoBSD > TinyBSD > > Are any of these particularly stronger than the other? If I was to > start over, or recommend one to someone else, which would be the best > these days? > > Thanks, > ==ml > > -- > Michael W. Lucas mwlucas@BlackHelicopters.org, mwlucas@FreeBSD.org > http://www.BlackHelicopters.org/~mwlucas/ > Coming Soon: "Absolute FreeBSD" -- http://www.AbsoluteFreeBSD.com > On 5/4/2007, the TSA kept 3 pairs of my soiled undies "for security reasons." I have been using all mentioned options, plus, minibsd. Honestly, I would recommend anyone to use TinyBSD, as long as: - You dont need to do cross building; - You can read a few instructions on a help screen or interactively answer some questions; This is what I mention because TinyBSD wont do cross building because it does not compile the whome world. Instead, it copies the already compiled and in production ones. Also because tinyBSD have a good README file, not no man page nor sgmlized docs. I know people are addressing those issues, regarding SGML doc, but it does not exist right now. The first issue is also getting addressed on the -CURRENT version of TinyBSD (cvs only, maybe on the website too - tinybsd.org), but it is not ready. According to patrick tracanelli TinyBSD will heavily be addressed to build ARM systems. And to do so, cross building is a must be. However, it is not present right now. I have added TinyBSD to flash discs, to CF cards, to memory sticks and also on optical drives. On CD/DVD it is just a matter of building an ISO with mkisofs and adding one extra line on kernel conf file. No "special magic" that requires using a whole other framework. I can also choose if I want tinyBSD to act as a live system, depending on the booted media, or if I want it to work as MFS system, which will never access the media once it is booted. It is specially good on memory sticks. It is a feature Julian Elischer contributed, if I remember the commit message correctly. TinyBSD also have pre-defined config files ready to build, just like picobsd used to. If you aim to make a FreeBSD system aimed for PCEngine's WRAP for example, you will save yourself a LOT of work and study on why NanoBSD, FreesBIE or anything else wont work on Wrap, and do the necessary changes, while TinyBSD has a ready-to-go predefined conf, so you will only spend your time on customization of the system. Not studying how to make it, at least, boot. So, my personal experiences are favorable to this tinybsd thing. Give it a try. BTW, its minimal image is 14MB. My usable ones are 21MB sized, in the average. -- =========== Eduardo Meyer pessoal: dudu.meyer@gmail.com profissional: ddm.farmaciap@saude.gov.br