Bug 11587 - lilocheck does not work
Summary: lilocheck does not work
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 6.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-05-22 21:04 UTC by Sean Utt
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-17 21:38:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
diff for RedHat/instimage/usr/lib/anaconda/kickstart.py to fix the lilocheck option (488 bytes, patch)
2000-06-08 00:39 UTC, Sean Utt
no flags Details | Diff

Description Sean Utt 2000-05-22 21:04:56 UTC

First off, it would be nice if there was a way to dump the errors from an
install to a floppy disk on failure. Writing down the error and carrying it
across the room to type it back in is a rather primitive method of doing

lilocheck is failing with the following error:

File: "/usr/lib/anaconda/kickstart.py", line 84, in doLiloCheck drives =
isys.hardDriveList ().keys() AttributeError: hardDriveList

I am going to guess that someone typo'd here, since this is what I see when
I cd to the anaconda dir on my updated (patched) cd directory and

grep -i harddrive * */* 2>/dev/null
fstab.py:       drives = isys.hardDriveDict().keys()
fstab.py:       return isys.hardDriveDict()
isys.py:def hardDriveDict():
kickstart.py:        drives = isys.hardDriveList ().keys()
kickstart.py:                "harddrive"        : None                  ,
raidstart-stub:drives = isys.hardDriveDict().keys()
todo.py:        d = isys.hardDriveDict()

All the other routines use sys.hardDriveDict().

I modified the kickstart.py to test this theory.

I changed drives = isys.hardDriveList ().keys() to
drives = isys.hardDriveDict().keys()

After making that change, the kickstart reboots the system without any
message as to why. I am guessing that is what it was supposed to do, but a
message of some kind, like: "LiloCheck: Lilo detected in boot sector,
probable existing install, kickstart aborting." would be helpful.

On a slightly more advanced note:

Is it possible for the kickstart to simply boot off the hard drive at that
point, instead of rebooting? The reason I am asking is that I have built
custom CD's that contain a ks.cfg in the initrd.img in the etc directory,
and the default in the syslinux.cfg is to boot the kickstart. If the
lilocheck routine could switch the boot to the hard drive, the CD could be
left in the drive after the install without having to switch the boot
device, and the installed rpm's could be verified against the files on the

Sean Utt

Comment 1 Sean Utt 2000-06-08 00:39:26 UTC
Created attachment 338 [details]
diff for RedHat/instimage/usr/lib/anaconda/kickstart.py to fix the lilocheck option

Comment 2 Michael Fulbright 2000-06-16 15:28:13 UTC
We're hoping to have time to add a facility to write the traceback to a

I will look into your other issues.

Comment 3 Michael Fulbright 2000-06-22 18:10:43 UTC
Could you attach the kickstart file which caused the problem, as well as
a description of how to reproduce it?

Comment 4 Michael Fulbright 2000-08-17 21:38:11 UTC
Please reopen this report if you continue to have problems.

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