wdbreen said: Gday Guys,
"The file just loaded does not appear to be executable"
Then just an ok prompt.
Can you boot into rescue mode from CD and then chroot (the menu proposes to do so) into your already-installed linux root partition?
Sounds like either SILO's installation went wrong or the symlinks in / or /boot for the initrd-kernel are somehow broken. I don't have a Sun box running permanently at home to copy& paste from. On my PC this looks somehow like this:
[FONT="Courier New"][SIZE="1"]marc@blaze:/$ ls -al
[...]
lrwxrwxrwx 1 root root 32 2006-06-28 18:56 initrd.img -> boot/initrd.img-2.6.15-25-server
lrwxrwxrwx 1 root root 32 2006-06-22 20:26 initrd.img.old -> boot/initrd.img-2.6.15-23-server
[...]
lrwxrwxrwx 1 root root 29 2006-06-28 18:56 vmlinuz -> boot/vmlinuz-2.6.15-25-server
lrwxrwxrwx 1 root root 29 2006-06-22 20:26 vmlinuz.old -> boot/vmlinuz-2.6.15-23-server
[...][/SIZE][/FONT]
Your kernel and initrd.img file names will probably be different. In general, silo.conf refers to the symlink of initrd.img and will look for vmlinuz in the "root =" partition given in silo.conf.
Check that thes files or their symlinks exist in the places SILO will be looking for them.
kind regards
Marc