linux-kernel - Re: [PATCH] init: add root=PARTUUID=UUID+/-%d support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3887.1307024686@turing-police.cc.vt.edu>
Date:	Thu, 02 Jun 2011 10:24:46 -0400
From:	Valdis.Kletnieks@...edu
To:	Will Drewry <wad@...omium.org>
Cc:	Kay Sievers <kay.sievers@...y.org>, linux-kernel@...r.kernel.org,
	Jens Axboe <jaxboe@...ionio.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Namhyung Kim <namhyung@...il.com>,
	Trond Myklebust <Trond.Myklebust@...app.com>
Subject: Re: [PATCH] init: add root=PARTUUID=UUID+/-%d support

On Thu, 02 Jun 2011 08:48:16 CDT, Will Drewry said:

> Good call!  I'll take a pass at integrating that. I can see a couple
> different ways of handling the parsing (e.g., when and what does it
> affect).  Do you think it would make sense to keep it isolated to just
> being a PARTUUID subargument or would it make more sense for
> PARTNROFF= to be evaluated as a generic root= attribute?  I can see
> benefits to both, but one is considerably more minimal to implement :)
>  [Maybe I'll try both and see how they look.]

I've seen multi-boot configs that have several disks similarly partitioned - a /boot
on /dev/sdN1 and / on /dev/sdN2.  For those configs, being able to say "use
partition 2 of whatever disk you booted" would be one less thing you have
to worry about getting out of sync.


Content of type "application/pgp-signature" skipped