Date: Thu, 25 May 2006 16:11:57 +0200 From: Dario Freni <saturnero@freesbie.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: small@freebsd.org, current@freebsd.org Subject: Re: FreeBSD's embedded agenda Message-ID: <4475BB2D.2090609@freesbie.org> In-Reply-To: <2538.1148556253@critter.freebsd.dk> References: <2538.1148556253@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig256F0C934D36CFDAD4DE1242
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Poul-Henning Kamp wrote:
> FreeSBIE is interesting in the upper size of embedded systems,
> and it is gaining flexibility and features fast. If you have
> rotating media available, FreeSBIE is probably what you should
> look at.
>=20
> NanoBSD caters only to the "run read-only from flash" area, call
> it if you will the "soekris" area. I need to investigate if it
> makes sense to use the FreeSBIE framework to build nanobsd images.
For what I've seen, imho NanoBSD could be built with FreeSBIE toolkit
simply tweaking the img.sh/flash.sh scripts to reflect its partitioning
scheme. The toolkit is also ready to welcome user-overridden scripts.
> It was generally agreed that we lacked a framework for doing really
> small systems. NanoBSD uses a subtractive approach ("WITOUT_THIS,
> WITHOUT_THAT etc") and this breaks down below 32-64 MB storage.
>=20
> For smaller systems, an additive approach would make more sense
> ("I want /bin/sh, /bin/ls ...") where the framework would do the
> nasty work of figuring out dependencies (necessary libraries and
> other files) and most of all, issue a comprehensive report that
> tells why a particular file was necessary ("/usr/share/termpcap
> is necessary because of /usr/bin/top").
FreeSBIE toolkit let you choose (optionally) which file the system must
contain in two ways: an additive approach and a substractive one. The
first approach consists in a text file containing every file which must
be copied to the system, the second one is the opposite: you can specify
in a txt which files/directories will be removed from the system.
For example pfsense build system use the second approach:
http://pfsense.com/cgi-bin/cvsweb.cgi/tools/builder_scripts/remove.list
The only problem is that selected files must be compatible with
compilation option (i.e.: you can't exclude libraries which you've
choose to link binaries with, but atm the toolkit let you do that
anyway). The improvements on the build-option survey have been a great
step forward.
> Right now we do nearly nothing.
>=20
> For our "reference platforms" we need two part webpages.
>=20
> The first half: "to get FreeBSD running on this kit, download
> this and do that", with pictures, arrows and config file lines etc.
>=20
> The second half: "Here is how to build this image on your own"
>=20
> We also need white-papers, HOW-TO's, magazine articles and so on.
>=20
> Nobody really owned up to any of this.
>=20
> We did however agree that we have the small@ mailing list and that
> we should use it more (Therefore this email).
Agree. I can write some HOWTOs about FreeSBIE or NanoBSD if it is
needed. We only have a very primordial wiki documentation at
wiki.freesbie.org.
--=20
Dario Freni (saturnero@freesbie.org)
FreeSBIE developer (http://www.freesbie.org)
GPG Public key at http://www.saturnero.net/saturnero.asc
--------------enig256F0C934D36CFDAD4DE1242
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEdbswymi72IiShysRAq9BAKChkPrD3HZID3sxORYUYXPbca2I5ACgnhON
iDTwSL4tdygnzOtgdWMKZC8=
=TdJS
-----END PGP SIGNATURE-----
--------------enig256F0C934D36CFDAD4DE1242--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4475BB2D.2090609>