On Fri, 8 Aug 2003, Hannes Reinecke wrote: > John Summerfield wrote: > > On Fri, 8 Aug 2003, Brigitte Warnecke-Schaer wrote: > > > > > >>Hello Sergey, > >> > >> > >>>1. I think, you did 'make modules' > >> > >>Was O.K. > >> > >> > >>>2. I think, you did 'make modules_install' > >> > >>Did we ... > >> > >> > >>>3. Copy the new kernel to /boot > >> > >>>cp arch/s390x/boot/image /boot/kernel-x.x.x ( e.g. kernel-2.4.21-3) > >> > >>O.K. > > > > > > > > I always thought the right way to do this is, as root, > > make install modules_install > Indeed. The above step should be equivalent to make install (dunno, > always copied it by hand :-), but a make modules_install should be done > nevertheless. > And, of course, a mkinitrd should be run afterwards, since some drivers > (e.g. dasd) are compiled as modules by default although they are > required at boot-time. > And as usual, do check where the above mentioned steps copies there > files into as to not overwrite your original installation :-)
"make install" calls a script /sbin/installkernel which puts the kernel in the right place as defined by your vendor, and which may also do the mkinitrd for you. On recent RHL it even updates (on IA32) grub or lilo. Check installkernel on your system to see what it does. I've never heard of anyone stuffing things up by (correctly) using the makefile supplied, but quite a few have by _not_ using the makefile. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb Copyright John Summerfield. Reproduction prohibited.
