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 am stuck between a rock and a hard place here. I want lilo to have two boot options; one Linux and one Winblows. I thought i was doing this right when i edited my lilo.conf... apparently not because i don't see a Winblows option in lilo upon bootup. At the bottom of the lilo.conf i added the "# DOS..." here is my conf file... Can someone tell me what it is i am doing wrong here
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="hdc=ide-scsi"
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 800x600x256
vga = 771
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
label = Winblows
table = /dev/hda/
# DOS bootable partition config ends
Distribution: Lots of distros in the past, now Linux Mint
Posts: 748
Rep:
other=/dev/hda1
label="windows"
table=/dev/hda
This is one of mine w/windows2000, and it looks the same. The only real differences are the tabs, quotes and spaces, but that shouldn't make much difference, I think. Still, maybe it'll give you some insights.
Edit: The label and table lines are indented, but LQ isn't showing them when I post.
What do you mean "Do u run lilo everytime u do changes in lilo.conf?" ? Do you mean do i reboot everytime i change the lilo.conf. If that is what you are asking then yes, i reboot everytime i change lilo.conf and i still only have one option...Linux. Nothing really wrong with that, but i do need access to Winblows sometimes... Bummer!
Everytime u do changes in lilo.conf u have to execute command 'lilo'. At this point the Lilo saves changes to MBR. Only writing changes in lilo.conf withotu executing lilo dont change anything.
After running 'lilo' u should get some message, something like
*Linux Added
*Windows Added
'lilo' command is this file - /sbin/lilo check if u have it there, i suppose u try to run it as root. U said u got nothing when u executed this command, not even an error message?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.