From: Tom Rini <trini@konsulko.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 1/2] wic: When using --use-uuid make sure that we update the fstab with PARTUUID
Date: Thu, 21 Sep 2017 17:19:50 -0400 [thread overview]
Message-ID: <20170921211950.GL30205@bill-the-cat> (raw)
In-Reply-To: <CAP9ODKquj79BCNcRg66C+GSbDeoAeO6nb61Nk2FQG75w_CCTjg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On Thu, Sep 21, 2017 at 06:15:56PM -0300, Otavio Salvador wrote:
> On Thu, Sep 21, 2017 at 2:46 PM, Tom Rini <trini@konsulko.com> 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>
>
> Adding more features which changes the fstab goes to the opposite
> direction of reproducible builds; is it desirable?
UUIDs are already something that would be different every time. It's
also (at least with just this patch) opt-in. The second patch shows
that it's quite useful (and there's real-world examples, ie Minnow SD
card vs USB/SATA, various ARM systems where mmcblkX can change depending
on regulators.
--
Tom
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-09-21 21:19 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 [this message]
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
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=20170921211950.GL30205@bill-the-cat \
--to=trini@konsulko.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