From: Nick Garnett <nickg@ecoscentric.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: raghavendra pai g <grpai1@rediffmail.com>,
ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: eCos Grub Problem
Date: Tue, 09 Aug 2005 14:57:00 -0000 [thread overview]
Message-ID: <m38xzb88eq.fsf@xl5.calivar.com> (raw)
In-Reply-To: <1123598203.13258.2.camel@icampbell-debian>
Ian Campbell <ijc@hellion.org.uk> writes:
> On Tue, 2005-08-09 at 15:24 +0100, Nick Garnett wrote:
>
> > My understanding of GRUB is that it uses a menu.lst file in /boot/grub
> > to supply the boot options. That is certainly what my SuSE
> > installation does. I'm not sure what role /etc/grub.conf plays, but it
> > is not the right place to put new boot options.
>
> On all the systems I've seen which use grub (primarily Debian systems)
> menu.lst is a symlink to grub.conf. I don't know for sure which one grub
> actually looks for (the manpage suggests menu.lst) but if you modify the
> other one and they aren't linked you'll run into trouble...
Here, on SuSE 9.1, they are definitely different files. The contents
of /etc/grub.conf seems designed for host tools to locate the
bootloader.
Of course SuSE may be doing their own thing here.
/etc/grub.conf:
root (hd0,1)
install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8000 (hd0,1)/grub/menu.lst
quit
/boot/grub/menu.lst:
# Modified by YaST2. Last modification on Fri May 28 15:56:01 2004
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,1)/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title Linux
kernel (hd0,1)/vmlinuz root=/dev/hda1 vga=0x31a splash=silent desktop resume=/dev/hda6 showopts
initrd (hd0,1)/initrd
###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
root (fd0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe
kernel (hd0,1)/vmlinuz root=/dev/hda1 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3
initrd (hd0,1)/initrd
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-08-09 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050809102804.17214.qmail@webmail28.rediffmail.com>
2005-08-09 14:24 ` Nick Garnett
2005-08-09 14:37 ` Ian Campbell
2005-08-09 14:57 ` Nick Garnett [this message]
2005-08-09 14:38 ` R Vamshi Krishna
2005-08-09 15:21 ` Nick Garnett
2005-08-09 18:47 ` David Brennan
[not found] <20050809091416.27715.qmail@webmail29.rediffmail.com>
2005-08-09 9:35 ` Nick Garnett
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=m38xzb88eq.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=grpai1@rediffmail.com \
--cc=ijc@hellion.org.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).