Hello all, On Thu, Dec 29, 2011 at 2:51 AM, Chris Larson <[email protected]> wrote:
> On Wed, Dec 28, 2011 at 6:07 PM, Leon Woestenberg > <[email protected]> wrote: > > On Thu, Dec 29, 2011 at 12:45 AM, Darren Hart <[email protected]> > > wrote: > >> > >> Poky-tiny defines a new distro policy for building tiny Linux images. > > > > 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 :) > Ah, I missed this line: o Read-only or RAMFS root filesystem However, our recipes in many ways depend on write behaviour on first boot. When under classic OE, I always had to verify each recipe for correct operation for ro fs's, and did so manually. Would be nice to cover this use case better. Regards, Leon.
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
