From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Q5DOz-0005V0-NE for mharc-grub-devel@gnu.org; Thu, 31 Mar 2011 04:38:49 -0400 Received: from [140.186.70.92] (port=55483 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q5DOw-0005RA-Ha for grub-devel@gnu.org; Thu, 31 Mar 2011 04:38:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q5DOq-0001UW-Tn for grub-devel@gnu.org; Thu, 31 Mar 2011 04:38:45 -0400 Received: from smarthost01.mail.zen.net.uk ([212.23.3.140]:44646) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q5DOq-0001U1-MT for grub-devel@gnu.org; Thu, 31 Mar 2011 04:38:40 -0400 Received: from [82.69.3.149] (helo=[192.168.1.65]) by smarthost01.mail.zen.net.uk with esmtp (Exim 4.63) (envelope-from ) id 1Q5DOo-0004sB-0f for grub-devel@gnu.org; Thu, 31 Mar 2011 08:38:38 +0000 Message-ID: <4D943D8D.8060501@zen.co.uk> Date: Thu, 31 Mar 2011 09:38:37 +0100 From: Barry Jackson User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-UK; rv:1.9.2.17pre) Gecko/20110330 Lightning/1.0b2 Lanikai/3.1.10pre MIME-Version: 1.0 To: grub-devel@gnu.org References: <20110329124031.GK9163@riva.ucam.org> <4D937DDE.1060600@zen.co.uk> <20110330195159.GS9163@riva.ucam.org> In-Reply-To: <20110330195159.GS9163@riva.ucam.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-Smarthost01-IP: [82.69.3.149] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 212.23.3.140 Subject: Re: [PATCH] Improve documentation of BIOS installation X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 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, 31 Mar 2011 08:38:48 -0000 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