Technology

Amiga Unix Is Bootable Again on 68040 and 68060 Machines

Martin HollowayPublished 2d ago4 min readBased on 2 sources
Reading level
Amiga Unix Is Bootable Again on 68040 and 68060 Machines
Photo by "Joe Smith" (Uploader of original was Joeinwap at en.wikipedia (Changes made by Ubcule)) / Public domain

Commodore's Unix for the Amiga boots again on 68040 and 68060 hardware. The work is an unofficial community project published at amigaux.org, with asokero, isoriano1968 and jusii listed as maintainers. It aims to keep Amix running on period 040 and 060 machines and on modern accelerator boards.

Amix shipped in 1990-92 for the A2500UX and A3000UX. It put full AT&T System V Release 4, the standard commercial Unix of the time, on Motorola 68030-based Amigas, with Commodore hardware adapted for workstation use. Commercial sales lasted only a short time.

Interest in surviving discs picked up earlier in 2026. Amiga Unix version 2.02 was treated as lost until Forgotten Computer recovered it from an old Amiga, as reported by Hackaday on May 25, 2026. The report was titled "Lost Version Of Amiga Unix Suddenly Reappears". Forgotten Computer also released a video explaining what Amiga Unix is, how the disc was found, and what is on it.

The AmigaUX project set two public dates around Saku 2026. Its Amiga Unix 68040/68060 launch was set for Saku 2026 at Oulun Tetra in Oulu, Finland. Its Amiga Unix Desktop 2026 was set to go live on 19 September 2026 at 17:00 Finnish time (EEST).

The current baseline is Amix 2.1 running on a real 68060. The project says it runs with or without an FPU, the optional math chip. An MMU, the memory hardware Unix needs to keep programs separate, is mandatory.

The focus is hardware support. The project reports working SCSI storage and ethernet network drivers for the Z3660 accelerator, tested on real hardware. It also reports a Zorro III SCSI driver, for a late Amiga expansion standard, and a kernel that auto-detects A4091/A4092 storage cards. That covers storage and network setup on machines where old drivers were missing or incomplete.

Installation now covers real machines and emulation, where software on a modern PC acts as the old computer. The medium boots from floppy and CD-ROM on real hardware, and from floppy image and ISO under emulation. The installer offers step-by-step and unattended, or automatic, setup. A fresh install starts with the OpenLook desktop, the windows and menus system.

Software updates follow a familiar Unix method. The apkg package manager fetches packages from pkg.amigaux.org, starting with grep, gzip, less, patch and zlib. The list is short. It sets up the download path rather than rebuilding everything at once.

Build tools run on Linux. The project supplies a cross toolchain called m68k-cbm-sysv4, which builds software on a modern PC for the old Motorola chip. Because no source code survives for parts of the old system, the team uses generative AI to help read old kernels in binary form, with human review and testing on real hardware. Quake runs on Amix, according to the project, used here as a stress test for tools, graphics, input and speed on 060-class processors.

The broader context here is preservation through continued use. Many older Unix efforts stop at saving disc images. This one adds automated install, package downloads over the network, and new drivers for cards that never had them.

In my view, that is what makes it interesting for working technologists. Writing a Zorro III SCSI driver in 2026, fixing MMU behavior on a 68060 without vendor help, and checking a cross compiler against System V programs is quiet systems work. It keeps a commercial Unix usable rather than viewable. One method is worth flagging, machine-assisted reading of closed binaries paired with human review and hardware testing, a routine now common in legacy support and security research.

My kids grew up with installs that never touched a disc. Watching an OpenLook session arrive from floppy and CD-ROM, then pull packages over ethernet from a live repository, is a useful reminder. Long life rarely comes from the vendor plan. It comes from installers, drivers and toolchains kept up after the vendor leaves.