I still have to produce the full image, but I’m still running the working image I built.
There is no major blocker, just I haven’t taken the time to build it and to figure out a better hosting situation. (Hosting it where my website/email/whatever live is fine but the upstream is bad so I’d have to throttle and my main hosting setup has metered bandwidth, so I will probably end up throwing it onto a Frantech slab.) In the mean time, I don’t know how easily people on this forum can get to a Tor server.
The plan is mostly to take take the kernel/bootloader/partition table from the official image, copy the kernel modules into /lib/modules, add all the packages (prebuilt packages available here, will figure out a method for hosting some bigger files: http://s3ldbb3l5eqd6tjsklzmxy6i47i3fim55fpxmgeaa6rvpcllkt4ci4yd.onion/a06/crux/ ), and do test-boots, debug it, etc., then remove the ssh keys (so new ones are created on startup), set the root password to something simple so that you can log in and create your user account. Basic nice stuff.
I have acquired a TuringPi 2 and some of their RK-1 boards, so I don’t need to use the qemu chroot any more: distccd lets them function as a small build farm, and their CPUs are similar enough (CPi’s A-06 is a RK3399, big.LITTLE 4/2, the TuringPi RK-1 uses an RK3588, which is dynamIQ and 4/4) that I actually used the DevTerm packages to build out the CRUX image for the RK-1. (I’m running it on a couple of headless CM-4s also, so I guess it’s also compatible, drivers aside.) I wish I had gotten one of them sooner (they had the same supply chain issues that Clockwork Pi had): it was painful trying to get the stupid qt6 stuff to build, but if I had a few nodes with excessive amounts of RAM, I wouldn’t have needed to do hacks.
It is just regular Linux, so the screenshots have more to do with what I am doing to the system than they do with what the system does, but I did like CPi’s amber setup so much that I cloned it on my R-01 Slackware image (They look orange in screenshots, but the bluish cast of the LCD makes them amber: Slackware image for DevTerm R01 .), and the view is a little more conventional on the A-06: running Firefox to view AwkiAwki ( GitHub - pete/awki: Awki is a lightweight wiki written in awk. These are my patches, original here: http://awkiawki.bogosoft.com/ ), dvtm in urxvt, cool-retro-term (power-hungry, I don’t use it too often), drawterm to edit code on the Plan 9 system (and in front of it, 9front’s vt(1), showing an ssh interface to a Pleroma instance), and trusty old xpdf showing “Coders at Work”.
