public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] booting to grub prompt, but config works
Date: Fri, 9 May 2008 14:51:37 -0700	[thread overview]
Message-ID: <5bdc1c8b0805091451ud1e4c6bm92ba1e30b095f174@mail.gmail.com> (raw)
In-Reply-To: <20080509224116.719eda25@loonquawl.digimed.co.uk>

On Fri, May 9, 2008 at 2:41 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Fri, 9 May 2008 21:50:09 +0200, Alex Schuster wrote:
>
>> Check for /boot/grub/menu.lst, this is an alternate (and maybe empty)
>> config file which grub seems to prefer over grub.conf.
>
> menu.lst has been the preferred config file for some years, it seem that
> GRUB is a little more strict about this nowadays.
>

I tried to read the ebuild but failed.

In my case I am sure that I was out of order WRT the way the quick
install guide says to build the system - first emerge grub, make
grub.conf, and then install grub. I was thinking I'd get the grub.conf
file from another system so I didn't bother doing it. After this
happened - and thanks for your help finding the solution - I started
wondering if the grub install or even the emerge of grub creates the
link when grub.conf is there but if it isn't there then there's
nothing to link to so we end up like my system last evening.

Anyway, just my guess since I know for a fact I didn't have a
grub.conf file when I did the emerge.

- Mark
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-05-09 21:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 19:32 [gentoo-user] booting to grub prompt, but config works Travis Osterman
2008-05-09 19:50 ` Alex Schuster
2008-05-09 21:41   ` Neil Bothwick
2008-05-09 21:51     ` Mark Knecht [this message]
2008-05-10  8:55       ` Alan McKinnon
2008-05-10 17:29         ` Mark Knecht
2008-05-10 18:57           ` Alan McKinnon
2008-05-09 19:52 ` Mark Knecht

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=5bdc1c8b0805091451ud1e4c6bm92ba1e30b095f174@mail.gmail.com \
    --to=markknecht@gmail.com \
    --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