Bug 59100 - Installer fails to run lilo succesfully
Summary: Installer fails to run lilo succesfully
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer   
(Show other bugs)
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-01-30 23:28 UTC by Julian Gough
Modified: 2007-04-18 16:39 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-30 23:28:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Julian Gough 2002-01-30 23:28:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.17-0.12custom i686)

Description of problem:
During the install process,  for a dual boot system containing windows, if you
type a name with a space for windows,  then lilo.conf is misconfigured and lilo
does not run.  When you reboot it goes straight to windows ... no linux!!!  and
no lilo.
Probably behaves badly if you put a space in any label but I have not tested

This may seem like a trivial and unlikely problem, but nowhere does it say there
must be no spaces, and an inexperienced user could easily be stumped by this. 
There are no error messages,  and the result is fatal.

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

How reproducible:

Steps to Reproduce:
1.Install redhat 7.2 from cd onto a pre-partitioned disk already containing
2.type in a label for lilo for windows with a space in it
3.end installation

Actual Results:  Lilo not installed,  does not boot.

Expected Results:  An error message should be generated, or better still no
spaces should be allowed to be entered as lilo labels during install.  It should
not allow exiting the installer without succesfully running lilo.

Additional info:

Comment 1 Jeremy Katz 2002-02-01 06:14:19 UTC
This is already fixed for future releases

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