public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: grub chainloader
Date: Wed, 18 Jul 2007 09:32:52 +0930	[thread overview]
Message-ID: <1184716972.7158.18.camel@orpheus> (raw)
In-Reply-To: <30vvm4-331.ln1@goldry.remarqs.net>

On Tue, 2007-07-17 at 18:12 -0500, »Q« wrote:
> In <news:bf6b6d5c0707171550sa74b587v3652ac2f00d3be8e@mail.gmail.com>,
> Thufir <hawat.thufir@gmail.com> wrote:
> 
> >I've read the GRUB documentation, but still don't understand why the
> >following worked:
> 
> [snip grub.conf]
> 
> >I would've thought that the chainloader +1 statement would be required
> >-- that's my experience at least.
> 
> It's only needed if you're booting an unsupported (by grub) OS;

no only unsupported OSs, you can chainload anything (bootable) such as
another linux distro, which has installed a bootloader into the
partition.  See how this guy booted 30+ OS's from grub:
http://www.justlinux.com/forum/showthread.php?threadid=134856

>   it
> tells grub to just hand off to another bootloader.  The +1 tells grub
> to load the first sector of the OS's partition, which is where the
> other bootloader should be embedded.
> 
> As long as you're booting Linux kernels, you can just point grub at
> them without using another bootloader.

you mean as long as grub understands the kernel and filesystem, you can
tell grub to load the kernel directly, with provided arguments.

I think :)

cya,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Kevin:  Dad, the fish got away. 
Joe Swanson:  The hell it did. You get in there and you kick that fish's ass.

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-07-18  0:11 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     ` Александър Л. Димитров
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 [this message]
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=1184716972.7158.18.camel@orpheus \
    --to=iaindb@netspace.net.au \
    --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