This is completely new to me and even after looking at the github page I didn't quite grasp what is so unique.
So I did a bit of searching:
I discovered sabotage distribution: https://github.com/sabotage-linux/sabotage
The concepts I like about it are:
- compiling the kernel without using perl (it was possible for few years).
- static link the core tools (busybox); less exposure to attacks, easier chroot/sandbox on the fly.
(would you like chroot from 64 bits into 32 bits, run sandboxed browser, or install 32 bits tcz aka syslinux)
- smaler auxiliar libs: (libnl-tiny?); libnl-tiny is known to work without issues with at least: iw, wpa-supplicant, kismet, aircrack-ng, libpcap
- simple package and build manager, ala archlinux pacman AUR repository; so both the core AND the tcz extensions could be scripted if you are security concerned about alien (not exposed) tcz recipes..
I like the freedom of (better) alternatives:
- to use llvm vs gcc (gcc is surviving because it is still the only one who can compile the full kernel)
- smaller C libs, like musl (not uclib) vs glibc.
- smaller core tools (like toybox vs busybox partial/total replacment ?). Imagine even a static compiled busybox (with musl) and part of tinycore rootfs64.gz is the same as rootfs32.gz, because any CPU (32/64 bits) can run same code. core.gz= commonFs.tools +libs.spec+ modules.
....Yesterday I decided to take time to play with
either FreeBSD or a minimalist Linux system. Luckily I decided to learn
more about Sabotage. What a joy! Clean scripts and deceptively simple
engineering! I put a clean ext4 filesystem on a partition as though I
were about to install Funtoo or Arch. I'm quite familiar with
installing those; but, Sabotage was faster and easier to install. MUCH
faster and easier. I executed your three scripts
butch install stage1 && butch install kernel
(that last one makes me smile -- installing a stage with that damned
simple package manager as if I were installing a single package).
In a very short time, mostly with the computer at the command prompt
waiting for me to return from the kitchen, I had a bootable linux system.
Well there was a small glitch. The root filesystem was mounted
read-only. Is that an artifact of the init system being different from
what I'm used to? Anyway, I added "rw" to root filesystem options in
/etc/fstab and "rw" to the kernel command line in my grub.cfg and
rebooted and all was well. In short order I was able to install xorg
and today I'm figuring out the init system (busybox init plus runit
services). I like the init design. Butch is great.
In between other things in the next week or so I'll try to replicate my
Funtoo desktop, fluxbox, rox-filer, mpv, and other things requiring gtk2
(and python). I would be interested in hearing if anyone has been able
to build kde applications on Sabotage(?). On Funtoo I build okular,
kate, kile, gwenview and calligra without avahi, consolekit, dbus,
policykit, or pulseaudio. It would be nice to do that on Sabotage.
Getting your questions answered here at ArchBang Forums
Please! Always give hardware info, if there is a chance that 's relevant: #lspci -vnn
On Arch(bang) and Openbox: http://stillstup.blogspot.com/