All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Fabio Berton <fabio.berton@ossystems.com.br>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] wic: Prevent duplicate entries on fstab
Date: Mon, 6 Mar 2017 21:07:28 +0200	[thread overview]
Message-ID: <20170306190728.GA19275@linux.intel.com> (raw)
In-Reply-To: <bad2d5fb-ee7d-e32f-7f97-da988d126f0f@ossystems.com.br>

On Mon, Mar 06, 2017 at 03:48:00PM -0300, Fabio Berton wrote:
> Hi Ed,
> 
> The main motivation to my patch is prevent to duplicate entries. For
> example, if I add to my fstab line:
> 
> LABEL=data           /data                auto defaults              0  1
> 
> and add to wsk file:
> 
> part /data --ondisk mmcblk0 --fstype=ext4 --label data --align 8192
> --size 500M --extra-space 0
> 
> Final fstab will have two entries for /data.
This can be easily avoided if you remove leading slash:
part data --ondisk mmcblk0 --fstype=ext4 --label data --align 8192 --size 500M --extra-space 0


> 
> In most Linux distros mount /boot partition, if we have kernel image
> or boot script to update we need to mount /boot partition. Why the
> reason to not mount /boot?
>
The code that skips / and /boot was brought to wic codebase more than 4
years ago: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=75c143a7aef46ecea07cf33edd2b1a0192e10149

I don't know exact reason to be honest. However, I think we need to be careful with this
kind of legacy. It doesn't mean we shouldn't remove it, but it should
not be done as a side effect of the patch addressing absolutely
different issue, I believe.

> >>>    For qemuarm machines I get the error:
> >>>
> >>>    | DEBUG: Executing python function set_image_size
> >>>    | DEBUG: Python function set_image_size finished
> >>>    | DEBUG: Executing shell function do_image_wic
> >>>    | Error: Please build syslinux first

Sorry, missed this. It looks like you're trying to use plugin that
depends on syslinux. For example, directdisk.wks uses bootimg-pcbios,
which uses syslinux. It's x86 specific and should not be used on arm.

--
Regards,
Ed


  reply	other threads:[~2017-03-06 19:21 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 [this message]
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
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=20170306190728.GA19275@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=fabio.berton@ossystems.com.br \
    --cc=openembedded-core@lists.openembedded.org \
    /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.