From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/5] #11662 - wic should mount /boot
Date: Fri, 30 Jun 2017 11:37:17 +0300 [thread overview]
Message-ID: <20170630083717.GA788@linux.intel.com> (raw)
In-Reply-To: <20170629083942.GA14649@linux.intel.com>
On Thu, Jun 29, 2017 at 11:39:42AM +0300, Ed Bartosh wrote:
> On Wed, Jun 28, 2017 at 10:32:27AM -0300, Otavio Salvador wrote:
> > On Wed, Jun 28, 2017 at 4:31 AM, Ed Bartosh <ed.bartosh@linux.intel.com> wrote:
> > > On Tue, Jun 27, 2017 at 05:41:45PM -0300, Fabio Berton wrote:
> > >> The last patch I sent is here:
> > >> https://patchwork.openembedded.org/patch/139252/
> > >>
> > >> We're using this patch internally with Pyro branch. I can rework to
> > >> apply on master.
> > >>
> > >> On 06/27/2017 05:35 PM, Otavio Salvador wrote:
> > >> >On Tue, Jun 27, 2017 at 10:28 AM, Ed Bartosh <ed.bartosh@linux.intel.com> wrote:
> > >> >>The patchset also fixes long standing bug: wic updated fstab
> > >> >>inplace in rootfs directory. This causes other tasks working with
> > >> >>rootfs directory to produce incorrect results or crash. This is
> > >> >>fixed by copying rootfs to the temporary directory before updating
> > >> >>fstab.
> > >> >
> > >> >As you is working on this, please also include Fabio's patch on the
> > >> >patchset. It includes a command like option to disable fstab change at
> > >> >all. For delta-based updates this is imperative.
> > >> >
> > >> >Fabio, could you point him the last patch revision?
> > >> >
> > >
> > > Do we really need that?
> > >
> > > JFYI: Mount point in .wks is an optional field. It makes sense to use it only
> > > if partition needs to be mounted on boot. fstab will not be updated
> > > unless it's explicitly requested by specifying mount points in .wks
> >
> > It should have support to not touch it. For images which we intend to
> > do delta updates, the content cannot be changed besides the original
> > rootfs generation. So yes, we need that.
>
> 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
In future if any other rootfs changing functionality is added to wic it must
conflict with this option.
Does this make sense?
--
Regards,
Ed
next prev parent reply other threads:[~2017-06-30 8:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 13:28 [PATCH v2 0/5] #11662 - wic should mount /boot Ed Bartosh
2017-06-27 13:28 ` [PATCH v2 1/5] wic: copy rootfs directory before changing fstab Ed Bartosh
2017-07-04 22:16 ` Burton, Ross
2017-07-05 8:01 ` Ed Bartosh
2017-07-05 10:38 ` Burton, Ross
2017-06-27 13:28 ` [PATCH v2 2/5] wic: use absolute paths in rootfs plugin Ed Bartosh
2017-06-27 13:28 ` [PATCH v2 3/5] wic: rootfs: fix rootfs path reporting Ed Bartosh
2017-06-27 13:28 ` [PATCH v2 4/5] wic: rootfs: make copied rootfs unique Ed Bartosh
2017-06-27 13:28 ` [PATCH v2 5/5] wic: add /boot mount point to fstab by default Ed Bartosh
2017-06-27 20:35 ` [PATCH v2 0/5] #11662 - wic should mount /boot Otavio Salvador
2017-06-27 20:41 ` Fabio Berton
2017-06-28 7:31 ` Ed Bartosh
2017-06-28 13:32 ` Otavio Salvador
2017-06-29 8:39 ` Ed Bartosh
2017-06-30 8:37 ` Ed Bartosh [this message]
2017-06-30 9:02 ` Patrick Ohly
2017-06-30 12:23 ` Ed Bartosh
2017-06-30 13:16 ` Patrick Ohly
2017-06-30 13:58 ` Otavio Salvador
2017-06-30 15:37 ` Ed Bartosh
2017-06-30 15:44 ` Ed Bartosh
2017-06-30 17:33 ` Otavio Salvador
2017-06-30 18:34 ` Patrick Ohly
2017-07-03 7:31 ` Ed Bartosh
2017-07-03 7:53 ` Patrick Ohly
2017-07-03 8:59 ` Ed Bartosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170630083717.GA788@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox