From: Tom Rini <trini@konsulko.com>
To: Ed Bartosh <ed.bartosh@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] wic: When using --use-uuid make sure that we update the fstab with PARTUUID
Date: Mon, 6 Nov 2017 07:44:17 -0500 [thread overview]
Message-ID: <20171106124417.GF32663@bill-the-cat> (raw)
In-Reply-To: <20171106100829.nqhna6hugyqe636k@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]
On Mon, Nov 06, 2017 at 12:08:29PM +0200, Ed Bartosh wrote:
> On Fri, Nov 03, 2017 at 08:51:50AM -0400, Tom Rini wrote:
> > On Fri, Oct 20, 2017 at 09:15:05AM -0400, Tom Rini wrote:
> > > On Tue, Oct 10, 2017 at 05:01:49PM -0400, Tom Rini wrote:
> > > > On Thu, Sep 21, 2017 at 01:46:16PM -0400, Tom Rini wrote:
> > > > > When we have been told to use the UUID we should also update the fstab
> > > > > to make use of PARTUUID instead of hard-coding the device in question.
> > > > > This will make the resulting image much more portable.
> > > > >
> > > > > Signed-off-by: Tom Rini <trini@konsulko.com>
> > > > > ---
> > > > > scripts/lib/wic/plugins/imager/direct.py | 9 ++++++---
> > > > > 1 file changed, 6 insertions(+), 3 deletions(-)
> > > >
> > > > Where we did we end up with this? Ed pointed out that you can tell wic
> > > > to use a specific UUID, so reproducible images are not a problem. And
> > > > making images that are readily portable is why other distros use
> > > > UUID/LABEL and not device names as much as possible. I personally enjoy
> > > > being able to put an image on uSD for minnow and have it work :)
> > > > Thanks!
> > >
> > > ping?
> >
> > I was just reminded about the real problems this solves (swap isn't
> > /dev/sda3, boot is being excessively slow), so, ping?
> >
>
> I'm generally ok with the patchset. The only thing I'm thinking of is if busybox mount
> supports PARTUUID syntax in fstab. Can you check this, please?
>
> I'd like to see Otavio's confirmation that --uuid option solves
> his reproducible builds concern.
>
> Can you rebase your patchset on top of current master?
Yes, OK.
> It would be also nice to get this functionality covered by tests.
OK, but what part of oe-selftest, and how exactly? Can one easily check
the resulting fstab?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-11-06 12:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 17:46 [PATCH 1/2] wic: When using --use-uuid make sure that we update the fstab with PARTUUID Tom Rini
2017-09-21 17:46 ` [PATCH 2/2] wic: Update canned-wks for systemd to use UUID everywhere Tom Rini
2017-09-21 21:15 ` [PATCH 1/2] wic: When using --use-uuid make sure that we update the fstab with PARTUUID Otavio Salvador
2017-09-21 21:19 ` Tom Rini
2017-09-21 21:20 ` Mark Hatle
2017-09-21 21:21 ` Tom Rini
2017-09-28 12:26 ` Ed Bartosh
2017-10-10 21:01 ` Tom Rini
2017-10-20 13:15 ` Tom Rini
2017-11-03 12:51 ` Tom Rini
2017-11-06 10:08 ` Ed Bartosh
2017-11-06 11:36 ` Otavio Salvador
2017-11-06 12:44 ` Tom Rini
2017-11-06 12:51 ` Otavio Salvador
2017-11-06 13:02 ` Tom Rini
2017-11-07 8:11 ` Ed Bartosh
2017-11-07 14:54 ` Tom Rini
2017-11-08 11:20 ` Ed Bartosh
2017-11-08 15:00 ` Tom Rini
2017-11-08 14:30 ` Ed Bartosh
2017-11-06 12:44 ` Tom Rini [this message]
2017-11-07 8:27 ` Ed Bartosh
2017-11-07 14:55 ` Tom Rini
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=20171106124417.GF32663@bill-the-cat \
--to=trini@konsulko.com \
--cc=ed.bartosh@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox