archlinux-installer-script VS mescc-tools-seed

I haven't installed it since ~2016/2017, so my knowledge might be outdated. If you use one of the arch-based distros with a GUI, then you're right that it's very easy to install.

If you follow the Wiki though, I think you still learn quite a bit: https://wiki.archlinux.org/title/installation_guide

This is right at the bottom of the installation guide (if you followed it and did not go the install script route). Regardless, it seems that arch is installed, now, either install a desktop environment (Gnome, KDE, XFCE, ... ) or a window manager ( i3, awesome, bspwm, herbstluftwm, ...) -> https://wiki.archlinux.org/title/General_recommendations#Graphical_user_interface.

I'm reading the installation guide. And I'm stick at section 1.2.

I started here https://wiki.archlinux.org/title/installation_guide

Stop following outdated YouTube tutorials and just use the installation guide on the Arch Wiki. All of the information needed is there.

From here I found a reference to the Gash, Mes-M2 and stage0 projects, who's README.org references a nice wiki for stage0. The Wiki references a more expansive stage0-posix repo. From here, I finally got all the pieces to fit togeather.

Of course, reproducible builds will only give you security if you trust the compiler you're using to verify. Unlike traditional distributions, Guix packages are rigorously defined in terms of their dependencies all the way down to ~60 MB of bootstrap binaries. There has been a lot of cool work to reduce the initial binary seed size, and they are working to reduce this even further to a "full source" bootstrap which will make use of the stage0 project to bootstrap the entire OS from a small, auditable ASCII Hex -> binary program.

stage0-posix just gained initial support for RISC-V (64-bit). It starts with 392 byte hex assembler, 361 byte "shell" and bootstraps simple linker (hex2), macro assembler (M0). Then it builds cc_riscv64 RISC-V compiler written in RISC-V assembly and uses it to build simple C compiler written in C (M2-Planet). Then it builds a few extra utilities (cp, mkdir, untar, ungz, sha256sum, chmod)

I wonder if Brainfuck could be used for https://github.com/oriansj/stage0-posix ? It would not surprise me if there is no other language for which there are so many interpreters written in so many different programming languages. It is even possible to write a Brainfuck interpreter in Brainfuck, which can be verified. And there is also a Brainfuck interpreter written in x86-64: https://github.com/316k/brainfuck-x86-64 . It is a little larger than hex0_x86.hex0 , but not too much to make it hard to verify.

I'd argue the easiest to implement language is macro-assembly then the C subset known as cc_x86

https://github.com/oriansj/mescc-tools-seed