ODFileSystem

ODFileSystem is a read-only optical-disc filesystem driver for Amiga systems. It is implemented as an AmigaDOS handler frontend with clean backend plugins for the various optical-disc formats it supports, allowing it to mount and browse CD-ROM, DVD, Blu-ray, and image-based media.

The project also includes host-side tools and tests so most parser and cache logic can be developed and validated outside an Amiga environment.

Purpose

ODFileSystem is the most modern and complete optical-disc filesystem for the Amiga. The handler deals with AmigaDOS packets, locks, and file handles, while the core library and backend parsers detect media formats, choose the appropriate view of hybrid discs, enumerate directories, and read file data.

ODFileSystem can:

• mount optical media through a standard AmigaDOS handler
• support common CD/DVD filesystem formats and hybrid discs
• present a consistent read-only file and directory model to Amiga software
• allow most logic to be tested on a host machine using image files

Supported Filesystems And Features

Filesystems

ODFileSystem currently includes backends for:

• ISO 9660
• Rock Ridge
• Joliet
• UDF
• HFS
• HFS+
• CDDA virtual audio tracks

Features

• Read-only AmigaDOS handler for optical media
• Multisession support, with the last session selected by default
• Hybrid-disc precedence rules
• Deterministic duplicate-name handling after normalization or charset conversion
• Rock Ridge, Joliet, UDF, HFS, and HFS+ probing
• Path lookup, directory enumeration, and file reads
• Block-cache based media access
• Host-side tools for inspecting image files

Feature Matrix

Filesystem	Status	Notes
ISO 9660	Supported	Plain ISO 9660 names and directory traversal
Rock Ridge	Supported	Preferred over plain ISO when present
Joliet	Supported	Preferred over plain ISO when Rock Ridge is absent
UDF	Supported	Bridge discs default to ISO-family content unless forced
HFS	Supported with limitations	Data fork only
HFS+	Supported with limitations	Data fork only; resource forks are not exposed
CDDA	Supported	Exposed as virtual WAV files

Format Selection Rules

For ISO-family hybrids, the default precedence is:

1. Rock Ridge
2. Joliet
3. Plain ISO 9660

For bridge and hybrid discs:

• ISO-family content is preferred over UDF by default
• ISO-family content is preferred over HFS by default
• UDF can be preferred explicitly
• HFS can be preferred explicitly
• A specific session or backend can be forced by mount options

UDF and ISO on the same disc are usually a bridge layout, where the ISO-family side exists for older systems and the UDF side exists for newer ones. On Amiga, the ISO-family view is the safer default because:

• Rock Ridge and Joliet map more naturally to the naming and metadata path the handler already exposes
• hybrid optical discs historically expected older systems to use the ISO side
• plain ISO-family trees are generally the least surprising fallback
• UDF support is newer and more likely to hit edge cases on odd media

So the default is essentially:

• prefer the more traditional, compatibility-oriented view
• let the user opt into UDF when they actually want that view

That is why the handler has an explicit UDF override instead of making UDF the default on bridge discs.

To prefer UDF for a bridge disc from the Mountlist, add:

Control = "UDF"

You can combine that with other control flags, for example:

Control = "UDF LOWERCASE FILEBUFFERS=128"

Name Collision Policy

If multiple on-disc names normalize to the same visible AmigaDOS name, the first entry keeps the unsuffixed name and later entries are renamed deterministically in on-disc order using ~2, ~3, and so on.

HFS And HFS+ Limitations

• Only data forks are exposed. Resource forks and Finder metadata are not presented as separate files or alternate streams.
• Because of those limits, some classic Mac software distributions may be incomplete when viewed through ODFileSystem even though their main data files remain readable.

CDDA

Audio tracks are exposed as virtual WAV files. On mixed-mode discs they appear in a CDDA/ directory, and on pure audio discs they appear at the root.

Amiga Rock Ridge AS

ODFileSystem now parses the Amiga-specific Rock Ridge AS SUSP entry on top of normal RRIP handling.

Current behavior:

• preserve the raw 4-byte Amiga protection field when present
• expose Amiga comments through the Amiga handler metadata path
• continue to use standard RRIP for names, timestamps, symlinks, and directory structure

Real-world AS source images used during development:

• Arabian Nights (1993)(Buzz)(M4)
• Benefactor (1994)(Psygnosis)

The automated real-image golden test downloads only the smaller Arabian Nights archive on demand, verifies the Archive.org MD5 before reuse, extracts track 1 to a plain 2048-byte data image, and skips cleanly if download or extraction tooling is unavailable. If a prepared data-track image already exists locally, set ODFS_REAL_AS_IMAGE=/path/to/arabian_nights.iso to reuse it without redownloading. The larger Benefactor image is kept as a manual reference input.

Building for AmigaOS

The Amiga handler is built with the amiga make target. The Makefile selects the Amiga frontend from the compiler target:

• m68k-amigaos-gcc builds the AmigaOS 3/classic handler
• ppc-amigaos-gcc builds the native AmigaOS 4 handler

AmigaOS 3

With an m68k AmigaOS cross-compiler in PATH, run:

make amiga

This uses m68k-amigaos-gcc by default and writes:

build/amiga/ODFileSystem

If the compiler is not in PATH, pass it explicitly:

make amiga CC=/path/to/m68k-amigaos-gcc

If the matching ar, size, and strip tools are also outside PATH, pass those too:

make amiga \
  CC=/path/to/m68k-amigaos-gcc \
  AMIGA_AR=/path/to/m68k-amigaos-ar \
  AMIGA_SIZE=/path/to/m68k-amigaos-size \
  STRIP=/path/to/m68k-amigaos-strip

