The "Community Usage" column is a subjective rating of how heavily the given distro is used in Bedrock Linux community intended to provide a level of confidence in the "Known Issues" column's accuracy and recency.
|Linux Distro||Community Usage||Known Issues||Fetch Support||Maintainer|
|Arch Linux||Very High||None||Yes||paradigm|
|Clear Linux||Very Low||Many issues †||Unmaintained||N/A|
|CRUX||None||BSD-style SysV init †||Unmaintained||N/A|
|Elementary OS||Very Low||None||No||None|
|Exherbo||Medium||None||Yes||Wulf C. Krueger|
|Fedora Silverblue||None||Read-only root †||No||None|
|KISS||Very Low||Escapes restriction †||Unmaintained||None|
|Manjaro||Very Low||pamac/octopi †||Unmaintained||None|
|MX Linux||None||systemd-shim †||No||None|
|NixOS||Very Low||many †||No||None|
|OpenSUSE||Very Low||defaults to grub+btrfs †||No||None|
|Slackware||Low||BSD-style SysV init †||Unmaintained||None|
|Solus||Very Low||stateless †||Unmaintained||None|
|Void Linux||Very High||None||Yes||paradigm|
One effort to add
brl fetch support involved bootstrapping via the
Nix package manager, which itself was installed via
Nix apparently disliked running in
brl fetch environment. This might be related to Nix sandboxing
efforts. More investigation is needed.
Nix requires a runtime daemon. Proper support for NixOS might require
enable support for pre/post enable hooks to launch the daemon when the
It is unclear if NixOS design assumptions will result in it becoming upset at
non-local components, such as
/etc files, changing out from under it.
Solus's "stateless" concept means it does not create various files in
/etc Bedrock expects. This might be done to avoid fighting with users
/etc file changes.
Solus does provide default versions of these files, but outside of
/etc. The expectation might be that the user copies them over at his/her
This is likely removable with adequate effort. Bedrock could be configured
to understand this concept via
bedrock.conf lists of stateless copy
locations. If the required file is missing but another location has it,
Bedrock would then copy it over when
Clear Linux also calls itself "stateless." Efforts here should be tested against Clear as well.
KISS Linux's package manager,
kiss, detects available executables on-the-fly
rather than via its own dependency and package availability management.
Consequently, it must be restricted to avoid accidentally jumping across
strata. As of 0.7.16, Bedrock's default/recommended configuration restricts
kiss may call
sudo under-the-hood. At the time of writing, using
Bedrock escapes restriction, as using
sudo resets the
conditionally checking if the new
$PATH should be restricted or not. This
may result in Bedrock-specific error messages when using
To properly support KISS Linux, Bedrock's
sudo restriction escape hole should
Fedora Silverblue uses a read-only root by default, which keeps the hijack
installer from being able to do things like extract
/bedrock onto the root
directory. Investigation needs to be done to understand the ramifications of
simply remounting the root directory read-write for the duration of the
install. Silverblue's non-traditional nature will likely raise other issues as
Guix is similar to NixOS, but the init in here is not
which gave hope about having NixOS-like configuration of systems on non-systemd distros.
hijack process is not working, because of design assumptions of Guix.
Neither did an attempt to use
Guix binaries to fetch what's needed.
More investigation is needed.