From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1VZ9OS-0004KH-W9 for mharc-grub-devel@gnu.org; Wed, 23 Oct 2013 21:07:21 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52490) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZ9OJ-0004JO-A4 for grub-devel@gnu.org; Wed, 23 Oct 2013 21:07:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VZ9OA-0003jq-TG for grub-devel@gnu.org; Wed, 23 Oct 2013 21:07:11 -0400 Received: from mail-ee0-x230.google.com ([2a00:1450:4013:c00::230]:55975) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZ9OA-0003ji-Kt for grub-devel@gnu.org; Wed, 23 Oct 2013 21:07:02 -0400 Received: by mail-ee0-f48.google.com with SMTP id e50so742672eek.7 for ; Wed, 23 Oct 2013 18:07:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=fV2VlVRU1ZbVwcEr3cE9tzIvFI81BF/AnSe8KY32ock=; b=CXOOszl2xkcK43kpkkOzjcltgr/jpTMHbtPu7L+vnOCkLZQ/AegQ4xEBCh6J0QxuFW aQbf+Y/KdObvmqqfpGFx2UTKrfCAUapV/1T3bw88u6JG8AytQNWL7fQApElZyYJfr30z MWwmnBVQGdmuoAJpXCUtSeq9Py0tEYJRx2ZoI3X2ejZOJdEKLTrwLGVrHDspxm2T2Epb C6v24aLfL39RGsi+oHSPdMREpXDjH106VMWJl3uW3TRSy+aGebmx/MudSweV27nPeN4N acqkEO8yFaLYw6MMmQeLRMeJSzJhCQ3/MVGSL1y4o6pqVkArWjYKzVvU5l5bO4RF2YUm OcNw== X-Received: by 10.15.53.132 with SMTP id r4mr107196eew.5.1382576821374; Wed, 23 Oct 2013 18:07:01 -0700 (PDT) Received: from [192.168.1.16] (31-249.1-85.cust.bluewin.ch. [85.1.249.31]) by mx.google.com with ESMTPSA id m54sm76771161eex.2.2013.10.23.18.07.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Oct 2013 18:07:00 -0700 (PDT) Message-ID: <526872B4.4080903@gmail.com> Date: Thu, 24 Oct 2013 03:07:00 +0200 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131005 Icedove/17.0.9 MIME-Version: 1.0 To: grub-devel@gnu.org Subject: Re: Grub PARTUUID vs UUID References: <52686BB2.2030004@gmail.com> In-Reply-To: <52686BB2.2030004@gmail.com> X-Enigmail-Version: 1.5.1 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="----enig2OFDIWMMNQFPPBUPCISOU" X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::230 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2013 01:07:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2OFDIWMMNQFPPBUPCISOU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 24.10.2013 02:37, FireIcer wrote: > Hey >=20 > I am looking at the impact in general with changing the grub-mkconfig > scan not to pickup and update the grub.cfg with the UUID code but the > PARTUUID code instead. >=20 > At present the situation forces the user to enable a working initramfs > to work around grub2. >=20 > Why is this a problem? well because initramfs can be used to decorate > ones boot display and many other things other than it's intended use. > This means that UUID as a parameter in the grub.cfg wont work. I > understand that Windows partitions use a shortened UUID only, so > compatibility needs to be able to differentiate between the two types. > UUID for windows partitions and PARTUUID for other GPT partitions. >=20 > I cant understand why UUID's were used rather than PARTUUID's. If the > code was modified to use PARTUUID's instead, what would be the impact > on compatibility on a large scale. >=20 Please do not confuse how GRUB finds disks itself and what is passed as root=3D parameter. Those are separate discussions and second one touches exclusively grub-mkconfig. > If people enable the option in Grub to use PARTUUID's then surely they > would know to setup GPT disks. I feel it should be encouraged to > remove the MBR tables as it is old and useless not to mention tied in > to microsoft products. Completely wrong. MBR partition table does not imply any microsoft product. It's used for very different disks in different systems, some of them never had windows at all. Also this is wrong to say that there is no partition ID in MBR. There is MBRID which is concatenated with partition offset to give the ID. > Now we have an Intel contribution "GPT" which > works much better is it not right that we encourage the use of GPT > over MBR? >=20 Intel is very low on my esteem with all the crapware which got out of it recently. > The point of this post is to raise alarm to the fact UUID's wont work > without initramfs or initrd as so to read the UUID but the kernel can > read PARTUUID without the use of initrd. Would that not be far better > to not rely on init ram filesystem? >=20 This sounds like Linux limitation, doesn't it? > A option/switch parameter when using mkconfig to output the cfg file > maybe? >=20 I don't see any patch attached. ------enig2OFDIWMMNQFPPBUPCISOU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iF4EAREKAAYFAlJocrQACgkQNak7dOguQgk0hAD+OWtdNFYJnVGeHsWxt91GWhAx p/4h95kCVo4MOvLmK+ABAMM4x9c5bikd8w6sghXkXta4wFIGQlFmEcc0/Vs0YMQm =Zblk -----END PGP SIGNATURE----- ------enig2OFDIWMMNQFPPBUPCISOU--