All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Menu.lst doesn't get updated with grub 1.95+20071101-1 release
Date: Tue, 29 Jan 2008 14:43:15 +0100	[thread overview]
Message-ID: <20080129134315.GD27435@thorin> (raw)
In-Reply-To: <511f47f50801290358o5e94d94cpd548ecf737447ef9@mail.gmail.com>

On Tue, Jan 29, 2008 at 05:28:45PM +0530, shirish wrote:
> Hi all,
> This might be no longer the matter at head but since I've the issue
> hence posting the same. Might be a repost in which I'm sorry.
> 
>  I'm running grub 1.95+20071101-1 release on Hardy.
> 
> This is the pastebin of menu.lst http://pastebin.ca/877007
> 
> while this is the pastebin of grub.cfg http://pastebin.ca/877010
> 
> when I do sudo update-grub I get this :-
> 
> shirish@Mugglewille:~$ sudo update-grub
> [sudo] password for shirish:
> Updating /boot/grub/grub.cfg ...
> Found linux image: /boot/vmlinuz-2.6.24-5-generic
> Found initrd image: /boot/initrd.img-2.6.24-5-generic
> Found linux image: /boot/vmlinuz-2.6.24-4-generic
> Found initrd image: /boot/initrd.img-2.6.24-4-generic
> Found linux image: /boot/vmlinuz-2.6.24-2-generic
> Found initrd image: /boot/initrd.img-2.6.24-2-generic
> Found memtest86+ image: /boot/memtest86+.bin
> done
> 
> Now this doesn't effect menu.lst & unfortunately grub2 doesn't work
> (the menu doesn't work something to do with unifont.pff). So each time
> I've to manually add entries to /boot/grub/menu.lst to tell where the
> new kernels are.
> 
> Any ideas, suggestions other than installing grub 0.97 ?

GRUB 2 uses grub.cfg, not menu.lst.

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)



      reply	other threads:[~2008-01-29 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 11:58 Menu.lst doesn't get updated with grub 1.95+20071101-1 release shirish
2008-01-29 13:43 ` Robert Millan [this message]

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=20080129134315.GD27435@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.