> To start off the install, we begin with the “System setup and README” disk. We need to partition the disk, and then do something counter-intuitive: install System 6 on a Mac partition. This is because there’s a Mac application that kicks off the A/UX boot process: SASH; the A/UX standalone shell. This ‘pre-boot environment’ allows for launching an A/UX kernel and also some disk and recovery operations.
Funny how that rhythms with having a macOS install next to Asahi Linux. The more things change:)
Also, swapping through 26 floppies to install would have been... Something.
If I remember correctly, there's an interesting historical reason for this: a lot of the original functionality that we'd today consider "part of the OS" was actually in ROM on hardware in really old Macs. Mouse functionality, basic windowing, etc. This meant that to get A/UX running you first had to bootstrap into a light version of Mac OS and then boot into A/UX.
The Toolbox ROMs, right? I can see the utility of using that (I mean, beyond that you might need to use it to boot), but why couldn't A/UX call those APIs itself? I can easily see where bootstrapping through Mac OS would be easier, but I can't immediately see why it would be particularly necessary.
there will always be a special place in my heart for a/ux. i ported a lot of open source software to it. ran a bbs, cu-seeme server, gopherd, httpd, and many other early internet services on it. this really gave me an early taste for what the internet would become.
> To start off the install, we begin with the “System setup and README” disk. We need to partition the disk, and then do something counter-intuitive: install System 6 on a Mac partition. This is because there’s a Mac application that kicks off the A/UX boot process: SASH; the A/UX standalone shell. This ‘pre-boot environment’ allows for launching an A/UX kernel and also some disk and recovery operations.
Funny how that rhythms with having a macOS install next to Asahi Linux. The more things change:)
Also, swapping through 26 floppies to install would have been... Something.
If I remember correctly, there's an interesting historical reason for this: a lot of the original functionality that we'd today consider "part of the OS" was actually in ROM on hardware in really old Macs. Mouse functionality, basic windowing, etc. This meant that to get A/UX running you first had to bootstrap into a light version of Mac OS and then boot into A/UX.
The Toolbox ROMs, right? I can see the utility of using that (I mean, beyond that you might need to use it to boot), but why couldn't A/UX call those APIs itself? I can easily see where bootstrapping through Mac OS would be easier, but I can't immediately see why it would be particularly necessary.
> Also, swapping through 26 floppies to install would have been... Something.
Windows 95 was about that size, and Office was closer to 50?
At my very first job I remember installing stuff that way...ugh
A/UX 1.0 came on a pre-written 80MB disk, which indeed would have been a lot easier.
Oh, that's even better:) I assumed the mentioned tape was the preferred way to get it, but a no-op install is faster/easier yet!
there will always be a special place in my heart for a/ux. i ported a lot of open source software to it. ran a bbs, cu-seeme server, gopherd, httpd, and many other early internet services on it. this really gave me an early taste for what the internet would become.