lbailly/liminix
1
0
Fork 0
forked from DGNum/liminix
Code Pull requests 2 Activity Actions

thinking

Browse source
This commit is contained in:
Daniel Barlow 2023-02-10 16:43:06 +00:00
parent a7c94f5a12
commit 6be459b9ac
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
THOUGHTS.txt
View file

@ -481,3 +481,23 @@ Actual Documentation (e.g. user and developer manuals) should live in
the liminix repo so it corresponds with the code, and can be rsynced the liminix repo so it corresponds with the code, and can be rsynced
from there to the web site, maybe with a deploy hook or something. from there to the web site, maybe with a deploy hook or something.
Haven't decided what a good doc format is yet Haven't decided what a good doc format is yet
If we create a flake for Hydra to run on, that _more or less_ means we
don't have any manual hydra jobset configuration to document.
There are still some tests that need adding to CI
Should the per-device config be a module not an overlay? Given that
half of what's in it is kernel config (a module could set this)
and the rest is source tarball download specs (needs nixpkgs,
a module has this and could set it too) I wonder why it isn't already
Can we make Hydra report output sizes so we can plot closure size
trends and see if it all goes awful?
Thu Feb 9 08:14:39 GMT 2023
For better developer experience, I am thinking that either (1)
swap tasks 2 and 3 (writable filesystem before module system)
or (2) add NBD support so I can iterate on a real device without
full rebuilds every time