What I have done is hooked up a Seagate Barracuda Drive to our new Multia.
I've left the 3.0.3 RedHat on the small internal drive, but wanted to
install 4.0 on the Seagate (sdb). I finished the NFS install to sdb3
(sdb2 is the swap) and it seemed to be all ok. I had to export NFS
with the insecure option for this to work.
Then booted from MILO "boot sdb3:vmlinux.gz" and it ended up booting
from sda2 (the original 3.0.3 installation). So I thought AH-HA!
I need to rdev the kernel that is sitting on sdb3 so it knows what
root fs, swap to use. The only problem is it has some hex number
when I do:
rdev /mnt/tmp/vmlinux.gz (where mnt/tmp is /dev/sdb3)
So I set this like so, disregarding the hex numbers:
rdev /mnt/tmp/vmlinux.gz /dev/sdb3
rdev -s /mnt/tmp/vmlinux.gz /dev/sdb2
rdev -r /mnt/tmp/vmlinux.gz 48xxx (I looked up the xxx)
rdev -R /mnt/tmp/vmlinux.gz 1
This gives me a "length error -- halting" message? I'm trying desparately
to learn about the Alpha flavor of Linux. Please help.
Thanks,
Scott Serr
serrs@uffenham.isu.edu
-- To unsubscribe: mail -s unsubscribe axp-list-request@redhat.com < /dev/null
Copyright © 1995-1997 Red Hat Software. Legal notices