Date: Mon, 25 Sep 2006 13:24:34 -0800 From: Tom Simes <simestd@netexpress.com> To: Patrick Tracanelli <eksffa@freebsdbrasil.com.br> Cc: freebsd-small@freebsd.org Subject: Re: TinyBSD available in the base system and 6.2-PRERELEASE image available online Message-ID: <20060925132434.36e6dba5.simestd@netexpress.com> In-Reply-To: <45182815.20603@freebsdbrasil.com.br> References: <4511C90E.6090305@freebsdbrasil.com.br> <20060925103733.076df673.simestd@netexpress.com> <45182815.20603@freebsdbrasil.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 25 Sep 2006 16:03:49 -0300 Patrick Tracanelli <eksffa@freebsdbrasil.com.br> wrote: > Hello Tom. > > All other images from http://www.tinybsd.org/tinybsd/Download except > this one will work on Soekris. I believe we should make 6.2-PRERELEASE > > for Soekris too, so in the next 20-30 minutes you can check this > download section to grab new one. Wow, that's service! Thanks Patrick :) > Regarding PREFIX, there is no special reason. But how do you suggest > using ports collection chrooting? The "ports" tree should be available > under the chrooted directory to do so, right? > > Maybe pkg_add would do the job easier, if pkg_add were available in > the embedded system. > > We are trying to work out a better approach for 3rd party software > installation, using the many ports' mk files and trying to detect > which files from pkg-plist shall not be installed in an embedded > system (say, man pages, shared examples, etc), so 3d party apps > support for TinyBSD is really something too basic right now. > > Ideas are welcome regarding this approach. I think every minimized *nix install suffers from this. As soon as someone gets $distribution downloaded they want to customize it for their particular task. I've tried several methods with NanoBSD, but ports with extensive dependencies or that need to add users to the system can quickly outgrow the simple shell scripts folks are using to assemble working images. While I'm still refining how I build an image, at this point the easiest and most successful method I've found is: create the basic build (in NanoBSD's case using a slightly modified nanobsd.sh script) chroot to that environment (chroot /usr/obj/_.w) and use pkg_add -r to install the additional packages/users I'm interested in. re-create disk image (with another slightly modified nanobsd.sh script) This method lets pkg_add take care of the dependencies for me, and also allows packages to be added successfully that need to add users / groups / files in "odd" places. There are still some manual steps, but the method is consistent, repeatable and works for me. As far as trying to protect people from installing Gimp on their embedded device - IMHO that is self correcting ;-) Tom ====================================================================== "Z-80 system stack overflow. Shut 'er down Scotty, the system's sucking mud" - Error message on TRS 80 Model-16B Tom Simes simestd@netexpress.com ======================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060925132434.36e6dba5.simestd>