All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] wic: Prevent duplicate entries on fstab
Date: Fri, 10 Mar 2017 14:43:52 +0100	[thread overview]
Message-ID: <1489153432.7785.448.camel@intel.com> (raw)
In-Reply-To: <CAP9ODKoVRj+Fqx1W4U=Nr1RgFvQgbvwrzatBpv==PpTJX1P3NA@mail.gmail.com>

On Fri, 2017-03-10 at 10:32 -0300, Otavio Salvador wrote:
> On Fri, Mar 10, 2017 at 4:33 AM, Patrick Ohly <patrick.ohly@intel.com> wrote:
> > Suppose IMAGE_FSTYPES = "ext4 wic", and the WKS_FILE has multiple
> > partitions and thus needs more entries in /etc/fstab than the
> > single-partition "ext4" - the result of do_rootfs simply cannot work for
> > both.
> 
> That is the point. If the machine requires to use multiple partitions
> the ext4 should have the /etc/fstab ready for use when deployed.

My thinking was a bit different. I had in mind a setup where the "ext4"
format as used by qemu has all files of the rootfs in a single
partition, whereas the wic image splits out the data into multiple
partitions (it recently gained such a feature).

This could be made to work if wic knew how to change fstab without
rewriting the root filesystem. But as that can't be done, such a
combination of different image formats is only possible for a rootfs
which always works with just a single partition.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-03-10 13:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 18:13 [PATCH] wic: Prevent duplicate entries on fstab Fabio Berton
2017-02-24 23:02 ` Burton, Ross
2017-03-03 12:12   ` Fabio Berton
2017-03-03 13:49     ` Burton, Ross
2017-03-06 14:00       ` Fabio Berton
2017-03-06 18:13         ` Ed Bartosh
2017-03-06 18:48           ` Fabio Berton
2017-03-06 19:07             ` Ed Bartosh
2017-03-09 21:11               ` Otavio Salvador
2017-03-10  7:33                 ` Patrick Ohly
2017-03-10 13:32                   ` Otavio Salvador
2017-03-10 13:43                     ` Patrick Ohly [this message]
2017-03-10 13:51                       ` Otavio Salvador

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=1489153432.7785.448.camel@intel.com \
    --to=patrick.ohly@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.