public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Александър Л. Димитров" <aleks_d@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: grub chainloader
Date: Wed, 18 Jul 2007 15:30:43 +0200	[thread overview]
Message-ID: <20070718133043.GA6012@brmbr.sfs.uni-tuebingen.de> (raw)
In-Reply-To: <bf6b6d5c0707171651k27b5613k833fc632fa1b2221@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1784 bytes --]

On 23:51 Tue 17 Jul, Thufir wrote:
>  Oh.  Why was the grub documentation not understandable like that?
>  maybe I misread it.  thanks for explaining!

I guess you missed it. `info grub' says (*Note chainloading)

---8<---8<----

4.1.2 Load another boot loader to boot unsupported operating systems
--------------------------------------------------------------------

If you want to boot an unsupported operating system (e.g. Windows 95),
chain-load a boot loader for the operating system. Normally, the boot
loader is embedded in the "boot sector" of the partition on which the
operating system is installed.

  1. Set GRUB's root device to the partition by the command
     `rootnoverify' (*note rootnoverify::):

          grub> rootnoverify (hd0,0)

  2. Set the "active" flag in the partition using the command
     `makeactive'(1) (*note Chain-loading-Footnote-1::) (*note
     makeactive::):

          grub> makeactive

  3. Load the boot loader with the command `chainloader' (*note
     chainloader::):

          grub> chainloader +1

     `+1' indicates that GRUB should read one sector from the start of
     the partition. The complete description about this syntax can be
     found in *Note Block list syntax::.

  4. Run the command `boot' (*note boot::).

   However, DOS and Windows have some deficiencies, so you might have to
use more complicated instructions. *Note DOS/Windows::, for more
information.

---8<---8<----

Note that it's usually better to refer to the info command for more
serious documentation about GNU tools in general. RMS and his guys don't 
exactly seem to like manpages that much that's what they have info for. 
They have their point, but that's another flame war ;-)


Regards,
	Aleks

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-07-18 18:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 22:50 [gentoo-user] grub chainloader Thufir
2007-07-17 23:12 ` [gentoo-user] " »Q«
2007-07-17 23:51   ` Thufir
2007-07-18 12:18     ` Alan McKinnon
2007-07-18 12:35       ` Etaoin Shrdlu
2007-07-18 14:20         ` Stroller
2007-07-18 15:00           ` Alan McKinnon
2007-07-18 16:06             ` Stroller
2007-07-18 17:32               ` Neil Bothwick
2007-07-19  7:44               ` Alan McKinnon
2007-07-19  0:31             ` Iain Buchanan
2007-07-18 13:30     ` Александър Л. Димитров [this message]
2007-07-18 19:35       ` Thufir
2007-07-19  0:25       ` Iain Buchanan
2007-07-19  0:51         ` Thufir
2007-07-19 11:36         ` Hans-Werner Hilse
2007-07-19 14:02           ` Iain Buchanan
2007-07-18  0:02   ` Iain Buchanan
2007-07-18  6:53     ` Mick
2007-07-18 15:36       ` Neil Bothwick
  -- strict thread matches above, loose matches on Subject: below --
2007-07-19  7:14 burlingk
2007-07-19  6:25 ` Boyd Stephen Smith Jr.

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=20070718133043.GA6012@brmbr.sfs.uni-tuebingen.de \
    --to=aleks_d@gmx.de \
    --cc=gentoo-user@lists.gentoo.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