SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Generally it should be no problem as you can choose the partition slackware will be installed on. However it is recommended that you use a primary partition for it.
Post some more information on your partitioning table when you want more help.
Originally posted by dufferin Any LILO lovers out there?
I use a 120GIG split in 12 and a 15GIG whole.
Right now I use OSL2000 to select which OS at bootup.
Before I install LILO, I wanna make sure I can put
things back to the way they were if need be.
Is LILO better and will it effect windoze?
Will all partitions be displayed on the menu?
Will it install on hda15 or hda1?
Is it easy to get off, or must you format?
Here's what I got:
WindozeXP on hda1
Others on hda5-14
Slackware 9.1 on hda15
WindozeME on hdb1
Will this work.
Thanks,
John.
Yes, you can uninstall LILO easy enough. /sbin/lilo -u will uninstall it. You can choose to install lilo either in the master boot record, or on the boot record of the linux partition. In your case, you will need to install it on the linux partition. I've never used OSL2000, but I imagine it can be used simultaneously with LILO. LILO cannot be used to boot NT/2K/XP. I use the standard boot loader that comes with 2K and have lilo installed on /dev/hda6 (first extended partition). With OSL2000 you may need to use the same tricks I do as described here: http://classes.csumb.edu/CST/CST434-.../DualBoot.html
Good luck.
P.S. If you already have WinXP, ME, and "Others" installed, it's always a good idea to create a recent backup before mucking with partitions.
Originally posted by azar92 Yes, you can uninstall LILO easy enough. /sbin/lilo -u will uninstall it. You can choose to install lilo either in the master boot record, or on the boot record of the linux partition. In your case, you will need to install it on the linux partition. I've never used OSL2000, but I imagine it can be used simultaneously with LILO. LILO cannot be used to boot NT/2K/XP. I use the standard boot loader that comes with 2K and have lilo installed on /dev/hda6 (first extended partition). With OSL2000 you may need to use the same tricks I do as described here: http://classes.csumb.edu/CST/CST434-.../DualBoot.html
Good luck.
P.S. If you already have WinXP, ME, and "Others" installed, it's always a good idea to create a recent backup before mucking with partitions.
Lilo cannot be used to boot NT/2K/XP ??
strange, because i used it to dual boot between slackware and WindowsXP. I had no problems with it at all. the winxp was on a ntfs partition.
Originally posted by deNiro Lilo cannot be used to boot NT/2K/XP ??
strange, because i used it to dual boot between slackware and WindowsXP. I had no problems with it at all. the winxp was on a ntfs partition.
This was my understanding. I was under the impression that XP had the same problems that NT/2K did. They liked to have their own bootloader on the Master Boot Record (MBR), though LILO could reside on the boot record of the linux partition. Perhaps this is changed with XP, or perhaps I've been lied to for the past 2-3 years.
Originally posted by azar92 This was my understanding. I was under the impression that XP had the same problems that NT/2K did. They liked to have their own bootloader on the Master Boot Record (MBR), though LILO could reside on the boot record of the linux partition. Perhaps this is changed with XP, or perhaps I've been lied to for the past 2-3 years.
hehe, lied is a strong word. but you have to add it manually (or in expert lilo config mode) or indeed it wont work. At my machine it doesn't recognize it automatically. But when i used expert mode, it just worked fine
Originally posted by KMcD I've always used LILO to dual boot between slack and Win2K and now WinXP. Was never a problem. Just install it on the MBR while installing slack.
consider yourself lucky. I've been struggling for month with LILO on a floppy because I couldn't get it loading Windows. But in the KDE Systemadministration there is a lilo configuration tool that helped me creating a working LILO version. It's probably just a front end but I didn't find the correct settings before.
Problem is what I want to appear in the menu does not.
I don't see WindowsME or Slackware 9.1, how come?
This should apper in menu:
Linux
WindowsME
WindowsXP (default)
An image directive is associated with the PATH to a kernel image - not the device name of a partition that a non-Linux OS resides on - you need to use :
other = /dev/hda1
table = /dev/hda
label = "WindowsXP"
So here's my lilo.conf. I'll use <-- to indicate what a line does.
Now I may not be 100% correct on all the details.
Code:
# Start LILO global section
append="hdc=ide-scsi hdd=ide-scsi" <-- stuff the kernel needs to know about my CD drives.
boot = /dev/hda <-- Where to put the bootloader (MBR here)(1)
message = /boot/boot_message.txt
prompt <-- Tells LILO to give you a menu
timeout = 1200 <-- How long to wait before loading default OS
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda1 <-- My WindowsXP install
label = DOS
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz <-- My VectorLinux Kernal image (2)
root = /dev/hda7 <-- Location of root partition
label = Linux
read-only
# Linux bootable partition config ends
Notes:
(1) - I've never actually put LILO anywhere else. Also of note, when you install LILO, it makes a backup of the existing MBR. man lilo will tell you the filename. Keep this for rescue purposes.
(2) - The image path is relative to your current root when you actually run the lilo command. If you want to reference a diffent linux install, you need to mount the partition that contains /boot for that install, then make a reference to that kernel image in your lilo.conf
Hope this helps. It's also good to have a live CD or something for rescue purposes.
dufferin - After you edit the lilo.conf file, you need to run the lilo program: /sbin/lilo That will apply any updates you've made. -- J.W.
Also, I've always installed lilo to the MBR too, and I've never had any trouble whatsoever with dual booting between Slack and XP on any of my machines. Just to be sure to install Windows first, then Linux. If you do it the other way around, Windows will overwrite the MBR, effectively killing your Linux install.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.