So damned close we can taste it.
I can tftp the kernel off neon, the bootp server is up (but not tested
-- anyone have a good way to test without a reboot), and we've got a
serial terminal set up.
We've still got to get the console working on the serial line, but we
should be OK with that.
What's got me confused is this, from the archive (I think it's wje's
On an Indy, the booted kernel (or other program) must be in MIPS
ECOFF format. On Moosehead, the kernel must be in ELF format. The
"-coff" option to the IRIX ld will cause it to create an ECOFF binary
instead of an ELF binary in the final link, even if all the input
binaries are in ELF format. If you want to boot an ELF kernel on
Indy, you have to boot an indirect loader. You can use the IRIX sash.
Put sash in the volume header on the Indy, or in a bootp-able place on
the host system.
1) Where's sash? A find / on my Indy didn't turn up anything by that
2) What exactly does `bootp-able' mean? If I stick it in
/tftpboot/18.104.22.168/sash, does that count? (The Indy is my only
IRIX box, and I don't have the installation CDs, so I'm somewhat
loathe to go screwing with the disk.)
3) Once I get it booting (pls, pls) will the Linux kernel know how to
talk to the serial console?
4) I've just got the kernel as /tftpboot/22.214.171.124/vmlinux. DO I
need to add .IP22 or anything?
#> Mike Shaver (firstname.lastname@example.org) Ingenia Communications Corporation
#> Welcome to the technocracy.
#> "you'd be so disappointed
#> to find out that the magic was not
#> really meant for you" - OLP