2012/2/21 Amit Kucheria amit.kucheria@linaro.org
On Mon, Feb 20, 2012 at 10:03 PM, C.A, Subramaniam subramaniam.ca@ti.com wrote:
On Mon, Feb 20, 2012 at 1:55 PM, Wookey wookey@wookware.org wrote:
+++ C.A, Subramaniam [2012-02-20 13:32 -0600]:
On Mon, Feb 20, 2012 at 12:40 PM, Wookey wookey@wookware.org wrote: Would there be a buildroot like setup? Like Wookey mentioned size does matter.
No, if you want to use buildroot, use buildroot (or openbricks, or yocto, or OE). Debian/Ubuntu are binary distros and there is no mileage in trying to occupy that space when other distros already do it well.
Making it relatively painless to rebuild or cross-rebuild your package-set debian-style is a useful goal, but not supporting loads of different package config options - that is something a source-based distro can do so much better.
We do plan to support minimal builds for bootstrapping purposes which might be useful in this regard, but that's not really what it's for.
Well minimal is all I care... not buildroot. But I would expect it to be < 20M in size. Does that make sense.... or am i speaking gibberish :-) ?
Doesn't the nano flavour take care of this?
Nano rootfs is 33M compressed tarball which expands to 95M.
That's "small", not "embedded" ;)
That said, these two already make it pretty obvious that for embedded it only makes sense to build the rootfs in a custom manner:
19M binary/boot/filesystem.dir/var/lib/apt 6,7M binary/boot/filesystem.dir/var/lib/dpkg
rather than using a ready-to-go-and-updateable distribution.
-- Kalle Vahlman, zuh@iki.fi Powered by http://movial.com Interesting stuff at http://sandbox.movial.com