Bug 35823

Summary: LILO prompt "mem=" doesn't override lilo.conf "append="
Product: [Retired] Red Hat Linux Reporter: Bowe Strickland <bowe>
Component: kernelAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: low    
Version: 7.1CC: rrussell
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-04-12 18:49:46 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 Bowe Strickland 2001-04-12 18:49:42 UTC 
In seawolf, lilo.conf has 'append="mem=64M"', and I specified mem=96M at
the LILO 
prompt.  The kernel uses 64M instead.  I suspect the issue is in the
kernel's parsing of
command line arguments... it's taking the first instead of the last. 
Interestingly, you do 
not get similar behavior for "init=" kernel boottime parameter....

lilo.conf:
>> image=/boot/vmlinuz-2.4.2-2
>>	label=linux
>>	read-only
>>	root=/dev/hda5
>>	append="mem=64M"

lilo prompt:
LILO: linux mem=96M

cat /proc/cmdline:
BOOT_IMAGE=linux ro root=305 BOOT_FILE=/boot/vmlinuz-2.4.2-2 mem=64M
mem=96M

cat /proc/meminfo | head -4:
>>        total:    used:    free:  shared: buffers:  cached:
>> Mem:  64151552 31064064 33087488        0  2748416 16683008
>> Swap: 139788288        0 139788288
>> MemTotal:        62648 kB
Comment 1 Arjan van de Ven 2001-04-12 19:59:40 UTC 
The kernel parses both and takes the smallest to be safe...
Fix your lilo.conf ;)

You should not need any mem= line with our kernel now anyway.