From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] booting to grub prompt, but config works
Date: Sat, 10 May 2008 10:29:00 -0700 [thread overview]
Message-ID: <5bdc1c8b0805101029l3d86287cr59b1799ea5496970@mail.gmail.com> (raw)
In-Reply-To: <200805101055.44286.alan.mckinnon@gmail.com>
On Sat, May 10, 2008 at 1:55 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
<SNIP>
> # change menu.lst to grub.conf
> if [[ ! -e ${dir}/grub.conf ]] && [[ -e ${dir}/menu.lst ]] ;
> then
> mv -f "${dir}"/menu.lst "${dir}"/grub.conf
> ewarn
> ewarn "*** IMPORTANT NOTE: menu.lst has been renamed to
> grub.conf"
> ewarn
> fi
>
>
> it's called essentially this way in post_inst():
>
> setup_boot_dir /boot
>
> what it does is in essence:
>
> 1. fail if /boot does not exist
> 2. create /boot/boot as a link to /boot
> 3. create /boot/grub
> 4. if you don't have a grub.conf and do have a menu.lst then rename it
> to grub.conf
>
>
>
> --
> Alan McKinnon
Yeah, it was that last bit that I wondered about. So, assuming you do
have a grub.conf what happens? Does nothing in the ebuild ever make
the menu.lst->grub.conf link? Did older ebuilds make this link? I have
no recollection of making one by hand.
The GNU grub manual I found online talks only about menu.lst. Is
having a grub.conf file a Gentoo thing? I've run *almost* nothing but
Gentoo for 8 years now so I have no real knowledge of how other
distros set this up.
- Mark
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-05-10 17:29 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
2008-05-10 8:55 ` Alan McKinnon
2008-05-10 17:29 ` Mark Knecht [this message]
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=5bdc1c8b0805101029l3d86287cr59b1799ea5496970@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