kreato-release is a release file on /etc. It is like os-release in functionality. It allows any software to see how the Kreato Linux system is configured. It uses an ini-like format, like kpkg configuration files and the retained krep rootfs configuration format. Example [General] dateBuilt=2023-05-15 klinuxVersion=rolling srcCommit=4691104 [Core] libc=glibc compiler=gcc coreutils=busybox tlsLibrary=openssl init=jumpstart [Extras] extraPackages=nim llvm mesa Options General dateBuilt: Shows the date the system has been built. Follows YYYY-MM-DD format. klinuxVersion: Shows Kreato Linux version the system is meant to run. rolling by default. srcCommit: Shows Kreato Linux source tree commit the system has been built with. Does not include kpkg included in the system. Core/Extras Core and Extras reflect the configuration used by krep rootfs. See kreastrap.conf(5) for the retained INI format.

Kreato Linux was started in 2022, mainly because i was fed up with other Linux distributions. It had a POSIX sh base (nyaa, the package manager was written in POSIX sh) with a bit of C at the start (nyaa-src was built in C, which was for building the rootfs). I killed out nyaa-src pretty quick because of it not utilizing the package manager nyaa, which was a big issue. The another reason was the code being a mess, and was full of shell commands anyway. It was good for a first try atleast, it gave me something that was working.

krep iso builds a live ISO from a trusted rootfs directory or tar archive. It replaces KreaISO and is not restricted to systemd. Assembly copies the input into a private workspace and does not modify it. It uses no mounts, loop devices, host package installs, or host kernel assets. Linux and root privileges are still required to preserve ownership and device nodes. Build and run Build krep as described in the rootfs guide, then run it on a prepared Linux host: