On Wed, Dec 28, 2011 at 6:07 PM, Leon Woestenberg <sidebranch.openembed...@gmail.com> wrote: > On Thu, Dec 29, 2011 at 12:45 AM, Darren Hart <dvh...@linux.intel.com> > wrote: >> >> V3: >> o Rebase on master >> o Dependent on oe-core series "Fixes for tiny distros and >> linux-yocto-tiny" >> >> RFC V2: >> o Use VIRTUAL-RUNTIME_keymaps as suggested by Martin Jansa >> o Drop poky-common abstraction as suggested by Richard Purdie in >> favor of POKY_DEFAULT_EXTRA_R* variables. >> >> Poky-tiny defines a new distro policy for building tiny Linux images. >> Rather >> > > Such images are useful for small Linux firmwares, both often also require a > read-only fs img. > > Does this current image require write access at first boot?
That's a good question. I wonder how well we support ro rootfs today. It'd be nice to have a declarative mechanism to control use of a unioning filesystem and/or symlinking or bind mounts. poky-tiny does say that one of its high level policy guidelines is to have a ro rootfs, so if it doesn't do it today, presumably it's just a matter of time :) -- Christopher Larson _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
