From: Phillip Susi <psusi@ubuntu.com>
To: Andrey Borzenkov <arvidjaar@gmail.com>,
The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub-install hidden options weirdness
Date: Wed, 25 Jun 2014 13:44:28 -0400 [thread overview]
Message-ID: <53AB0A7C.2090800@ubuntu.com> (raw)
In-Reply-To: <20140625213335.3e683422@opensuse.site>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/25/2014 1:33 PM, Andrey Borzenkov wrote:
> This could be considered as endorsement to continue to use it ...
>
No, saying "dont' use this because it is depreciated" is exactly the
opposite endorsing its continued use.
>> 2) It seems that --root-directory has been overloaded to specify
>> the efi system directory. This seems like it was the wrong thing
>> to do and again, is totally undocumented.
>
>
> We already have --efi-directory. Why would you want to endorse
> this archaic usage?
I don't: I'm pointing out that this usage seems like it was an
undocumented mistake and it should be removed.
>> 3) It appears that --grub-setup used to allow you to specify an
>> alternate program to run instead of grub-setup. Now it seems to
>> check if its argument is "setup" and if so, has the same affect
>> as - --no-bootsector, and otherwise has no effect. This seems
>> completely wrong.
>
>
> This covers two common use cases known to me a) using it from
> within build directory with --grub=setup=./grub-setup and b) using
> it to disable actual installation with --grub-setup=/bin/true.
> Current code is compatible with them.
No, it is not. The current code ignores all values of --grub-setup
other than --grub-setup=setup.
>> 4) The similar arguments --grub-mkrelpath, --grub-probe, -
>> --grub-editenv, and --font are accepted and completely ignored.
>> If the option no longer works, it should be removed rather than
>> silently ignored. At least that way you don't have people using
>> it and wondering why it isn't working.
>
>
> Again - common use case is using just built grub without installing
> it. Do you have example of other non-trivial use cases?
Again, they are now completely ignored and have zero effect.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTqwp8AAoJEI5FoCIzSKrwhYsH/00j0500OF7ItHiwtFlLrQVz
qyKw+fbjEr3YpesLza9x9ov2T8Peh6Z1sQVFc6RqZwl5KtfF7Tf4lWJ2ktmpzW7q
qQMe/5njOd0Z0p68WOYPjz5kQU6Bsn6KqGgkSadDwISo+pLfeRazmGPmGKZTJ60B
PCDK4ksT8DU3rbn5446mqpAJuWOGTn+R5ijdkCxYVJG6aKild7vc1aEXOW7gkzFF
8R5xREB+RE//LY5eEtms2++xXej107hkS1Jv/bIaNBGuqrFQGjfjOPxmo0Ag9tP8
AM6pGZyxniGJgWg8S7kL6mGi13jK8j/JhQejpEp5DXEJf2osHUFP0lK0qkogjFM=
=9o/P
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-06-25 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 14:13 grub-install hidden options weirdness Phillip Susi
2014-06-25 17:33 ` Andrey Borzenkov
2014-06-25 17:44 ` Phillip Susi [this message]
2014-06-25 18:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=53AB0A7C.2090800@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.