In an attempt to move onto 2.4.17 from 2.4.7, I downloaded the 2.4.17 kernel
sources and all the patches, that I am aware of, from developerworks.

The kernel make seems to go OK, but the install phase gets the error below.
arch/s390/boot/Makefile is calling arch/s390/boot/install.sh with 5 arguements,
but install.sh is only expecting 4. It doesn't seem to know about Kerntypes.

I tweaked arch/s390/boot/Makefile and then everything works - or at least runs
to completion. I think everything is OK but I always feel a little uneasy when
things like this happen.

Anyone seen anything like this?

===============================================================
sh -x ./install.sh 2.4.17 image /usr/src/linux-2.4.17/System.map
/usr/src/linux-2.4.17/Kerntypes ""
+ '[' -x /root/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
+ '[' -f /usr/src/linux-2.4.17/Kerntypes/vmlinuz ']'
+ '[' -f /usr/src/linux-2.4.17/Kerntypes/System.map ']'
+ cat image
./install.sh: /usr/src/linux-2.4.17/Kerntypes/vmlinuz: Not a directory
+ cp /usr/src/linux-2.4.17/System.map /usr/src/linux-2.4.17/Kerntypes/System.map
cp: accessing `/usr/src/linux-2.4.17/Kerntypes/System.map': Not a directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.17/arch/s390/boot'
make: *** [install] Error 2
===============================================================



Steve Arden

[EMAIL PROTECTED]
IBM-Global Services @ Lucent
(630)979-7124

Reply via email to