All of lore.kernel.org
 help / color / mirror / Atom feed
From: Barry Jackson <zen25000@zen.co.uk>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Improve documentation of BIOS installation
Date: Thu, 31 Mar 2011 09:38:37 +0100	[thread overview]
Message-ID: <4D943D8D.8060501@zen.co.uk> (raw)
In-Reply-To: <20110330195159.GS9163@riva.ucam.org>

On 30/03/11 20:52, Colin Watson wrote:
> On Wed, Mar 30, 2011 at 08:00:46PM +0100, Barry Jackson wrote:
>> On 29/03/11 13:40, Colin Watson wrote:
>>> With http://grub.enbug.org/BIOS_Boot_Partition being down at the moment,
>>> I went to look at what corresponding documentation there was in the
>>> manual.........
>>
>> One question that I cannot find an answer for in the manual here :-
>> 18.1 GRUB only offers a rescue shell
>> It explains that the only available commands are ls, set, unset and insmod.
>> So what use is it?
>> Assuming that a module is missing or a variable is incorrect, and
>> these are corrected with insmod and set - what next?
>> I can see no way to boot after correcting things without a 'boot'
>> command available. If you can't boot, why bother with set or insmod.
>> I just don't get it!
>
> The manual even answers this question directly with an example:
>
>    http://www.gnu.org/software/grub/manual/grub.html#GRUB-only-offers-a-rescue-shell
>
> See the example after "then you can correct this and enter normal mode
> manually".
>
> (Once you are in normal mode with a correct prefix, then commands will
> be autoloaded, although you could insmod them manually if you really
> wanted.  But this should be self-explanatory once you do it, as entering
> normal mode will give you a GRUB menu.)
>
> I've extended the text you refer to
> (http://www.gnu.org/software/grub/manual/grub.html#Commands) to link to
> this troubleshooting section.  It'll be there the next time we push to
> the website.
>
> Regards,
>

Thanks Colin,
I was being a bit dim - or maybe it was late.
I had not grasped the concept of the 'normal' command which was not 
included in the list of available commands.

It's much clearer now.

Maybe next time I'm hit with a rescue shell I may just be able to boot 
from it ;-)

Barry


  reply	other threads:[~2011-03-31  8:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 12:40 [PATCH] Improve documentation of BIOS installation Colin Watson
2011-03-29 13:11 ` Pádraig Brady
2011-03-29 13:29   ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-03-29 15:12   ` Colin Watson
2011-03-30 15:10     ` Pádraig Brady
2011-03-29 16:26 ` richardvoigt
2011-03-30 19:00 ` Barry Jackson
2011-03-30 19:08   ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-03-30 19:52   ` Colin Watson
2011-03-31  8:38     ` Barry Jackson [this message]
2011-04-12 12:33       ` Colin Watson

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=4D943D8D.8060501@zen.co.uk \
    --to=zen25000@zen.co.uk \
    --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.