I bought my Octane on eBay in 2008 (it was previously used at Ford), I think it was around $80 and shipping was more than half of that (an Octane weighs ~80 lbs).
Here's a crazy one I saw yesterday: the Canadian government auctioning an unused Origin 3400, still in shipping crate. https://www.gcsurplus.ca/mn-eng.cfm?snc=wfsav&sc=enc-bid&scn...
In those days I got an extremely cheap Sun workstation on ebay as an example.
Anyway, I guess supply is low but there are still nerdy people who think an old Unix machine is cool. (I'd take one running Irix just to play with for sure.)
e.g. 10 years ago people were dumping CRT monitors, now a decent Sony Trinitron starts at 150-200 €
I remember saving for what seemed like an eternity, then buying a used (and only slightly defective) Trinitron from a friend's dad (who was a draughtsman) round about '97.
I don't recall what size it was, but the point was it was big for the day, like 24" - it was so heavy that me and my dad could barely lift it! When we got it home, it bowed my wooden desk in a very threatening way, but managed to sit there for a couple of months before it finally broke through the desk!
"The OpenBSD/sgi port was discontinued after the 6.5 release."
That said, it was a very mature port and ran on many models, in 64-bit mode.
The code remains in -current for now.. the last release, 6.5 is a complete modern (was released in 2019) Unix operating system, which is more than can be said for running IRIX or Linux on these machines. I'm not even _aware_ of any binary distros of Linux for these. And good luck building your own kernel and userland.
I guess the reason is that they used an Origin 350 for builds, but the disk controller driver had a bug causing lockups and FS corruption which never got fixed.
https://marc.info/?l=openbsd-cvs&m=156941089510768&w=2
I also remember Miod Vallat doing a lot of the work on sgi, but he left the project a few years ago.
I feel the same. Indy amd O2 were amazing computers. I got rid of all my SGI gear. Every so often I feel a pang of regret...
This is not a criticism, but I would like to deeply understand, what does Linux leadership want it to be? An OS that just runs on anything for the sake of it?
It already seems true that Linux aspires to be much more than what UNIX is. It can be a dumping ground of sorts for your ideas and research projects. As long as the code does something useful enough without corrupting the entire system, it seems to be fair game. That is kind of freeing and it would stand to benefit the project to be communicated more directly. These are my observations.
Some subsystems have stricter guidelines yet, e.g. if you want to add support for graphics hardware to DRM, the graphics subsystem, there must be a corresponding, fully featured open source userland implementation for it.
This is not a criticism, but I would like to deeply understand, what does Linux leadership want it to be? An OS that just runs on anything for the sake of it?
NetBSD falls under this, for example, but NetBSD also has many other benefits and aims than "Can run on your Burroughs P100."
Linux has ~5k people a year contributing patches to the kernel; it can have many aims, because "Linux leadership" doesn't mean "Linux dictatorship."
It's not quite like that, there's quite a bit of hardware support that has been dropped along the way. It's not enough for people to care about stuff, they have to care about it enough that they maintain that support in line with kernel devs' expectations. That's not always easy.
The inclusive attitude is exceptional for drivers and new architecture support. The kernel is intended to be portable, the more architectures supported the more mature the abstractions become. So as long as there's existing hardware capable of running the kernel for the new architecture, you probably won't meet much resistance landing support, provided it's not a disaster.
> the more architectures supported the more mature the abstractions become.
I don't think so. I mean, yes, there's some pretty obscure things in there. But to be part of the mainline kernel means that you're code must pass all sorts of gatekeepers. The code has to meet a number of quality and appropriateness checks. A good number of eyeballs have to sign off, or at least no object.
It happens again and again:
There's a plateau of Real Computers, where Real People do Real Work, because they wouldn't deign to deal with the oddities and lack of performance peasants put up with on their Bitty Boxes.
Then something nasty happens, and those Bitty Boxes become more capable without becoming correspondingly more expensive. All of a sudden, the companies selling Real Computers no longer have a value proposition: Their stuff may not be hugely more capable, but at least it's massively more expensive!
Eventually, not even the Real People can continue to ignore the fact the Toys are smoking them in every benchmarkable metric aside from cool factor.
It happened to DEC when minicomputers fell to PCs, and it happened to Sun and SGI when the "workstation" category got folded into the "somewhat-more-expensive-than-usual PC" category.
Linux originally ignored the extreme low-end PCs, but in 1991, it was pretty clear than 16-bit x86 CPUs were more trouble than they were worth in the Unix-like world and it wasn't a good move to mutilate the kernel to fit on a kind of system which was rapidly becoming obsolete. However, Linux is not ignoring the current Bitty Boxes, the SBCs which can run the kernel with no compromises once you navigate the weirdness of ARM-based hardware.
(Yes, there is a project to run Linux on 16-bit x86 chips and other MMU-less CPUs. It's called ELKS and it was never very active.)
Anyway, it is a shared memory system, and under IRIX, that was done dynamically. The same chips were used in their NT visual workstations. Those did not manage the graphics memory dynamically, but were capable in every other way.
At the time, one could push 500mb plus images around like nothing. Was a big deal.
SGI did Linux drivers, and the SGI / Microsoft Farenheit project got in the way. Those never left SGI for legal reasons. Had that happened, perhaps Linux for an O2 would make sense.
I am not sure that system has ever seen a low level document release.
The 1st gen Visual Workstations had a different chipset called 'Cobalt', but also had a Unified Memory Architecture.
Makes me feel very old!
There are also Fibre Channel adapters for these if you have the XIO-PCI card cage. Can boot from it with some special magic IIRC, but a local SCSI drive is fine for most things.
https://store.inertialcomputing.com/product-p/scsi2sd-v5-st3...
But sure, if you're just tooling around, nfsroot is convenient.
Though network booting and storage may well be an easier avenue and cheaper. If you already have a NAS, that may well be the easiest path.
It's possible to install gigE, but you will need a PCI-X shoebox and also a NIC with compatible firmware. Not super easy to find.
Little ominous though how heavily it’s reliant on linus being available. I hope the business continuity planning is up to spec