Ian's site is definitely the most helpful for normal installs but as the offical tester for When Things Go Bad, here's a few things I noticed recently :
Installing to an O350, if you use a USB keyboard and mouse doing the graphical install, things will go nicely until you get to the Inst> prompt. Then the USB keyboard disappears. Oh crap. So the install by console method works fine but now you have a botched miniroot. A "fixup" blew the machine out of the water. 'C'ontinue or 'r'eload is probably a better choice. Better yet is to not bother with the graphics install, start straight from the console. They never did get USB working properly.
(I added < rm /etc/ioconfig.conf > to the shutdown script.)
6.5.21 is the earliest version that supports O350, by the way. Found that in the release notes, in case anyone searches for that in the future.
fx -> exercise -> sequential -> wri(te)-o(nly) takes about six hours with a 146 gb drive but still doesn't zero out the partition 1 miniroot. Ain't that sweet ? An Adaptec 2940 in a peecee will actually wipe the entire drive from its own BIOS. It's easy and works. There may be a way to do this from an Irix miniroot but I just gave up and put the 2U piece of shit in the closet. I hope it doesn't poison the moths.
On an Octane, graphical install from an external CD-ROM works well. However ... I have both an IDE DVD-Writer with a Yamaha adapter and a Toshiba (?) scsi dvd-rom removed from a dead O2. Trying the IDE dvd-writer first, everything went swimmingly until it got to the "List distributions" choice 1 under the Inst> prompt. "No Local CD-ROM Found." Wa ? Since it had just loaded the miniroot from the CD-ROM, I figured it was probably there. Choice 14-ed out, ran hinv. No cd-rom. Did "boot -f dksc(1,4,8)sash64" &c &c, booted fine to sash from the exact same cd-rom that 12 seconds previous it couldn't see to open the distribution.
Well crap, let's try the real scsi cd-rom. Maybe it's picky during the install phase.
Same result. What the hell ? Remembered that jan-jaap once said drives need to have parity enabled. Scrounged up a jumper and enabled parity on the drive. It had been disabled because with the parity jumper in place, I got lots of spurious error messages. With the parity jumper on the drive, it now 1) gave some error messages booting into Inst> but 2) saw the CD-ROM at the Inst> prompt and showed the drive with an hinv.
So, hell. If you get some weirdass problems from your CD drive during installation, it might help to play with the parity jumper. Didn't retry the IDE-Yamaha combo but it is probably the same. Next time I install (hopefully never) will test that. Pre-Inst> and post-install it works mostly fine without parity.
Along with USB, they never really got cd-rooms working reliably. You know, ...? well, anyway ...
After installation, both of them are a little flaky until you get some of the Irix utilities installed (mediad, maybe ?) so Be Prepared and Stay Calm. Then they seem to settle down.
Got 21 running, I have looked all over the innertubes and found either very basic installs with no desktop and barely a command line (can do 'ls' and 'cd' but not much else) or the "install standard" process that installs three different non-functional web browsers, five insecure web servers, two incompatible help documentation systems and two cycle-gobbling services that no longer exist. Not kidding. This
Inst> keep *
Inst> install required
Inst> install default eoe 4Dwm desktop_base x_eoe desktop_eoe
Inst> keep *.books *.man
Inst> install prereqs
Inst> go
will give you a very basic but completely working Irix desktop with no baggage. There's no System Manager so you either have to set up networking by hand (not a big deal) or install the desktopsysadm package right away. I discovered there's no command line way to add users and groups, except by editing the password and group file. That was kind of a shock. Software manager will be there tho, so adding exactly what you want is easy.
The nice thing about Software Manager as opposed to Inst> is that you can easily open up the packages and see what's inside, then choose what you want. Yes you can do this with Inst> but it's a pain in the rear to keep track of everything. Software Manager is okay.
This probably isn't for everyone (if I had never done an Irix install before I'd be screaming and pounding my head against the wall) but the results are good. Not gonna lie, 2 x 400 !> 2 x 800, but with a clean 6.5.21, it's not as sleepy as you'd think. And an Octane turns on when you push the button.
Although mine still bitches about the botched miniroot. I'm thinking of leaving it there as a security measure. Anybody who can get past that is welcome to the computer and any nekkid photos inside. They're probably hackers from the China government anyhow, we can't possibly hope to out-think those guys !
Extra credit question : who is stupider, the NSA or the people who believe their bullshit ?
Installing to an O350, if you use a USB keyboard and mouse doing the graphical install, things will go nicely until you get to the Inst> prompt. Then the USB keyboard disappears. Oh crap. So the install by console method works fine but now you have a botched miniroot. A "fixup" blew the machine out of the water. 'C'ontinue or 'r'eload is probably a better choice. Better yet is to not bother with the graphics install, start straight from the console. They never did get USB working properly.
(I added < rm /etc/ioconfig.conf > to the shutdown script.)
6.5.21 is the earliest version that supports O350, by the way. Found that in the release notes, in case anyone searches for that in the future.
fx -> exercise -> sequential -> wri(te)-o(nly) takes about six hours with a 146 gb drive but still doesn't zero out the partition 1 miniroot. Ain't that sweet ? An Adaptec 2940 in a peecee will actually wipe the entire drive from its own BIOS. It's easy and works. There may be a way to do this from an Irix miniroot but I just gave up and put the 2U piece of shit in the closet. I hope it doesn't poison the moths.
On an Octane, graphical install from an external CD-ROM works well. However ... I have both an IDE DVD-Writer with a Yamaha adapter and a Toshiba (?) scsi dvd-rom removed from a dead O2. Trying the IDE dvd-writer first, everything went swimmingly until it got to the "List distributions" choice 1 under the Inst> prompt. "No Local CD-ROM Found." Wa ? Since it had just loaded the miniroot from the CD-ROM, I figured it was probably there. Choice 14-ed out, ran hinv. No cd-rom. Did "boot -f dksc(1,4,8)sash64" &c &c, booted fine to sash from the exact same cd-rom that 12 seconds previous it couldn't see to open the distribution.
Well crap, let's try the real scsi cd-rom. Maybe it's picky during the install phase.
Same result. What the hell ? Remembered that jan-jaap once said drives need to have parity enabled. Scrounged up a jumper and enabled parity on the drive. It had been disabled because with the parity jumper in place, I got lots of spurious error messages. With the parity jumper on the drive, it now 1) gave some error messages booting into Inst> but 2) saw the CD-ROM at the Inst> prompt and showed the drive with an hinv.
So, hell. If you get some weirdass problems from your CD drive during installation, it might help to play with the parity jumper. Didn't retry the IDE-Yamaha combo but it is probably the same. Next time I install (hopefully never) will test that. Pre-Inst> and post-install it works mostly fine without parity.
Along with USB, they never really got cd-rooms working reliably. You know, ...? well, anyway ...
After installation, both of them are a little flaky until you get some of the Irix utilities installed (mediad, maybe ?) so Be Prepared and Stay Calm. Then they seem to settle down.
Got 21 running, I have looked all over the innertubes and found either very basic installs with no desktop and barely a command line (can do 'ls' and 'cd' but not much else) or the "install standard" process that installs three different non-functional web browsers, five insecure web servers, two incompatible help documentation systems and two cycle-gobbling services that no longer exist. Not kidding. This
Inst> keep *
Inst> install required
Inst> install default eoe 4Dwm desktop_base x_eoe desktop_eoe
Inst> keep *.books *.man
Inst> install prereqs
Inst> go
will give you a very basic but completely working Irix desktop with no baggage. There's no System Manager so you either have to set up networking by hand (not a big deal) or install the desktopsysadm package right away. I discovered there's no command line way to add users and groups, except by editing the password and group file. That was kind of a shock. Software manager will be there tho, so adding exactly what you want is easy.
The nice thing about Software Manager as opposed to Inst> is that you can easily open up the packages and see what's inside, then choose what you want. Yes you can do this with Inst> but it's a pain in the rear to keep track of everything. Software Manager is okay.
This probably isn't for everyone (if I had never done an Irix install before I'd be screaming and pounding my head against the wall) but the results are good. Not gonna lie, 2 x 400 !> 2 x 800, but with a clean 6.5.21, it's not as sleepy as you'd think. And an Octane turns on when you push the button.
Although mine still bitches about the botched miniroot. I'm thinking of leaving it there as a security measure. Anybody who can get past that is welcome to the computer and any nekkid photos inside. They're probably hackers from the China government anyhow, we can't possibly hope to out-think those guys !
Extra credit question : who is stupider, the NSA or the people who believe their bullshit ?
Juliet ! the dice were loaded from the start ...