These are unofficial rpms of the sparc kernel rpms. They contain the patched code to stop the teardrop attack on 2.0.30 kernels. The 2.0.32 kernel is being worked on and may be released in a 2days to a week by the Sparc Linux development people. I will release other RPMS of that kernel (if not official ones) when they come out. Here are some instructions that I use with the i386 mode to install kernel and kernel modules that have the same version number (ie you have 2.0.30 and want to install newer 2.0.30 kernel modules). I do not know how useful they are with Sparcs, but thought I would include them for completeness. Due to the fact that the rescue mode on the floppy disks is a work in progress, we have to work around some of its limitations when having to rescue a system that is in dire strait's. So instead of using the linux rescue mode, we will act like we are doing an install, and get the various cd data up. Insert the boot floppy and at the boot prompt, hit return. Go through the questions of monitor type, finding the cdrom, etc. until we get a choice of whether we are doing an upgrade or an install. When the screen comes up asking what partition to install as root, we will change to Virtual Console 2 with the keystroke ALT-F2. Now we are ready to begin "real rescue mode." You should now be at a # prompt with the cdrom mounted at /tmp/rhimage. To make things easier in the future, do the following: ln -s /tmp/rhimage/live /cdrom export PATH=/bin:/usr/bin:/sbin:/usr/sbin:/cdrom/bin:/cdrom/usr/bin:/cdrom/usr/sbin:/cdrom/sbin This will get you a shorthand to the live cdrom executables that you might need to get the machine up and going. If we need to repair your harddrives, you should be able to do a fsck of the appropriate partitions. If you need to see what partitions you might have, I use cfdisk to get a picture of which ones are Linux partitions. If we need to install a new or old kernel to replace a broken set, the following will get them working (the hda partitions are example only. Change to suit your hard-drive). mkdir /mnt mount /dev/hda1 /mnt mount /dev/hda2 /mnt/usr cd /tmp/rhimage/RedHat/RPMS # rpm --root /mnt -qa | grep kernel- kernel-2.0.30-2 kernel-modules-2.0.30-2 kernel-headers-2.0.30-2 kernel-source-2.0.30-2 # rpm --root /mnt -qa | grep pcmcia pcmcia-cs-2.9.4-2 # rpm --root /mnt -e pcmcia-cs # rpm --root /mnt --noscripts -e kernel-modules # rpm --root /mnt -Uvh kernel-* pcmcia* # rpm --root /mnt -qa | grep kernel kernel-2.0.30-3 kernel-modules-2.0.30-3 kernel-headers-2.0.30-3 kernel-source-2.0.30-3 # rpm --root /mnt -qa | grep pcmcia pcmcia-cs-2.9.5-3 ls /mnt/boot/vmlinu* # to see where /mnt/boot/vmlinu* -> is pointing to. sync ; sync # to force the data to be written to disk. look in your /mnt/etc/conf.modules to see if the correct SCSI modules are being looked for or other items you might need to boot with, and edit it if you need to. insmod /mnt/lib/modules/2.0.xx/block/loop.o cd /mnt chroot /mnt mkinitrd -v -f initrd-2.0.xx 2.0.xx # where xx is the kernel # you are looking for. edit /mnt/etc/lilo.conf to get the new kernel being booted. lilo -r /mnt sync ; sync # to force buffers to be cleaned. umount /mnt reboot the system with a CTRL-ALT-DEL .