Bug 11528 – lilo allows spaces during config of lilo name entry

This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 11528 - lilo allows spaces during config of lilo name entry

Summary:	lilo allows spaces during config of lilo name entry

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	lilo (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-05-19 14:39 EDT by Ric Moore
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-06-06 09:50:41 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ric Moore 2000-05-19 14:39:31 EDT

During the last part of installation when lilo is set up, and the user is
queried as to what he wants to name the lilo setup, instead of it being the
default word 'linux', they could enter 'linux ric' with a space between the
two words and when booting have lilo barf finding the space. We're seeing
quite a few tickets where the user says it completely installs then refuses
to boot. They'd forget what they named it, while it bombs and we're
supposed to guess what they did because it allowed them to. Ric

Comment 1 rolf_vom_stein 2000-06-06 09:50:41 EDT

During the installation the return code of lilo isn't checked correctly!
If you run  lilo with a blank with a configuration like below: i.e.: 
default = Red Hat
...
   label=Red Hat

Lilo returns: Syntax Error near line XXX

During the installation this error is not handled, thus the 
routine pretends a successful installtion.

Comment 2 Jeremy Katz 2002-04-12 01:43:46 EDT

fixed in current releases

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