Table of Contents
include_toc
| include_toc |
|---|
| true |
Developer notes
This is the engineering side of FDS: how the pieces are built, why choices were made, and what we actually measured. The user manual describes how to use the current interfaces without the milestone history.
Current storage work is recorded in native SD migration validation. The earlier cartridge/desktop revision has separate acceptance, as does the frozen 0.1.0 release. Old test reports describe the inputs named in those reports; a changed source tree needs fresh checks.
Design and build references
Acceptance history
- clap-validation
- dasung-validation
- m0-validation
- m1-validation
- m10-validation
- m11-validation
- m12-validation
- m2-validation
- m3-validation
- m4-validation
- m5-validation
- m6-validation
- m7-validation
- m8-validation
- m9-validation
- workstation-validation
Earlier guides and working notes
These retain useful implementation details and the historical interfaces that went with them. Use the user manual for current commands, especially software cartridge creation: new payloads contain installed Void package trees.
FDS/OS
Start here
Use the computer
- Use cartridges and run programs
- DATA and persistent files
- WindowMaker and FDS Control
- Dasung Paperlike display
Install and maintain
- Flash disk images
- Internal storage and machine settings
- Pi 5 EEPROM configuration
- Recovery and rollback
- Verify a release
- Reclaim build space
- Troubleshooting
Build and contribute
Home · All pages · Edit the wiki · Source repository
Maintained directly in the fds-os.wiki repository. Historical acceptance applies only to the source and artifacts identified in each record.