Re: grubenv vs. diskfilter

[Phillip Susi <psusi@ubuntu.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/19/2013 2:31 AM, Andrey Borzenkov wrote:
>> I've been kicking around the thought that grub-pc should just
>> put grubenv in the embed area attached to the core img, and
>> grub-efi should put it in the ESP.
> 
> This still leaves the case when core.img cannot be embedded (and 
> adding extra space obviously increases chances of that) or
> delilberate blocklist installs (openSUSE defaults to booting from
> partition). And we still have PPC, SPARC and hopefully ARM to
> handle.

Blocklist installs already are unsupported and have plenty of
problems, including not working with diskfilter.  They should still be
able to work with grubenv in a regular file on a plain ext4 regular
disk partition.

As for embed size, there are really only two classes in practice: 2048
sector, which has plenty of room, and 63 sector, which already doesn't
fit for non trivial configurations including diskfilter.

> And we need some way for user space to auto-detect where
> environment block is located ...

Stick a pointer to the location in the grubenv file?

>> That would solve grubenv not working on btrfs too.
>> 
> 
> Does btrfs guarantee that bootloader area is always located on a 
> single physical device?

Not sure what you mean.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRwc9pAAoJEJrBOlT6nu75Zp0H/3Ef/f23D0tWNdPj9vzW+CkP
l79g0bfbZddPKaunpcOjccSKdjko9sFenRN8HnAegKuu0s+6ro/ir7PaR7wHkA11
+9rO+pZWEluqwcdvlR2C72ErfJ7DHvmVP+togmhzV6aeP2xvw00xr05GKZeryrND
FHG1uftp8RTxHGH28py4ta95MRzcVnGzBbkzaDz27bWuTcrijZO6rP5nc3038+8b
QMXJJnAXx49Fb7jlC0GxwgFXbdYhzqQy4tZMvQsV2WTiK38yrVnI8sJqeG7seglH
1nV9uUkxGIKGJo0TRNl6vSFkCTXiPfXM7GHny6bwzu9fpBMQZiwXVhuqhCUaqQk=
=Fk2C
-----END PGP SIGNATURE-----