Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok - I was mistaken with those files, but I did find the following:
lilo.raid.conf
#
# lilo.raid.conf
#
#
# A RAID installation is called for. With (version 22) of LILO
# the boot record will be installed on the RAID partition. The
# Master Boot Record will find the record on (hda2), which is marked
# as an active partition. (sdb1) is also marked active. If (hda) fails,
# it will be possible to boot by disabling the IDE controller in BIOS,
# which will cause (sdb) to become device 0x80, and boot appropriately.
boot = /dev/md1
#
# Auxiliary boot records will be installed automatically. Since
# this is a PARALLEL raid device, there will be no boot records
# other that the one written to the RAID set (sdb1, hda2).
raid-extra-boot = auto
#
# The SCSI controller BIOS assigns device codes backwards
# from what one might expect, so we make the BIOS device
# code assignment by the BIOS explict:
#
# This system also will run DOS, but we have
# to fake DOS into thinking it is booting from
# drive C:
other=/dev/sdb2
label=dosB2
map-drive = 0x80 to = 0x81
map-drive = 0x81 to = 0x82
map-drive = 0x82 to = 0x80
#
# We can boot OS/2 from a secondary partition. The 'table='
# specification tells OS/2 that the secondary (boot) parition
# mounts as drive E:. Versions of LILO prior to version 22 will
# require a special boot loader, but as of version 22, all
# chain loader functions have been combined into the default
# chain loader, '/boot/chain.b'.
Niall, first make copies of files
Secondly,
#################################################
# end of sample-lilo.conf Global section #
#################################################
#
# The first image is the default image
other=/dev/hda1
label=win_2k
table=/dev/hda
I took the easy road and used Yast. But thank you nautilus for the long version too.
BTW - the reason for so many OS's is simply that I do a lot of forensics work and this machine is my test machine. I'm new to LInux, and rapidly learning it's inner workings, but sometimes it's the little things that get me stumped.
In the LILO case, I was simply trying to find a way to NOT have to monitor the boot process every time. More of a laziness thing.
Thanks again, this is, as always, a great resource.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.