Bug 26379

Summary: "lilo -R 'rLwc?:2630-std-def-15'" has no effect
Product: Branch 5.1 Reporter: Ivan Zakharyaschev <imz>
Component: liloAssignee: Dmitry V. Levin <ldv>
Status: NEW --- QA Contact: QA 5.1 <qa-5.1>
Severity: critical    
Priority: P3    
Version: unspecified   
Hardware: all   
OS: Linux   
Attachments:
Description Flags
/etc/lilo.conf none

Description Ivan Zakharyaschev 2011-09-26 23:39:04 MSK 
Created attachment 5124 [details]
/etc/lilo.conf

lilo-22.7.3-alt6.M51.1

"lilo -R" is an important feature for testing new kernels on systems where you can't intercatively control the booting process. But in my case, I wasn't able to use it. I issued the command "lilo -R 'rLwc?:2630-std-def-15'", but after a reboot the kernel that was booted was still the default one, not the chosen one.

My /etc/lilo.conf is attached. The specified label does exist indeed:


[root@localhost ~]# strace -e trace=file -fF lilo -R 'rLwc?:2630-std-def-15'
execve("/sbin/lilo", ["lilo", "-R", "rLwc?:2630-std-def-15"], [/* 41 vars */]) = 0
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
open("/lib/libdevmapper.so.1.00", O_RDONLY) = 3
open("/lib/libblkid.so.1", O_RDONLY)    = 3
open("/lib/libc.so.6", O_RDONLY)        = 3
open("/lib/libuuid.so.1", O_RDONLY)     = 3
open("/etc/lilo.conf", O_RDONLY)        = 3
stat64("/dev/.devfsd", 0xbfd939a4)      = -1 ENOENT (No such file or directory)
open("/boot/map", O_RDWR)               = 4
Process 16936 detached
[root@localhost ~]# fgrep -2 'rLwc?:2630-std-def-15' /etc/lilo.conf
image="/boot/vmlinuz-2.6.30-std-def-alt15"
	initrd="/boot/initrd-2.6.30-std-def-alt15.img"
	label="rLwc?:2630-std-def-15"
	root="UUID=88f85e96-c860-4402-90a3-ede10bae1661"
	read-only
[root@localhost ~]#
Comment 1 Ivan Zakharyaschev 2011-09-27 00:44:40 MSK 
However, for another simpler label, it worked: "lilo -R ALTLinux".
Comment 2 Ivan Zakharyaschev 2011-09-27 04:09:50 MSK 
So, the workaround for this problem is to create a menu entry in /etc/lilo.conf with a simpler label. As I did:

image="/boot/vmlinuz-record"
	label="record"
	initrd="/boot/initrd-record.img"
	root="UUID=88f85e96-c860-4402-90a3-ede10bae1661"
	read-only

The specified files are symlinks to the kernel being tested. "lilo -R record" does work.
Comment 3 Ivan Zakharyaschev 2011-09-27 04:12:38 MSK 
Perhaps, the problem is with the length of the label (similarly to https://bugzilla.altlinux.org/show_bug.cgi?id=22616 ), or perhaps the problem is with the special symbols like "?"...