Live data from Hacker News

So what is the deal with A/UX anyways?

virtuallyfun.com

151–160 of 166 posts

Re: So what is the deal with A/UX anyways?

#151
post #111

Does anyone have a .zip or something of an emulator with this all up and running?

this is the 'emaculation' windows build:

https://sourceforge.net/projects/bsd42/files/4BSD%20under%20...

decompress and run the batch file.

I didn't bother installing X11 as anything else is a better X11 than the one mouse button Mac.. I enabled TCP/IP and you can telnet in on 127.0.0.1 42323

Enjoy!

Re: So what is the deal with A/UX anyways?

#152

Earlier quoted context omitted.

Right-click, "Search Google for A/UX". Wikipedia article is the first link. Try harder.

Why would I try harder for something that _might_ be interesting? That's just bad writing. If I can’t tell what something’s about from the first couple paragraphs or a quick skim, I’ll tune it out. I have plenty of other content to read.

I chose to introduce it slowly setting where it came from. I wasn't aiming to write an encyclopedia entry. Otherwise it'd be a one liner.

Can't please them all.

Re: So what is the deal with A/UX anyways?

#153
post #74
post #24

This YouTube video on A/UX https://www.youtube.com/watch?v=nwrTTXOg-KI is one of the best things I've found about the subject. (It has a usable transcript.) On the subject of what happened with Big Mac, the Macintosh II and NeXT, https://lowendmac.com/2013/apples-bigmac-project-failed-prec... and some of the articles linked from it https://lowendmac.com/2013/next-years-steve-jobs-before-triu... https://www.aventure-a…

