> Ok...wiped the second disk and am partitioning it now. Am I correct in > thinking that I can use fx -x to set it up like an option drive, add a > second efs partition, then adjust the sizes of the others as noted > above? How big should each be and what are they for? Coming from Alpha, > this sure looks quite a bit like our MILO booting method (where you need a > small FAT partition to hold the boot loader). I just want to avoid having > two 2GB paritions if I'm only using a small portion of one for booting > from...
All you need is 1 partition for root and 1 for swap, if you want additional ones, you can add them. > > * Get a kernel like 'vmlinux-2.2.14-r4x00-cvs-INDY.ecoff' > > Ok...where do I find this? I also need a URL for the tarball... Maybe easier to check out oss.sgi.com - lots of info there, including a complete ready-to-install redhat 5.2 distro. > > * Use 'dvhtool' to drop the kernel into the volume header on the 2nd > > disk. Something along these lines: > > dvhtool -v add vmlinux-2.2.14-r4x00-cvs-INDY.ecoff linux > /dev/rdsk/dks0d2vh I just ftp'd the kernel from the box connected to the net to the Indy root partition. > > * Set up a dhcp server somewhere on the lan using something like this: > Ugh! I forgot how to get the hardware address! Any > tips? Nevermind...just found it :-P I cheated here as well. I passed args to the kernel to tell it its own IP, NFS root partition and gateway. That allowed the kernel on the irix drive to load and then access a remote nfs drive for install. > > * Remove the IRIX disk from the system > > * Change the SCSI ID of the other disk to '1' I didn't do either of these! > > Is this really necessary? Couldn't I alter the environment vars in sash > (SystemPartition and OSLoadPartition)? > > > You don't *have* to go through the 'dvhtool' part if you > > don't want to, but if you don't you'll always be having to boot off of > the > > network or have a efs partition on the disk that you can put the kernel > on to > > and then boot to that. I'm hoping to at some point be able to figure out > the > > format of that volume header and be able to write something like dvhtool > to > > allow you to modify it. > > I'll look into this once I get booted up and running. I've helped Alpha > out a lot, so maybe I can apply some of that knowledge here... :-) I'm > assuming docs are lacking on the format of the volume header, but other > than that, what would help to figure this out? I kept my IRIX drive since it was a work machine. Its there OS so I left it on there. The second drive already existed and was already blank!! So I now have a dual-boot system. > Must be nice :-) My Irix install seems ok thusfar. It boots and runs > fine, despite me playing with the second drive. I'm lucky for that since > I cannot re-install due to lack of media :-P Anyone else think IRIX thrashes its drives too much? Seems to take forever for anything to load its got 160MB of RAM or something like that. Now that it works, I can load debian, but I got pissed at my windows machine and got the OK to whipe Win95 off and load Linux, now the Indy is pretty useful. I wonder if they know you can buy those things for about $50 these days. -- Evan __________________________________________________ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/
