From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] doc: document config_directory and config_file variables
Date: Sun, 8 Nov 2015 09:55:29 +0300 [thread overview]
Message-ID: <563EF1E1.3070706@gmail.com> (raw)
In-Reply-To: <563E822F.3040503@gmx.fr>
08.11.2015 01:58, Arbiel (gmx) пишет:
>
>>>
>>> undocumented command parameter : --hint (command search), and some other
>>> --hint.something which I haven't been able to localise just now.
>>>
>>
>> Which command?
> search.
> And I just read in a grub.cfg file, not one of mine the line
>
> search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 427b86fb-cc66-46be-ad68-ade86794af55
>
> which shows some "--hint" parameters. What do they all mean ?
They are intended to optimize search at boot time. They contain guessed
firmware device names. If this name was guessed correctly, it avoids
searching across all devices at boot time.
In practice for Linux on i386-pc it does not really work because to
reliably guess BIOS HDD number you need EDD and with 32 bit Linux boot
protocol EDD information must be provided by bootloader.
This is again something that users should not be normally concerned with
- these hints are added automatically by probing code. We could add "see
development manual for additional options" if we had development manual
... but yes, description of grub-mkconfig framework and which high-level
functions are provided is missing.
prev parent reply other threads:[~2015-11-08 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 10:21 [PATCH] doc: document config_directory and config_file variables Andrey Borzenkov
2015-11-07 13:45 ` Vladimir 'phcoder' Serbinenko
2015-11-07 19:51 ` Arbiel (gmx)
2015-11-07 20:09 ` Andrei Borzenkov
2015-11-07 22:58 ` Arbiel (gmx)
2015-11-08 6:55 ` Andrei Borzenkov [this message]
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=563EF1E1.3070706@gmail.com \
--to=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.