know of another dual boot program rather than grub
Nigel Henry
cave.dnb2m97pp at aliceadsl.fr
Thu Feb 19 21:45:17 UTC 2009
On Thursday 19 February 2009 18:59, John Culleton wrote:
> On Thursday 12 February 2009 11:43:05 pm Ray Burke wrote:
> > does any one know of another dual boot program rather
> > than grub to boot both win xp pro and Kubuntu, as Grub
> > does not allow my bkup hdd's mointed in removable hdd
> > racks like when in xp pro but now using grub as dual boot
> > fails with error 17, so need another program for this
> > dual boot
> >
> > ray
> Well hter is always Lilo. When I run it from Slack I can't
> get it to boot Kubuntu so I am stuck with grub. But maybe
> there is some magic incantation I am missing. Does anyone
> on list boot Debian/Kubuntu form Lilo? If so what does the
> lilo.conf look like?
>
>
> --
> John Culleton
> Able Indexers and Typesetters
> http://wexfordpress.com
Ok. Here goes. My LiLo was originally installed from Debian Woody 3.0r2
cdroms, and is currently working ok on Debian Sarge, Etch, and Lenny, which
were all upgraded from Woody. The lilo.conf below is for Lenny, and is not
accessed directly when booting up. When booting up I get Grub, and Lenny's
LiLo is accessable via a chainloader in Grub. All the entries in Lenny's LiLo
are just for different Lenny kernels. Anyway. See below.
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda7
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda7
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
#install=/boot/boot-menu.b
#new install parameter below
install=menu
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
# prompt
# single-key
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
# Boot up Linux by default.
#
#default=Linux
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
image=/boot/vmlinuz-2.6.8-2-386
label=Linux2.6.8
initrd=/boot/initrd.img-2.6.8-2-386
read-only
image=/boot/vmlinuz-2.6.11-1-386
label=Linux2.6.11
initrd=/boot/initrd.img-2.6.11-1-386
read-only
image=/boot/vmlinuz-2.6.17-2-686
label=Linux2.6.17
initrd=/boot/initrd.img-2.6.17-2-686
read-only
image=/boot/vmlinuz-2.6.21-2-686
label=Linux2.6.21
initrd=/boot/initrd.img-2.6.21-2-686
read-only
image=/boot/vmlinuz-2.6.21-rt4
label=Linux2.6.21rt4
initrd=/boot/initrd.img-2.6.21-rt4
read-only
image=/boot/vmlinuz-2.6.21.5-rt18
label=Linux2.6.21rt18
initrd=/boot/initrd.img-2.6.21.5-rt18
read-only
image=/boot/vmlinuz-2.6.26-1-686
label=Linux2.6.26-1
initrd=/boot/initrd.img-2.6.26-1-686
read-only
I see that my Sarge is booting directly to LiLo, and as there are multiple
installs on the harddrive, there are chainloader entries in lilo.conf, which
may be what you're looking for. See below.
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda1
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
# prompt
# single-key
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
# Boot up Linux by default.
#
default=Linux
image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
other=/dev/hda7
label=Fedora8
other=/dev/hda9
label=Archlinux
image=/boot/vmlinuz-2.4.27-2-386
label=Linuxalsa2.4
initrd=/boot/initrd.img-2.4.27-2-386
read-only
image=/boot/vmlinuz-2.6.8-2-386
label=Linux-2.6.8
initrd=/boot/initrd.img-2.6.8-2-386
read-only
The chainloader entries above, are the "other" ones for Fedora8, and
Archlinux.
The only problem I've found with LiLo recently, is that you have to be
carefull as to how many characters you have for the label. If you have too
many, when running /sbin/lilo, it will not add the new entry to lilo.conf.
I've learned to keep the labels as short as possible.
I don't know if any of this helps you, but only you know.
All the best.
Nigel.
More information about the kubuntu-users
mailing list