From: "Georgina Joyce" <gena-j@bulldoghome.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: best boot loader to use
Date: Mon, 2 Apr 2007 23:43:08 +0100 [thread overview]
Message-ID: <000401c77578$4d10a410$0302a8c0@forestfern> (raw)
In-Reply-To: <Pine.LNX.4.64.0703311202400.3693@CHIHUAHUAD1.gateway.2wire.net>
Hi
Well if you can boot into debian, how can you say your boot loader isn't working? Could it not be that you've made an error in the FC entry? Your kernel name is different to that of mine as you can see from the file I sent some time ago.
For some reason, I couldn't get the format you have used to work. So you might want to put the (hd0,2) on the kernel line and initrd lines. As in my example.
Providing you don't touch the debian lines, you will be alright and you'll get into your FC installation.
I've mainly used lilo and only recently moved to grub and I can tell you that they both do the same job but are quite different in their approaches. If you want a steeper learning curve switch over to lilo when you've got FC booting.
BTW:
Did you check that those tab spaces have not caused the line to wrap as in your post to me?
Regards
Gena
Amateur Call: M 0 E B P
VOIP / IM: gena1959uk
Tel 01772 380039 Mobile: 07876 502276
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Nick Gawronski
Sent: Saturday, March 31, 2007 6:15 PM
To: speakup@braille.uwo.ca
Subject: best boot loader to use
Hi, I was wondering what is the best boot loader to use grub or lilo? I
have grub installed on my debian system but debian also has a package
lilo that I can install. I am trying to get both debian and fedora core 6
bootable and when I try adding the proper lines to my menu.lst file and
hit the down errow and then enter nothing happens. This makes me believe
that the boot loader is not working properly or I did not write the file
properly. Here is what I have currently in my menu.lst file, I have
debian installed on /dev/hda1 and fedora core 6 installed on /dev/hda3
Do you think I should stick with grub or switch to lilo?
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/hda1 ro quiet speakup_synth=dectlk
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.6.18-speakup-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-speakup-686 root=/dev/hda1 ro quiet speakup_synth=dectlk
initrd /boot/initrd.img-2.6.18-speakup-686
savedefault
title Debian GNU/Linux, kernel 2.6.18-speakup-686 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-speakup-686 root=/dev/hda1 ro quiet speakup_synth=dectlk single
initrd /boot/initrd.img-2.6.18-speakup-686
savedefault
### END DEBIAN AUTOMAGIC KERNELS LIST
title fedora core 6
root (hd0,2)
kernel /boot/vmlinuz-2.6.18-1.2849.fc6spkxen root=/dev/hda3 ro quiet speaku$
initrd /boot/initrd-2.6.18-1.2849.fc6spkxen.img
savedefault
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
__________ NOD32 2160 (20070331) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Nick Gawronski
[not found] ` <20070331182837.GA3267@cm.nu>
` Nick Gawronski
` Georgina Joyce [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='000401c77578$4d10a410$0302a8c0@forestfern' \
--to=gena-j@bulldoghome.com \
--cc=speakup@braille.uwo.ca \
/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).