[OE-core] [PATCH v2 0/5] #11662 - wic should mount /boot

Ed Bartosh ed.bartosh at linux.intel.com
Fri Jun 30 12:23:30 UTC 2017


On Fri, Jun 30, 2017 at 11:02:13AM +0200, Patrick Ohly wrote:
> On Fri, 2017-06-30 at 11:37 +0300, Ed Bartosh wrote:
> > > I'm not sure I understand this. If you don't want fstab to be
> > changed
> > > you should not specify mount points in .wks
> > > There is only one reason to have mount points in .wks: to make wic
> > to
> > > change /etc/fstab, which you apparently don't want. So, don't
> > specify
> > > mount points and you'll have what you want.
> > > 
> > > Having additional option for this looks redundand to me.
> > 
> > After thinking a bit more about it I'd propose to have global wic
> > option
> > to avoid rootfs content changes. Not just fstab updates, but any
> > changes. For now this option (--no-rootfs-update ?) should prevent
> > creating
> > images if either mount points are specified or --exclude-path is used
> > in .wks
> 
> Why does --exclude-path conflict with --no-rootfs-update? Is that a
> conceptual problem or an implementation problem?
>

I thought that removing directories from original rootfs is a
modification.

> If I'm not mistaken, --exclude-path merely means "take this rootfs, but
> exclude certain parts". That's in line with --no-rootfs-update == "do
> not modify the content of the rootfs", as it just helps with choosing
> where content goes (the "single rootfs" -> "different partitions"
> approach).
That's questionable statement, but I agree it makes sense in some cases.
If nobody objects I'm ok with this. Let's assume that removing part of
the content is not a modifiation :)

--
Regards,
Ed



More information about the Openembedded-core mailing list