Bug 7118

Summary:	mem= n...[K \| M] not recognized in lilo.conf or lilo boot prompt
Product:	[Retired] Red Hat Linux	Reporter:	ldunaway
Component:	kernel	Assignee:	Michael K. Johnson <johnsonm>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-01-04 22:27:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ldunaway 1999-11-18 21:37:21 UTC

When I added append="mem=130495K" (which worked in my 6.0) to lilo.conf; it
was ignored.

I tried it on the lilo boot prompt and got "invalid number"

What's up??????????????

ps: 128M fails the same way

Comment 1 Cristian Gafton 2000-01-04 22:27:59 UTC

Assigned to dledford

Comment 2 openshift-github-bot 2016-09-29 13:52:23 UTC

Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/86e6dc1475254c44a1a78d9292e00a0f7842733e
Add details for field.Required

Some fields are only required if other fields have certain values.
This patch adds some additional error messaging to inform the user
why these fields were necessary.

Fixes issue #7118

Signed-off-by: Stephen Gallagher <sgallagh>