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

[Otavio Salvador]

On Fri, Jun 30, 2017 at 10:16 AM, Patrick Ohly <patrick.ohly at intel.com> wrote:
> On Fri, 2017-06-30 at 15:23 +0300, Ed Bartosh wrote:
>> 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.
>
> But it's not actually removed from the original roofs directory, right?
> For me, "not modified" refers to that and the files in it.

My problem is with the fstab change. If I explicitly ask wic to drop
something I know it is doing it so it is under my control.

Adding --no-fstab-change solves in an elegant way my problem.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750