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]
Date:	Fri, 7 Jan 2011 16:13:27 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Kirill Smelkov <kirr@...dau.phys.spbu.ru>
Cc:	Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org,
	Will Drewry <wad@...omium.org>
Subject: Re: [RESEND PATCH 1/2] init: Add support for root devices to be
 specified by partition name

On Fri, Jan 7, 2011 at 12:42, Kirill Smelkov <kirr@...dau.phys.spbu.ru> wrote:
>  [ In follow-up to b5af921e ]
>
> Besides GUIDs, there are also partition names stored in an EFI GPT
> partition table. So let's add support for root to be located not only by
> GUID, but also by partition names, like this:
>
>    root=PARTNAME=<partition-name>

Are you sure about this? What's your use case?

Generally, we really don't recommend ever to use any simple labels for
critical stuff -- not from filesystems, not from partitions.

I know that some distros did that, but this is pretty misguided, and I
think, should not be extended to any new facility, unless there is a
good use case for that.

Labels are not unique and in the general case absolutely not useful to
uniquely identify data on a disk. They only make sense for humans, or
interfaces that visualize things -- they should usually not be used in
any environment that reliably needs to identify a certain partition.
We have the uuids  for a reason.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