I would guess that the vmlinuz-2.4.9-17 is intended for use under VM, and so supports the multiple 80-byte parmfile records, while the vmlinuz-2.4.9-17tape kernel uses the 1 long record parmfile layout. I would say you should be using the vmlinuz-2.4.9-17tape kernel, since you're running out of an LPAR.
Mark Post -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 9:40 AM To: [EMAIL PROTECTED] Subject: kernel image question RH7.2 (2.4.9-17tape) in an LPAR I have an /etc/zilo.conf (I thought this file was no longer used?) and an /etc/zipl.conf. using loader, my /etc/zipl.conf is written as: [defaultboot] default=linux [linux] target=/boot/ image=/boot/vmlinuz-2.4.9-17tape parameters="root=/dev/dasda1 dasd=6B40-6B43,6BC0-6BC3" [linux-up] target=/boot/ image=/boot/vmlinuz-2.4.9-17 parameters="root=/dev/dasda1 dasd=6B40-6B43,6BC0-6BC3" When I activate the LPAR in the HMC, linux is booting from dasd. How do these images differ? Should I be using /boot/vmlinuz-2.4.9-17 here instead of vmlinuz-2.4.9-17tape? ~ Daniel
