From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] UUID support in installer (poky-contrib: ed/oe-core/uuid-init-install)
Date: Mon, 15 Jun 2015 19:10:37 +0300 [thread overview]
Message-ID: <1434384647-2901-1-git-send-email-ed.bartosh@linux.intel.com> (raw)
Hi,
This patchet adds support of GPT partition table and
UUID support to initramfs installer scripts.
Using UUID in favor of device names is more reliable as
UUID names are persistent.
Device names can change as the order of adding device nodes
is arbitrary. This sometimes results in device names switching
on each boot, which can cause system fail to boot.
Persistent naming solves these issues.
Implementation details:
Used partition UUID in kernel command line to specify root partition.
Used partition UUID in /etc/fstab to specify swap partition.
Used filesystem UUID in /etc/fstab to specify boot partition.
Code cleanup and usability fixes were done along the way. They're also
included into this patchset.
Patchest was tested on NUC device in both EFI and non-EFI modes.
See more details in [YOCTO #6101]
NOTE: Please drop the following pending patches as they're included into the patchset:
[OE-core] [PATCH] image-live: Set syslinux timeout to 5s
[OE-core] [PATCH] initramfs-live-install: Add gptdisk to initramfs
[OE-core] [PATCH] init-install-efi: Implement UUID support
Please review
Ed Bartosh (10):
image-live: Set syslinux timeout to 5s
initramfs-live-install: Add blkid to initramfs
busybox: Enable UUID-related options
init-install-efi: Implement UUID support
init-install: Use GPT table with GRUB 2
init-install: Implement UUID support
init-install: Specify filesystem type in parted command line
init-install: Specify partition name in parted command line
init-install: code cleanup: Replace tabs with spaces
init-install: code cleanup: replace /dev/$device -> $device
meta/classes/image-live.bbclass | 2 +-
meta/recipes-core/busybox/busybox/defconfig | 8 +-
.../initrdscripts/files/init-install-efi.sh | 90 ++++++-------
.../initrdscripts/files/init-install.sh | 146 +++++++++++++--------
.../initramfs-live-install-efi_1.0.bb | 2 +-
.../initrdscripts/initramfs-live-install_1.0.bb | 2 +-
6 files changed, 143 insertions(+), 107 deletions(-)
--
Ed
next reply other threads:[~2015-06-15 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 16:10 Ed Bartosh [this message]
2015-06-15 16:10 ` [PATCH 01/10] image-live: Set syslinux timeout to 5s Ed Bartosh
2015-06-15 16:10 ` [PATCH 02/10] initramfs-live-install: Add blkid to initramfs Ed Bartosh
2015-06-15 16:10 ` [PATCH 03/10] busybox: Enable UUID-related options Ed Bartosh
2015-06-15 16:10 ` [PATCH 04/10] init-install-efi: Implement UUID support Ed Bartosh
2015-06-15 16:10 ` [PATCH 05/10] init-install: Use GPT table with GRUB 2 Ed Bartosh
2015-06-15 16:10 ` [PATCH 06/10] init-install: Implement UUID support Ed Bartosh
2015-06-15 16:10 ` [PATCH 07/10] init-install: Specify filesystem type in parted command line Ed Bartosh
2015-06-15 16:10 ` [PATCH 08/10] init-install: Specify partition name " Ed Bartosh
2015-06-15 16:10 ` [PATCH 09/10] init-install: code cleanup: Replace tabs with spaces Ed Bartosh
2015-06-15 16:10 ` [PATCH 10/10] init-install: code cleanup: replace /dev/$device -> $device 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=1434384647-2901-1-git-send-email-ed.bartosh@linux.intel.com \
--to=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