27 lines
2.0 KiB
Markdown
27 lines
2.0 KiB
Markdown
# FDS/OS user manual
|
|
|
|
FDS/OS runs a cartridge-based Linux computer. Start with the overview, then choose
|
|
the guide for building software, trying the emulator, or operating the machine.
|
|
Commands in workstation guides run on your Linux computer; commands in the
|
|
operating guides run at the FDS console unless stated otherwise.
|
|
|
|
| Guide | What you will learn |
|
|
| --- | --- |
|
|
| [Overview](../README.md) | How the computer, internal storage and cartridges fit together |
|
|
| [Run on a Raspberry Pi 5](hardware-setup.md) | Wire HDMI/USB/power, prepare NVMe and SYSTEM, reach the first console, calibrate bays and diagnose hardware |
|
|
| [Build and start FDS](getting-started.md) | Prepare the OS build workstation, create images and boot the emulator |
|
|
| [Software and emulator walkthrough](workstation.md) | Build Void source packages, assemble cartridges, insert them and write USB media |
|
|
| [Using cartridges](cartridges.md) | Inspect bays, run applications, resolve command names and eject safely |
|
|
| [DATA and files](data.md) | Use persistent storage and manage active DATA |
|
|
| [Desktop and control panel](desktop.md) | Open WindowMaker, manage cartridges graphically and customize the theme |
|
|
| [Software format](software-format.md) | Write source recipes and understand the installed-program image layout |
|
|
| [Internal storage](internal-storage.md) | Install boot/recovery storage and manage machine settings |
|
|
| [Recovery](recovery.md) | Inspect failed media and check or repair DATA |
|
|
| [Release verification](releases.md) | Verify downloaded images before use |
|
|
| [Dasung display](dasung.md) | Inspect and control the built-in Paperlike daemon |
|
|
| [Cleanup](cleanup.md) | Reclaim obsolete build output without losing current images or personal data |
|
|
| [Troubleshooting](troubleshooting.md) | Diagnose build, cartridge, desktop and emulator problems |
|
|
|
|
Implementation plans, dependency rationale, measurements, hardware procedures and
|
|
historical test results are maintained separately in [developer notes](developer/README.md).
|