To build the OS3 release archive, use:

make amigaos3-lha

This creates build/amiga/ODFileSystem.lha containing ODFileSystem, ODFileSystem-test, ODFileSystem-rom, ODFileSystem-rom-test, and README.md. The test ADF is built and released separately.

AmigaOS 4

With the AmigaOS 4 PPC toolchain in PATH, run:

make amiga CC=ppc-amigaos-gcc

This selects AMIGA_TARGET=os4 automatically and builds the native OS4 filesystem handler. To keep OS3 and OS4 outputs side by side, use a separate build directory:

make amiga \
  CC=ppc-amigaos-gcc \
  AMIGA_BUILD=build/amiga-os4

The handler is then written to:

build/amiga-os4/ODFileSystem

For OS4 builds the Makefile also writes a Kickstart-module form:

build/amiga-os4/CDFileSystem

These two files are intentionally different:

• ODFileSystem is the normal disk-loadable filesystem handler. Copy it to L:ODFileSystem and use it with a DOSDriver or mountlist.
• CDFileSystem is a relocatable Kickstart resident module. Use it when replacing Kickstart/CDFileSystem in an OS4 Kickstart directory or Kickstart.zip; the Kicklayout entry remains MODULE Kickstart/CDFileSystem.

If the OS4 toolchain is installed outside PATH, pass the full tool paths:

make amiga \
  CC=/opt/amiga-ppc/bin/ppc-amigaos-gcc \
  AMIGA_AR=/opt/amiga-ppc/bin/ppc-amigaos-ar \
  AMIGA_OBJCOPY=/opt/amiga-ppc/bin/ppc-amigaos-objcopy \
  AMIGA_SIZE=/opt/amiga-ppc/bin/ppc-amigaos-size \
  STRIP=/opt/amiga-ppc/bin/ppc-amigaos-strip \
  AMIGA_BUILD=build/amiga-os4

The Makefile normally derives the NDK include path from the selected compiler. If your SDK is elsewhere, add NDK_PATH=/path/to/include_h.

Debug and Size Limits

Release builds have serial logging disabled. For a test build with serial output enabled, use make amiga-test with the same toolchain selection:

make amiga-test
make amiga-test CC=ppc-amigaos-gcc AMIGA_TEST_BUILD=build/amiga-os4-test

The OS4 test build likewise produces both ODFileSystem and CDFileSystem under the selected test build directory.

To build the OS4 release archive, use:

make amigaos4-lha \
  CC=ppc-amigaos-gcc \
  AMIGA_BUILD=build/amiga-os4 \
  AMIGA_TEST_BUILD=build/amiga-os4-test

This creates build/amiga-os4/ODFileSystem-amigaos4.lha containing ODFileSystem-amigaos4, CDFileSystem, ODFileSystem-amigaos4-test, CDFileSystem-test, and README.md.

Release builds enforce a default size limit of 60000 bytes for OS3 and 131072 bytes for OS4. If intentional growth needs a higher ceiling, override it with AMIGA_SIZE_LIMIT=<bytes>. During local bring-up, the limit can be disabled with ENFORCE_SIZE_LIMITS=0.

Sample Mountlist

For the mountlist examples below, copy the built handler to L:ODFileSystem. With the default build directory that is build/amiga/ODFileSystem; if you set AMIGA_BUILD, use the corresponding ODFileSystem output from that directory.

For Workbench-style installation, copy:

• platform/amiga/dosdrivers/CD0 to DEVS:DOSDrivers/CD0
• platform/amiga/dosdrivers/CD0.info to DEVS:DOSDrivers/CD0.info

Change FileSystem in CD0 to L:ODFileSystem.

Then edit the Device and Unit tooltypes on the CD0 icon to match your hardware.

If you want a plain Mountlist entry instead, add one such as:

CD0:
    Handler   = L:ODFileSystem
    Stacksize = 8192
    Priority  = 5
    GlobVec   = -1
    DosType   = 0x43443031
    Device    = scsi.device
    Unit      = 2
    Flags     = 0
    Surfaces  = 1
    BlocksPerTrack = 1
    BlockSize = 2048
    Reserved  = 0
    LowCyl    = 0
    HighCyl   = 0
    Buffers   = 20
    BufMemType = 0
    Mount     = 1
    Activate  = 1
#

Optional handler control flags can be supplied through the mount entry control string, for example:

Control = "LOWERCASE UDF FILEBUFFERS=128"

Supported control flags:

• LOWERCASE to lowercase plain ISO names
• NOROCKRIDGE or NORR to disable Rock Ridge
• NOJOLIET or NOJ to disable Joliet
• HFSFIRST or HF to prefer HFS on hybrid discs
• UDF to prefer UDF on bridge discs
• FILEBUFFERS or FB to set the block-cache size

See mountlist.example for a fuller example with hardware notes, and CD0 for the packaged DOSDriver entry used with Workbench.

Unit Tests

Unit tests are host-side tests under tests/unit/. Run them with:

make check

This builds the host library and the unit-test binaries, then runs all suites. In this workspace, make check completes successfully.

The repository also contains image-based golden tests in tests/golden/, but the unit-test entry point is make check.

make golden-check also includes an optional real-world AS fixture test. It uses tests/golden/fetch_real_as_fixture.sh to cache and verify the small Arabian Nights archive locally before running the metadata assertions.

License

ODFileSystem is licensed under the BSD 2-Clause license. See LICENSE for the full text.