Put a disk of your own in drive 1
make run-voyager and make run-cosmos now attach Disks/personal.img as the second drive. It is made the first time it is wanted and then left alone: a rule with no prerequisites, so make never looks at it again. NOT UNDER build/, and that is the whole point. Everything else in this repository is made from source and can be thrown away without losing anything, so 'clean' empties build/ without a thought - and a disk of your own that a clean deletes is not a disk of your own. It is the one place here where something MADE ON THE MACHINE can live, which starts to matter the moment there are tools on it that make things. Disks/ is in .gitignore for the same reason: what you make on the machine is yours and not the repository's. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW
This commit is contained in:
co-authored by
Claude Opus 5
parent
e4f4bae762
commit
3e48e9690d
@@ -142,6 +142,10 @@ make run-voyager
|
||||
`make` builds a disk as well as the tools, so there is one to boot. `make run-cosmos` is the
|
||||
same system in the terminal, for a machine with no graphics library.
|
||||
|
||||
Both put a second disk in drive 1, at `Disks/personal.img`. It is made once and then never
|
||||
rebuilt, cleaned or committed: everything else here can be thrown away and made again from
|
||||
source, and that one is where anything made ON the machine lives.
|
||||
|
||||
Then `dir` to see what is there, `load Snake.sbx` and `run` to play something, or `load Asm.sbx` and `run cosmos.asm` to watch the machine build itself.
|
||||
|
||||
Every source in `Programs/` is on that disk, under `/Source`, so anything not shipped as a
|
||||
|
||||
Reference in New Issue
Block a user