Also sprach SA on Monday 04 March 2002 14:36: > Make sure your /boot images and files in /boot for 2.4.9-31 are like this:
Thanks for your reply, Peter, here is the essence of my actual /boot directory: -rw-r--r-- 1 root root 264789 Mär 4 19:25 initrd-2.4.9-31.img lrwxrwxrwx 1 root root 14 Mär 3 14:39 kernel.h -> kernel.h-2.4.9 -rw-r--r-- 1 root root 405 Mär 3 14:39 kernel.h-2.4.9 lrwxrwxrwx 1 root root 20 Mär 3 19:07 module-info -> module-info-2.4.9-31 -rw-r--r-- 1 root root 13599 Jan 17 20:26 module-info-2.4.9-21 -rw-r--r-- 1 root root 13599 Feb 26 13:18 module-info-2.4.9-31 lrwxrwxrwx 1 root root 19 Mär 4 19:20 System.map -> System.map-2.4.9-31 -rw-r--r-- 1 root root 438427 Jan 17 20:26 System.map-2.4.9-21 -rw-r--r-- 1 root root 438666 Feb 26 13:18 System.map-2.4.9-31 lrwxrwxrwx 1 root root 16 Mär 3 19:07 vmlinuz -> vmlinuz-2.4.9-31 -rw-r--r-- 1 root root 973701 Jan 17 20:26 vmlinuz-2.4.9-21 -rw-r--r-- 1 root root 975103 Feb 26 13:18 vmlinuz-2.4.9-31 I NEVER have been using an initrd before, but, just in case, I made one - with no success. Booting kernel 2.4.9-31 hangs ... > and make sure your /boot/grub setup file info matches the right boot image > for kernel 2.4.9-31. The relevant part of my menu.list is: title = RedHat 7.1 (hda5, 2.4.9-31) root = (hd0,4) kernel = /vmlinuz-2.4.9-31 vga=normal hdb=ide-scsi hdd=ide-scsi root=/dev/hda6 initrd = /initrd-2.4.9-31.img > Did you make a boot floppy for k2.4.9-31??? If so try it out. I did, "mkbootdisk 2.4.9-31". Funny enough, it booted right away! > latest initscripts, mkinitrd and SysVinit or anything else 7.1 might need I think, I'm really up to date with all this stuff, so I'm really baffled. Klaus-Peter _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
