grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Jones <cjns1989@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Documentation bug?
Date: Wed, 26 Jan 2011 22:53:02 -0500	[thread overview]
Message-ID: <20110127035302.GA5474@pavo.local> (raw)
In-Reply-To: <AANLkTinYU4cmpgSYkuX337d4BuT4z76n5bMK4DEi4Ywn@mail.gmail.com>

On Wed, Jan 26, 2011 at 12:46:57AM EST, KESHAV P.R. wrote:

> You can take a look at grub-mkrescue shell script in utils dir to find
> out how to create a bootable grub2 cd.

Yes, it was as simple as:

| $ mkdir /tmp/iso
| $ grub-mkrescue -o grub.iso /boot/grub
| $ growisofs.... etc.

I booted from the DVD but only got a ‘grub > ’ and it took me a good bit
of googling to figure out that I needed issue the following command to
make the grub menu appear:

| grub > configfile /boot.cfg

Of course, my setup is very basic, with a flat multi-boot menu, but all
the same, I feel that both the procedure to create the boot disk and how
to use it when recovering really need to be documented in the new
manual: In the event of a mishap, I can just slip in my custom grub
rescue disk instead of having to hunt for an install or live CD/DVD and
waste time fumbling for the correct grub command syntax to get the
machine to boot.. Priceless!

Thanks,

cj



  reply	other threads:[~2011-01-27  3:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  2:10 Documentation bug? Chris Jones
2011-01-25  2:22 ` Bruce Dubbs
2011-01-25  3:09   ` Chris Jones
2011-01-25  3:39     ` Bruce Dubbs
2011-01-26  4:58       ` Chris Jones
2011-01-25  3:07 ` richardvoigt
2011-01-26  5:25   ` Chris Jones
2011-01-26  5:46 ` KESHAV P.R.
2011-01-27  3:53   ` Chris Jones [this message]
2011-01-28 17:17 ` Colin Watson
2011-01-28 20:23   ` Chris Jones

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=20110127035302.GA5474@pavo.local \
    --to=cjns1989@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).