From: "H. Peter Anvin" <hpa@zytor.com>
To: Will Drewry <wad@chromium.org>
Cc: linux-kernel@vger.kernel.org, kay.sievers@vrfy.org,
akpm@linux-foundation.org, Jens Axboe <jaxboe@fusionio.com>,
Namhyung Kim <namhyung@gmail.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [PATCH v3 1/2] init: add root=PARTUUID=UUID/PARTNROFF=%d support
Date: Mon, 25 Jul 2011 13:47:30 -0700 [thread overview]
Message-ID: <4E2DD662.9060404@zytor.com> (raw)
In-Reply-To: <1309468207-24199-1-git-send-email-wad@chromium.org>
On 06/30/2011 02:10 PM, Will Drewry wrote:
> Expand root=PARTUUID=UUID syntax to support selecting a root partition
> by integer offset from a known, unique partition. This approach
> provides similar properties to specifying a device and partition number,
> but using the UUID as the unique path prior to evaluating the offset.
>
> For example,
> root=PARTUUID=99DE9194-FC15-4223-9192-FC243948F88B/PARTNROFF=1
> selects the partition with UUID 99DE.. then select the next
> partition.
>
> This change is motivated by a particular usecase in Chromium OS where
> the bootloader can easily determine what partition it is on (by UUID)
> but doesn't perform general partition table walking.
>
> That said, support for this model provides a direct mechanism for the
> user to modify the root partition to boot without specifically needing
> to extract each UUID or update the bootloader explicitly when the root
> partition UUID is changed (if it is recreated to be larger, for
> instance). Pinning to a /boot-style partition UUID allows the arbitrary
> root partition reconfiguration/modifications with slightly less
> ambiguity than just [dev][partition] and less stringency than the
> specific root partition UUID.
>
Obklibcsnark:
Does anyone still doubt that as long as this kind of code exists in the
kernel that it will not get continually added to?
-hpa
prev parent reply other threads:[~2011-07-25 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 21:10 Will Drewry
2011-06-30 21:10 ` [PATCH v3 2/2] Documentation: add pointer to name_to_dev_t for root= values Will Drewry
2011-07-05 20:53 ` [PATCH v3 1/2] init: add root=PARTUUID=UUID/PARTNROFF=%d support Andrew Morton
2011-07-06 18:01 ` Will Drewry
2011-07-25 19:55 ` [PATCH] init: clean up devt_from_partuuid syntax checking and logging Will Drewry
2011-07-25 20:47 ` H. Peter Anvin [this message]
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=4E2DD662.9060404@zytor.com \
--to=hpa@zytor.com \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=jaxboe@fusionio.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=wad@chromium.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
Powered by JetHome