Bug 115046 - lilo not reading lilo.conf
Summary: lilo not reading lilo.conf
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: lilo
Version: 9
Hardware: i686
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-05 21:06 UTC by Jody Branter
Modified: 2007-04-18 17:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-05 22:49:57 UTC
Embargoed:


Attachments (Terms of Use)

Description Jody Branter 2004-02-05 21:06:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Description of problem:
I'm trying to change the default os that lilo boots to from Linux to
WindowsXP.  Seems simple enough right?  Edit the 'default=' line in
the lilo.conf file to say 'default=WindowsXP'.  here is my lilo.conf:

prompt
timeout=100
default=WindowsXP
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/xray-blue.boot
linear

image=/boot/vmlinuz-2.4.20-8smp
	label=Linux
	initrd=/boot/initrd-2.4.20-8smp.img
	read-only
	append="root=LABEL=/"

image=/boot/vmlinuz-2.4.20-8
	label=Linux-up
	initrd=/boot/initrd-2.4.20-8.img
	read-only
	append="root=LABEL=/"

other=/dev/hda1
	optional
	label=WindowsXP

Why then does it still boot to Linux?  I've tried moving the Windows
entry to the top of the list like you used to have to do, but it
doesn't help.  The system always boots to Linux by default.  Windows
does boot, but only when you select it before the time runs out.  This
has me stumped.  Could lilo be reading from something other than
lilo.conf?  Is there something missing in the file?

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.reboot the damn computer
2.
3.
    

Additional info:

Comment 1 Jeremy Katz 2004-02-05 22:49:57 UTC
You have to rerun /sbin/lilo after changing lilo.conf.


Note You need to log in before you can comment on or make changes to this bug.