public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Erik Grinaker <erikg@wired-networks.net>
To: gentoo-dev@gentoo.org
Subject: RE: [gentoo-dev] Point of fact.
Date: 08 Mar 2002 17:51:17 +0100	[thread overview]
Message-ID: <1015606277.2535.92.camel@maas.wired> (raw)
In-Reply-To: <23DFAA462CC6A64487613B0E242D9FF706EBB4@mercury.phoenix-interactive.com>

On Fri, 2002-03-08 at 16:55, Sean Mitchell wrote:

> Well, the rest of that whole post aside, many of us have had trouble with
> grub because we have no separate /boot partition. In my case, my /boot
> partition is on /dev/hde1, which grub just can't seem to find.
> 
> I like grub, but I've had much more success with lilo.

This is all explained in the grub documentation
(http://www.gnu.org/manual/grub-0.90/html_chapter/grub_toc.html). 

The biggest problem people have with GRUB is that they fail to realize
what root in the GRUB config means - it is not the system root, but the
root where the kernel images reside. In other words, your boot
partition.

Your config entry should be for exampe "root (hd0,0)", where hd0,0 is
your boot partition.

When you specify your kernel image you must do this relative to your
boot root, which usually should be /<your-kernel-image>. And then you
pass your *system root* as a boot argument, for example ;

kernel /bzkernel-2.4.18-2 root=/dev/hda5

Now, in order to avoid all this confusion (or perhaps add to it :)), you
can create a symlink from /boot/boot to /boot. This allows you to
specify /boot/<kernelimage> in your grub config. To do this, issue the
command "cd /boot && ln -s . boot".

now it will work to specify your kernel image as, for example ;

kernel /boot/bzkernel-2.4.18-2 root=/dev/hda5

GRUB is far superior to LILO in pretty much every conceivable way, as
long as you read the documentation and understand how it works. And when
you do so you will quickly see that LILO is a child's toy in comparison.


Feel free to add this to the docs...

-- 

Erik Grinaker
Freelance UNIX/Linux systems consultant

"Perfection is acheived not when there is nothing more to add, but
rather when there is nothing more to take away"
- Antoine de Saint-Exupéry




  parent reply	other threads:[~2002-03-08 16:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-08 15:55 [gentoo-dev] Point of fact Sean Mitchell
2002-03-08 16:30 ` Thilo Bangert
2002-03-08 16:51 ` Erik Grinaker [this message]
2002-03-08 16:55   ` Erik Grinaker
2002-03-08 17:16   ` Marc Soda
2002-03-08 17:21   ` Jon Nelson
2002-03-08 20:34   ` Martin Schlemmer
2002-03-09  9:39   ` Jim Nutt
2002-03-08 18:42 ` Arcady Genkin
  -- strict thread matches above, loose matches on Subject: below --
2002-03-08 18:23 Sean Mitchell
2002-03-08  1:42 Tom Newsom
2002-03-08 13:52 ` Karl Trygve Kalleberg
2002-03-08 15:48 ` Marc Soda

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=1015606277.2535.92.camel@maas.wired \
    --to=erikg@wired-networks.net \
    --cc=gentoo-dev@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