* On the software side, Big Mac's vision of Unix with Macintosh on top is familiar from NeXT and OS X. It was also roughly paralleled by many other projects, from Pink/Taligent and BeOS to OS/2 and WinNT. But it's worth asking where Jobs and the other Big Mac supporters got the idea from in turn. One obvious source of inspiration for the NeXT work was Xerox PARC, and Jobs seems to have been acknowledging (or claiming…

> That just leaves the PARC-influenced "object-oriented" element which later showed up on the NeXT in the form of Objective C and the NeXT APIs. Had Big Mac's software already taken some steps in this kind of direction? Or was it an ambition for later, or simply not on the roadmap at all yet? I have no idea.

This was already present on the classical Macs, and Lisa, via the Object Pascal frameworks, and later evolved into its C++ replacement.

Copland was also heavily C++ based.

Re: So what is the deal with A/UX anyways?

#154

Earlier quoted context omitted.

Now in retrospect some workstation vendors could maybe have survived a little more by switching to x86 PC like hardware except the window for doing the switch was astonishingly small and they would have transformed to either a random OS vendor, or a random PC hardware vendor, or even both I think this window was non-existent: Moore’s Law at the time was turning white boxes into workstations faster than any time-and-m…

I'm not sure about that, even today. The typical white box PC motherboard then (and now) doesn't support 128gb of memory for example, you have to buy a HP Z400 or a Mac Pro (or an old server). Plus they aren't really designed to be maintained, or have space for dual processors. The Sun/HP/DEC/IBM workstations were not purely bought because they were fast, there was often specific software in mind that the end user wa…

Same here. The 5yo Lenovo trounces the 2yo top of the line x86 MacBook Pro on pretty much everything. When it was young it easily humiliated every computer in the house.

Re: So what is the deal with A/UX anyways?

#155
post #139
post #80

Earlier quoted context omitted.

My impression is that they all built desktop minicomputers possible thanks to CPUs like the 68K but moved on to RISC designs when the 68K started showing its age. I would not say the PA-RISC was open, but SPARC had multiple sources and MIPS showed up everywhere. At that period, the x86 was not an option - Sun tried.

Apollo was building bit-slice 68000 emulations (to have an MMU) into the mid '80s, and ran Aegis, their homegrown fully-networked GUI OS, coded in their home-grown Pascal, with their home-grown touchpad pointer and home-grown token-ring network, on those and on actual 68K into the late '80s. Aegis was inspired by MULTICS, not Unix, and was definitely a better system. They were demand-paging across the network in the…

> Aegis was inspired by MULTICS, not Unix, and was definitely a better system. They were demand-paging across the network in the early '80s.

I’d love to see one of those operating. We have lost so many great ideas we seem to never revisit…

Re: So what is the deal with A/UX anyways?

#156

Earlier quoted context omitted.

Have you ever played with this: https://macintoshgarden.org/apps/aux-apple-unix-68k-version-... I found it interesting that it mentions both ‘Milwaukee‘, and Cayman "brac" ... Here on the Jasmine 80. Seems like lots of weird codenames. It looks like UniSoft had done a lot of work on the code (you?) to make it super portable. Although everything not directly related to the Milwaukee was cut. It'd be interesting to see…

(here's probably too much information) yup I wrote a lot of that, I did all the console stuff (font renderer, vt100, mouse, keyboard, fdb/adb, ui event queue etc). Missing is all the auto config support (ability to add 3rd party drivers to the kernel in the field, something that at the time you usually couldn't do without source), fixes for large screen support, all my appletalk code is missing too. However I can see…

Cayman must be Cayman Systems (Cambridge, MA).

I'd seen this zip file floating around for well over a decade, maybe quite a bit longer. It was amazing to see someone write enough glue for an emulator to actually boot it. It's even more crazy to get 3.0.1 to mount it under Qemu and do a full build in 17 seconds... I can't even imagine how long it took to build this back in the day!

Apparently above Milwaukee has something to do with Gasse and the BigMac Jr.

I wonder what ever happened to Unisoft's unix business. I've always wanted a SYSV but they seem impossible to buy. Best I have is a non commercial SYSIII from SCO before they 'gave 32v' and lower away but it's all so murkey if they could give anything away but I think they could sublicense for a fee (best $100 ever!)

Re: So what is the deal with A/UX anyways?

#157
post #139

Earlier quoted context omitted.

Apollo was building bit-slice 68000 emulations (to have an MMU) into the mid '80s, and ran Aegis, their homegrown fully-networked GUI OS, coded in their home-grown Pascal, with their home-grown touchpad pointer and home-grown token-ring network, on those and on actual 68K into the late '80s. Aegis was inspired by MULTICS, not Unix, and was definitely a better system. They were demand-paging across the network in the…

> Aegis was inspired by MULTICS, not Unix, and was definitely a better system. They were demand-paging across the network in the early '80s. I’d love to see one of those operating. We have lost so many great ideas we seem to never revisit…

Another was a read() system call that would copy into a caller-supplied buffer if it had to, but would normally just return a pointer into its buffer cache.

Re: So what is the deal with A/UX anyways?

#158

Earlier quoted context omitted.

(here's probably too much information) yup I wrote a lot of that, I did all the console stuff (font renderer, vt100, mouse, keyboard, fdb/adb, ui event queue etc). Missing is all the auto config support (ability to add 3rd party drivers to the kernel in the field, something that at the time you usually couldn't do without source), fixes for large screen support, all my appletalk code is missing too. However I can see…

Cayman must be Cayman Systems (Cambridge, MA). I'd seen this zip file floating around for well over a decade, maybe quite a bit longer. It was amazing to see someone write enough glue for an emulator to actually boot it. It's even more crazy to get 3.0.1 to mount it under Qemu and do a full build in 17 seconds... I can't even imagine how long it took to build this back in the day! Apparently above Milwaukee has somet…

After I left the Unix biz changed, we'd made money doing lots of ports for small companies, as Sun/SGI/etc got successful there were fewer of them, then we did the 88k and 29k ports but those guys didn't really take off. Doing A/UX also kind of screwed the company, I think it made us ignore our smaller customers, we expanded a bit too much, moved into a nicer building. We also didn't do an x86 port, which was a mistake - we actually helped SCO with the MMU portion of the SysV 286 port, there was some deal where we were supposed to get a copy but somehow that didn't happen (no love lost there).

UniSoft still exists, these days they sell digital video stuff (which was very weird when I became a cable/sat protocol engineer for a while a decade or so ago).

Reading what other people have been saying "Milwaukee" might have been a Mac2 code name.

Re: So what is the deal with A/UX anyways?

#159
post #7
post #3

I truly believe that A/UX doesn't get the credit it deserves. Was it ambitious? Sure. Did it it fully succeed in the goals it set for itself? Not really. But it was really a very nice integration of the Finder and UNIX. After all these years, I still look back on it with fondness. It certainly was a cornerstone platform for me.

Interesting that the article calls out the price point as one of the reasons it didn't succeed. Although a lot of that was the OS only having drivers for expensive hardware and being unusable on the lower end Macs. That said, high price killed off most of the legacy Unix vendors/products. The world was changing around them and they weren't ready or able to give up the profit margins they had enjoyed for so long. Pers…

Imagine in today’s money sinking 12,000 USD on a computer.

Do you take the Macintosh II with A/UX aka Unix from a company that doesn’t seem all too interested in the product themselves and selling what seems like a toy or do you go with SUN? They hired Bill Joy, and they are 100% committed to Unix?

They simply cost too much for a non commital company like Apple. If anything it’s amazing they saw it through to the end of the Quadra

Re: So what is the deal with A/UX anyways?

#160
post #47

Earlier quoted context omitted.

> The Unix workstation was the triumph of COTS micros over LSI or custom VLSI hardware. Well the Sun-1 definitely started there, no question (I don’t remember the Daisy or Apollo hardware). HP definitely never did and Sun (and SGI et al) all went down the custom hardware rabbit hole. By the time they tried to hop onto the PC hardware train it was too late. None of those companies survive in any meaningful way. BTW if…

the SUN-1 was based on the SUN (Stanford University Network) board, but I can't find anything concrete on the SUN board (Also by Andy) other than it existing, and apparently 'cheap/free' to license? Apparently it formed the foundations of cisco/SGi & SUN.

Indeed, I remember those days well.
Post reply on HN