←back to thread

55 points todsacerdoti | 1 comments | | HN request time: 0s | source
Show context
neilv ◴[] No.26595984[source]
Apollo Domain/OS was great, innovative, and opinionated. It wasn't just another BSD or System V, and they rethought a lot of things.

Apollo's heyday was a bit before my time, but my first real job was working on technical software at a company who was a big-ticket technical software developer on Apollos (and I even once saw marketing brochure with our badge on an Apollo workstation). As an intern, I set up a pair of them for porting (though we preferred SPARCstations), and later, when I moved to headquarters, HQ was still doing the master SCM and (what's now called) CI, for all platforms, on Apollo DN10k pedestals. We got the DSEE descendant Atria ClearCase on non-Apollo workstations, in a new-tech R&D group I was in. I bought a couple retired Apollo workstations just to play with them at home.

Apollo did a lot of innovative stuff in Domain, and it's one of the few platforms I'm sometimes tempted to buy again, just to play with it and understand more of how they approached things.

When it had been years since I'd seen or heard of Apollo anywhere, I bumped into someone from there, who mentioned that Boeing had done some documentation using Apollos, and part of their very serious configuration management process involved them physically archiving an entire Domain network. (I'm guessing they used the very nice Interleaf software, which seemed to be popular on Apollo, and, by that time, had long also been available on other platforms.) It was appealing to think of an Apollo Domain network preserved in stasis, should humanity ever need to call up Apollo for duty again.

replies(3): >>26597283 #>>26598177 #>>26599667 #
ncmncm ◴[] No.26599667[source]
Domain/OS, later "Domain/IX" (we were told the "IX" meant "9", but weren't fooled; everyone called it "domainix") inherited from Aegis a powerfully useful feature still missing in Unix and Linux: environment variable references could appear in symbolic link text, and be expanded when the link was followed.

Dragonfly BSD has adopted a similar but rather clumsier version of the feature.

People always think at first that this would introduce security problems, but I have not heard of a plausible one.

(As an aside, corporate marketing departments were always coming up with reasons why "their" unix mustn't be called unix. People not fooled just stuck "-ix" on the end. E.g., Sun promoted their "Solaris", thus "solarix". That is why Apple's thing is still called "macosix" by those of us who know better; similarly, Windows is pronounced "windos".)

replies(1): >>26600967 #
1. neilv ◴[] No.26600967[source]
AT&T didn't share Unix as well as would be modern commercial open source convention, but there was also a culture of non-commercial sharing at the time. So, besides not wanting to step on the trademark or copyrights, and hear from lawyers, there was also a sense of fighting back against AT&T, even in marketing. (Also, Berkeley counterculture might've helped, I suppose.)

GNU = GNU's Not Unix

mt Xinu <= UNIX(tm)

https://ia601002.us.archive.org/3/items/Mt_Xinu_Mach_386_920...