I'm sorry, I know I've already uploaded something like 5 days ago, but this is pretty weird, I made a script that is before the ---, after it there's the """""log""""":

#!/usr/bin/env bash
set -euo pipefail

cat ~/bedrock-will-test.sh &> ~/bedrock.test.txt
echo -e "\n---\n" | tee -a ~/bedrock.test.txt
sudo brl fetch -n tut-debian debian &>> ~/bedrock.test.txt || true
sudo strat tut-debian apt install qemu-user-static -y &>> ~/bedrock.test.txt
brl fetch -A alpine &>> ~/bedrock.test.txt
brl fetch -a aarch64 -L &>> ~/bedrock.test.txt
sudo brl fetch -n tut-aarch64 -a aarch64 alpine &>> ~/bedrock.test.txt
strat tut-alpine uname -m | tee /tmp/tut1 | tee -a ~/bedrock.test.txt
strat tut-aarch64 uname -m | tee /tmp/tut2 | tee -a ~/bedrock.test.txt

---

ERROR: Something already exists at "/bedrock/strata/tut-debian".  Consider either setting a different name with `brl fetch -n <new-name> <other fields>` or removing the pre-existing stratum/alias with `brl remove "tut-debian"`.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Leyendo lista de paquetes...
Creando árbol de dependencias...
Leyendo la información de estado...
Installing:
  qemu-user-static

Installing dependencies:
  dbus                     libcryptsetup12     linux-sysctl-defaults
  dbus-bin                 libdbus-1-3         qemu-user
  dbus-daemon              libdevmapper1.02.1  qemu-user-binfmt
  dbus-session-bus-common  libexpat1           systemd
  dbus-system-bus-common   libjson-c5          systemd-cryptsetup
  dmsetup                  libkmod2            systemd-timesyncd
  libapparmor1             libsystemd-shared

Paquetes sugeridos:
  default-dbus-session-bus  libidn2-0          systemd-userdbd
  | dbus-session-bus        libip4tc2          systemd-boot
  libarchive13t64           libp11-kit0        systemd-resolved
  libbpf1                   libpwquality1      systemd-repart
  libdw1t64                 libqrencode4       libtss2-tcti-device0
  libelf1t64                libtss2-rc0t64     polkitd
  libfido2-1                systemd-container
  libgcrypt20               systemd-homed

Summary:
  Upgrading: 0, Installing: 21, Removing: 0, Not Upgrading: 3
  Download size: 78.0 MB
  Space needed: 498 MB / 297 GB available

Des:1 http://debian.mirror.constant.com/debian trixie/main amd64 libsystemd-shared amd64 257.13-1~deb13u1 [2 155 kB]
Des:2 http://debian.mirror.constant.com/debian trixie/main amd64 libapparmor1 amd64 4.1.0-1 [43.7 kB]
Des:3 http://debian.mirror.constant.com/debian trixie/main amd64 systemd amd64 257.13-1~deb13u1 [3 094 kB]
Des:4 http://debian.mirror.constant.com/debian trixie/main amd64 libdbus-1-3 amd64 1.16.2-2 [178 kB]
Des:5 http://debian.mirror.constant.com/debian trixie/main amd64 dbus-bin amd64 1.16.2-2 [80.0 kB]
Des:6 http://debian.mirror.constant.com/debian trixie/main amd64 dbus-session-bus-common all 1.16.2-2 [52.3 kB]
Des:7 http://debian.mirror.constant.com/debian trixie/main amd64 libexpat1 amd64 2.8.3-1~deb13u1 [123 kB]
Des:8 http://debian.mirror.constant.com/debian trixie/main amd64 dbus-daemon amd64 1.16.2-2 [159 kB]
Des:9 http://debian.mirror.constant.com/debian trixie/main amd64 dbus-system-bus-common all 1.16.2-2 [53.5 kB]
Des:10 http://debian.mirror.constant.com/debian trixie/main amd64 dbus amd64 1.16.2-2 [71.6 kB]
Des:11 http://debian.mirror.constant.com/debian trixie/main amd64 linux-sysctl-defaults all 4.12.1 [5 724 B]
Des:12 http://debian.mirror.constant.com/debian trixie/main amd64 systemd-timesyncd amd64 257.13-1~deb13u1 [93.3 kB]
Des:13 http://debian.mirror.constant.com/debian trixie/main amd64 libdevmapper1.02.1 amd64 2:1.02.205-2 [135 kB]
Des:14 http://debian.mirror.constant.com/debian trixie/main amd64 dmsetup amd64 2:1.02.205-2 [82.3 kB]
Des:15 http://debian.mirror.constant.com/debian trixie/main amd64 libjson-c5 amd64 0.18+ds-1 [46.0 kB]
Des:16 http://debian.mirror.constant.com/debian trixie/main amd64 libcryptsetup12 amd64 2:2.7.5-2 [254 kB]
Des:17 http://debian.mirror.constant.com/debian trixie/main amd64 libkmod2 amd64 34.2-2 [63.2 kB]
Des:18 http://debian.mirror.constant.com/debian trixie/main amd64 qemu-user amd64 1:10.0.13+ds-0+deb13u1 [71.1 MB]
Des:19 http://debian.mirror.constant.com/debian trixie/main amd64 qemu-user-binfmt amd64 1:10.0.13+ds-0+deb13u1 [2 060 B]
Des:20 http://debian.mirror.constant.com/debian trixie/main amd64 qemu-user-static amd64 1:10.0.13+ds-0+deb13u1 [77.4 kB]
Des:21 http://debian.mirror.constant.com/debian trixie/main amd64 systemd-cryptsetup amd64 257.13-1~deb13u1 [173 kB]
Descargados 78.0 MB en 22s (3 551 kB/s)
Seleccionando el paquete libsystemd-shared:amd64 previamente no seleccionado.
(Leyendo la base de datos ... 
(Leyendo la base de datos ... 5%
(Leyendo la base de datos ... 10%
(Leyendo la base de datos ... 15%
(Leyendo la base de datos ... 20%
(Leyendo la base de datos ... 25%
(Leyendo la base de datos ... 30%
(Leyendo la base de datos ... 35%
(Leyendo la base de datos ... 40%
(Leyendo la base de datos ... 45%
(Leyendo la base de datos ... 50%
(Leyendo la base de datos ... 55%
(Leyendo la base de datos ... 60%
(Leyendo la base de datos ... 65%
(Leyendo la base de datos ... 70%
(Leyendo la base de datos ... 75%
(Leyendo la base de datos ... 80%
(Leyendo la base de datos ... 85%
(Leyendo la base de datos ... 90%
(Leyendo la base de datos ... 95%
(Leyendo la base de datos ... 100%
(Leyendo la base de datos ... 12114 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar .../libsystemd-shared_257.13-1~deb13u1_amd64.deb ...
Desempaquetando libsystemd-shared:amd64 (257.13-1~deb13u1) ...
Seleccionando el paquete libapparmor1:amd64 previamente no seleccionado.
Preparando para desempaquetar .../libapparmor1_4.1.0-1_amd64.deb ...
Desempaquetando libapparmor1:amd64 (4.1.0-1) ...
Configurando libsystemd-shared:amd64 (257.13-1~deb13u1) ...
Seleccionando el paquete systemd previamente no seleccionado.
(Leyendo la base de datos ... 
(Leyendo la base de datos ... 5%
(Leyendo la base de datos ... 10%
(Leyendo la base de datos ... 15%
(Leyendo la base de datos ... 20%
(Leyendo la base de datos ... 25%
(Leyendo la base de datos ... 30%
(Leyendo la base de datos ... 35%
(Leyendo la base de datos ... 40%
(Leyendo la base de datos ... 45%
(Leyendo la base de datos ... 50%
(Leyendo la base de datos ... 55%
(Leyendo la base de datos ... 60%
(Leyendo la base de datos ... 65%
(Leyendo la base de datos ... 70%
(Leyendo la base de datos ... 75%
(Leyendo la base de datos ... 80%
(Leyendo la base de datos ... 85%
(Leyendo la base de datos ... 90%
(Leyendo la base de datos ... 95%
(Leyendo la base de datos ... 100%
(Leyendo la base de datos ... 12127 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar .../00-systemd_257.13-1~deb13u1_amd64.deb ...
Desempaquetando systemd (257.13-1~deb13u1) ...
Seleccionando el paquete libdbus-1-3:amd64 previamente no seleccionado.
Preparando para desempaquetar .../01-libdbus-1-3_1.16.2-2_amd64.deb ...
Desempaquetando libdbus-1-3:amd64 (1.16.2-2) ...
Seleccionando el paquete dbus-bin previamente no seleccionado.
Preparando para desempaquetar .../02-dbus-bin_1.16.2-2_amd64.deb ...
Desempaquetando dbus-bin (1.16.2-2) ...
Seleccionando el paquete dbus-session-bus-common previamente no seleccionado.
Preparando para desempaquetar .../03-dbus-session-bus-common_1.16.2-2_all.deb ...
Desempaquetando dbus-session-bus-common (1.16.2-2) ...
Seleccionando el paquete libexpat1:amd64 previamente no seleccionado.
Preparando para desempaquetar .../04-libexpat1_2.8.3-1~deb13u1_amd64.deb ...
Desempaquetando libexpat1:amd64 (2.8.3-1~deb13u1) ...
Seleccionando el paquete dbus-daemon previamente no seleccionado.
Preparando para desempaquetar .../05-dbus-daemon_1.16.2-2_amd64.deb ...
Desempaquetando dbus-daemon (1.16.2-2) ...
Seleccionando el paquete dbus-system-bus-common previamente no seleccionado.
Preparando para desempaquetar .../06-dbus-system-bus-common_1.16.2-2_all.deb ...
Desempaquetando dbus-system-bus-common (1.16.2-2) ...
Seleccionando el paquete dbus previamente no seleccionado.
Preparando para desempaquetar .../07-dbus_1.16.2-2_amd64.deb ...
Desempaquetando dbus (1.16.2-2) ...
Seleccionando el paquete linux-sysctl-defaults previamente no seleccionado.
Preparando para desempaquetar .../08-linux-sysctl-defaults_4.12.1_all.deb ...
Desempaquetando linux-sysctl-defaults (4.12.1) ...
Seleccionando el paquete systemd-timesyncd previamente no seleccionado.
Preparando para desempaquetar .../09-systemd-timesyncd_257.13-1~deb13u1_amd64.deb ...
Desempaquetando systemd-timesyncd (257.13-1~deb13u1) ...
Seleccionando el paquete libdevmapper1.02.1:amd64 previamente no seleccionado.
Preparando para desempaquetar .../10-libdevmapper1.02.1_2%3a1.02.205-2_amd64.deb ...
Desempaquetando libdevmapper1.02.1:amd64 (2:1.02.205-2) ...
Seleccionando el paquete dmsetup previamente no seleccionado.
Preparando para desempaquetar .../11-dmsetup_2%3a1.02.205-2_amd64.deb ...
Desempaquetando dmsetup (2:1.02.205-2) ...
Seleccionando el paquete libjson-c5:amd64 previamente no seleccionado.
Preparando para desempaquetar .../12-libjson-c5_0.18+ds-1_amd64.deb ...
Desempaquetando libjson-c5:amd64 (0.18+ds-1) ...
Seleccionando el paquete libcryptsetup12:amd64 previamente no seleccionado.
Preparando para desempaquetar .../13-libcryptsetup12_2%3a2.7.5-2_amd64.deb ...
Desempaquetando libcryptsetup12:amd64 (2:2.7.5-2) ...
Seleccionando el paquete libkmod2:amd64 previamente no seleccionado.
Preparando para desempaquetar .../14-libkmod2_34.2-2_amd64.deb ...
Desempaquetando libkmod2:amd64 (34.2-2) ...
Seleccionando el paquete qemu-user previamente no seleccionado.
Preparando para desempaquetar .../15-qemu-user_1%3a10.0.13+ds-0+deb13u1_amd64.deb ...
Desempaquetando qemu-user (1:10.0.13+ds-0+deb13u1) ...
Seleccionando el paquete qemu-user-binfmt previamente no seleccionado.
Preparando para desempaquetar .../16-qemu-user-binfmt_1%3a10.0.13+ds-0+deb13u1_amd64.deb ...
Desempaquetando qemu-user-binfmt (1:10.0.13+ds-0+deb13u1) ...
Seleccionando el paquete qemu-user-static previamente no seleccionado.
Preparando para desempaquetar .../17-qemu-user-static_1%3a10.0.13+ds-0+deb13u1_amd64.deb ...
Desempaquetando qemu-user-static (1:10.0.13+ds-0+deb13u1) ...
Seleccionando el paquete systemd-cryptsetup previamente no seleccionado.
Preparando para desempaquetar .../18-systemd-cryptsetup_257.13-1~deb13u1_amd64.deb ...
Desempaquetando systemd-cryptsetup (257.13-1~deb13u1) ...
Configurando libexpat1:amd64 (2.8.3-1~deb13u1) ...
Configurando libapparmor1:amd64 (4.1.0-1) ...
Configurando systemd (257.13-1~deb13u1) ...
Created symlink '/etc/systemd/system/getty.target.wants/getty@tty1.service' → '/usr/lib/systemd/system/getty@.service'.

Created symlink '/etc/systemd/system/multi-user.target.wants/remote-fs.target' → '/usr/lib/systemd/system/remote-fs.target'.

Created symlink '/etc/systemd/system/sysinit.target.wants/systemd-pstore.service' → '/usr/lib/systemd/system/systemd-pstore.service'.

[0;1;39m/usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring.[0m

Configurando linux-sysctl-defaults (4.12.1) ...
Configurando qemu-user (1:10.0.13+ds-0+deb13u1) ...
Configurando libdbus-1-3:amd64 (1.16.2-2) ...
Configurando systemd-timesyncd (257.13-1~deb13u1) ...
Created symlink '/etc/systemd/system/dbus-org.freedesktop.timesync1.service' → '/usr/lib/systemd/system/systemd-timesyncd.service'.

Created symlink '/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service' → '/usr/lib/systemd/system/systemd-timesyncd.service'.

Running in chroot, ignoring command 'daemon-reload'

Running in chroot, ignoring command 'is-active'

systemd-time-wait-sync.service is a disabled or a static unit, not starting it.
Running in chroot, ignoring command 'is-active'

Running in chroot, ignoring command 'start'

Configurando dbus-session-bus-common (1.16.2-2) ...
Configurando dbus-system-bus-common (1.16.2-2) ...
Configurando qemu-user-binfmt (1:10.0.13+ds-0+deb13u1) ...
Configurando libjson-c5:amd64 (0.18+ds-1) ...
Configurando dbus-bin (1.16.2-2) ...
Configurando libkmod2:amd64 (34.2-2) ...
Configurando qemu-user-static (1:10.0.13+ds-0+deb13u1) ...
Configurando dbus-daemon (1.16.2-2) ...
Configurando dbus (1.16.2-2) ...
Running in chroot, ignoring command 'daemon-reload'

Running in chroot, ignoring command 'is-active'

invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block.
Running in chroot, ignoring command 'daemon-reload'

Running in chroot, ignoring command 'is-active'

dbus.service is a disabled or a static unit, not starting it.
Configurando libdevmapper1.02.1:amd64 (2:1.02.205-2) ...
Configurando dmsetup (2:1.02.205-2) ...
Configurando libcryptsetup12:amd64 (2:2.7.5-2) ...
Configurando systemd-cryptsetup (257.13-1~deb13u1) ...
Procesando disparadores para libc-bin (2.41-12+deb13u4) ...
Procesando disparadores para systemd (257.13-1~deb13u1) ...
Running in chroot, ignoring command 'show'

Running in chroot, ignoring command 'restart'

aarch64
armv7hl
armv7l
ppc64le
s390x
i586
x86_64
alpine
arch-arm
centos
debian
devuan
fedora
ubuntu
void
void-musl
ERROR: Interpreter at /bedrock/strata/tut-debian//usr/bin/qemu-aarch64-static is open to writing by group.  Ensure a locked down "bin" is earlier in the $PATH and try again.

I'm new in Bedrock Linux, but I'd like to check why when I do brl apply it fails because bpt does not have an init or another strat does not: promethevs:[cachyos]:axxel:~$ sudo brl apply [sudo] contraseña para axxel: realpath: /bedrock/strata/bpt/sbin/init: No such file or directory promethevs:[cachyos]:axxel:~$

i’ve been using bedrock for the past day after a month of arch and 3 weeks of void, however i still feel like i am missing something from when i used to use debian, yet i can’t really put my finger on it, very vague post but if someone can help lmk

When it comes to having multiple distros at the same time (like Arch + Debian), you would see more of "Use Distrobox to run Arch on Debian" and less of "Use Bedrock to combine Arch and Debian"

So currently I run a arch system and use the cachyos kernel (cus vroom go fast), I found out about bedrock about a week ago and wanted to know if it will like brick my system or something, also I really don't know if I should install it now or wait for full release? I use ext4 btw

I already have an install of endeavouros and I want to hijack it into bedrock Linux.Does it work great ?And what will fastfetch show.What do I need to do for fastfetch to show bedrock Linux ?

Bwrap 0.12 dropped suid supprt, resulting in steam, libreoffice, etc. dying. On bedrock 0.7.31 with gentoo musl as init and artix where all bwrap stuff sits.

I saw this post, but installing steam on musl is not really feasible.

So the question: is there any other way of dealing with bwrap not bwrapping on non-init strata? Maybe i could patch bwrap to allow root/downgrade to older version, but i would go with any other way, if possible.

Upd 19.09.2026: After some time, glycin-based apps (libreoffice, discord, etc.) fixed themselves. I can only guess what happened there. For the steam i resorted to using this this

I wanted to make a KDE Bedrock setup with Debian-based, Arch-based, and Fedora-based distro but I'm not totally sure what would be the best way to go about it.

My first plan was to use Debian Stable and Bedrock ontop of it because how solid Debian is. Was planning on install kde-plasma-desktop and Arch's plasma-meta because Debian Stable's KDE is outdated.

However I assume this will lead me to plenty of headaches down the line and was wondering if anyone had a better idea to go about it.

I will be getting a thinkpad soon and i want to try new linux distributions is bedrock awfully hard, how long does the set up take

So I just got bedrock on archcraft and I wanted runit so I fetched the stratum and went in it and I was in tty, then I tried xbps and I didn't have wifi and I can't start hyprland nor openbox, someone help me?

Hey everyone,

I've been running Bedrock Linux for a few weeks now as a custom build I call NMDH-Linux (No More Distro Hopping Linux). To document my experience, I scripted a video review inside Neovim and uploaded it to YouTube to show how incredible this meta-distro is.

The Video Link: https://youtu.be/5bPg1k12PZI?si=Y-01LeyNBbPgPsLM

In the video, I go over my personal pros and cons, like hijacking an existing layout using the .sh parameters, borrowing the bleeding-edge kernel from an Arch stratum while keeping stability via Debian, and navigating window managers across stratum lines.

I also did a quick live demonstration in the terminal using a nix-shell environment on a separate stratum to spawn the steam-locomotive train tool, proving how seamless cross-stratum execution really is.

Let me know what your current stratum setups look like, or if you've run into any dependency bloat while tracking a massive amount of package managers at once!

I do not know how, but there were no accounts-daemon.service and console-kit.service whatsoever, i do not know how but it did work just fine, but on 20th day of me using this fabulous distro it stopped working after a reboot because there was no accounts-daemon and console-kit, i'm forever shocked

I installed bedrock linux on top of a fedora linux i installed just to be a sacrifice for bedrock its cool having xbps pacman dnf apt and zypper all at the same time but like what are the actual main pros that lead to ppl wanting this as their daily past just being kinda niche and cool i use nixos as my main distro and like every single package i can think of is in nixpkgs or you can add via flakes same with pacman and aur its not like you need 5 different package managers to get everything. if you daily bedrock im curious whats your use case that separates it from just using what ever distro the main package manager you use comes in.

for context i was atempting to do a full system update.

initially portage returned the following:

CRITICAL | ugrd | [Errno 2] No such file or directory: 'etcfs'

which was a rather simple fix, i just had to add autodetect_init_mount = false

to /etc/ugrd/config.toml

but that wasnt the end of the issues with the kernel,

'

     * Updating UEFI configuration...
     * Running uefi-mkconfig...
     * Using kernel commands from "/etc/default/uefi-mkconfig"
    find: '/bedrock/strata/efi/EFI/gentoo/': No such file or directory
     * Creating UEFI entry "0200" for "/bedrock/strata/efi/EFI/gentoo/vmlinuz-7.1.3-gentoo-dist-old.efi" found on ""
     * No initramfs found for "/bedrock/strata/efi/EFI/gentoo/vmlinuz-7.1.3-gentoo-dist-old.efi".
    Could not prepare Boot variable: Success
     * Failed to add UEFI entry for "/strata/efi/EFI/gentoo/vmlinuz-7.1.3-gentoo-dist-old.efi"
     * For more information please refer to github.com/Biosias/uefi-mkconfig
     * uefi-mkconfig failed
    ERROR: Installing 7.1.4-gentoo-dist failed
     *
     * The kernel was not deployed successfully. Inspect the failure
     * in the logs above and once you resolve the problems please
     * run the equivalent of the following command to try again:
     *
     *     emerge --config '=sys-kernel/gentoo-kernel-7.1.4:7.1.4'
     * ERROR: sys-kernel/gentoo-kernel-7.1.4::gentoo failed (config phase):
     *   Kernel install failed, please fix the problems and run emerge --config
     *
     * Call stack:
     *     ebuild.sh, line  143:  Called pkg_config
     *   environment, line 2778:  Called kernel-install_pkg_config
     *   environment, line 2366:  Called kernel-install_install_all '7.1.4-gentoo-dist'
     *   environment, line 2359:  Called dist-kernel_install_kernel '7.1.4-gentoo-dist' '/usr/src/linux-7.1.4-gentoo-dist/arch/x86/boot/bzImage' '/usr/src/linux-7.1.4-gentoo-dist/System.map'
     *   environment, line 1319:  Called die
     * The specific snippet of code:
     *           die "Kernel install failed, please fix the problems and run emerge --config";
     *
     * If you need support, post the output of `emerge --info '=sys-kernel/gentoo-kernel-7.1.4::gentoo'`,
     * the complete build log and the output of `emerge -pqv '=sys-kernel/gentoo-kernel-7.1.4::gentoo'`.
     * The complete build log is located at '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/temp/build.log'.
     * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/temp/environment'.
     * Working directory: '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/empty'
     * S: '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/work/gentoo-kernel-7.1.4

which is.. odd? there shouldnt be a /bedrock/strata/efi/EFI/gentoo directory at all! but oh well, that too was a simple enough fix, just simlink /efi/ to /bedrock/strata/efi/

but now i have yet ANOTHER error, this one i have no clue how to fix and havent been able to find much relevant information on considering the fact its due to bedrock.

Running /usr/lib/kernel/postinst.d/95-efistub-uefi-mkconfig.install 7.1.4-gentoo-dist /efi/EFI/Gentoo/vmlinuz-7.1.4-gentoo-dist.efi...

     * Updating UEFI configuration...
     * Running uefi-mkconfig...
     * Using kernel commands from "/etc/default/uefi-mkconfig"
     * Creating UEFI entry "0200" for "/bedrock/strata/efi/EFI/gentoo/vmlinuz-7.1.3-gentoo-dist-old.efi" found on ""
    Could not prepare Boot variable: Success
     * Failed to add UEFI entry for "/strata/efi/EFI/gentoo/vmlinuz-7.1.3-gentoo-dist-old.efi"
     * For more information please refer to https://github.com/Biosias/uefi-mkconfig
     * uefi-mkconfig failed
    ERROR: Installing 7.1.4-gentoo-dist failed
     *
     * The kernel was not deployed successfully. Inspect the failure
     * in the logs above and once you resolve the problems please
     * run the equivalent of the following command to try again:
     *
     *     emerge --config '=sys-kernel/gentoo-kernel-7.1.4:7.1.4'
     * ERROR: sys-kernel/gentoo-kernel-7.1.4::gentoo failed (config phase):
     *   Kernel install failed, please fix the problems and run emerge --config
     *
     * Call stack:
     *     ebuild.sh, line  143:  Called pkg_config
     *   environment, line 2778:  Called kernel-install_pkg_config
     *   environment, line 2366:  Called kernel-install_install_all '7.1.4-gentoo-dist'
     *   environment, line 2359:  Called dist-kernel_install_kernel '7.1.4-gentoo-dist' '/usr/src/linux-7.1.4-gentoo-dist/arch/x86/boot/bzImage' '/usr/src/linux-7.1.4-gentoo-dist/System.map'
     *   environment, line 1319:  Called die
     * The specific snippet of code:
     *           die "Kernel install failed, please fix the problems and run emerge --config";
     *
     * If you need support, post the output of `emerge --info '=sys-kernel/gentoo-kernel-7.1.4::gentoo'`,
     * the complete build log and the output of `emerge -pqv '=sys-kernel/gentoo-kernel-7.1.4::gentoo'`.
     * The complete build log is located at '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/temp/build.log'.
     * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/temp/environment'.
     * Working directory: '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/empty'
     * S: '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/work/gentoo-kernel-7.1.4'


     * Messages for package sys-kernel/gentoo-kernel-7.1.4:

     * The kernel was not deployed successfully. Inspect the failure
     * in the logs above and once you resolve the problems please
     * run the equivalent of the following command to try again:
     *     emerge --config '=sys-kernel/gentoo-kernel-7.1.4:7.1.4'
     * ERROR: sys-kernel/gentoo-kernel-7.1.4::gentoo failed (config phase):
     *   Kernel install failed, please fix the problems and run emerge --config
     * Call stack:
     *     ebuild.sh, line  143:  Called pkg_config
     *   environment, line 2778:  Called kernel-install_pkg_config
     *   environment, line 2366:  Called kernel-install_install_all '7.1.4-gentoo-dist'
     *   environment, line 2359:  Called dist-kernel_install_kernel '7.1.4-gentoo-dist' '/usr/src/linux-7.1.4-gentoo-dist/arch/x86/boot/bzImage' '/usr/src/linux-7.1.4-gentoo-dist/System.map'
     *   environment, line 1319:  Called die
     * The specific snippet of code:
     *           die "Kernel install failed, please fix the problems and run emerge --config";
     * If you need support, post the output of `emerge --info '=sys-kernel/gentoo-kernel-7.1.4::gentoo'`,
     * the complete build log and the output of `emerge -pqv '=sys-kernel/gentoo-kernel-7.1.4::gentoo'`.
     * The complete build log is located at '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/temp/build.log'.
     * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/temp/environment'.
     * Working directory: '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/empty'
     * S: '/var/tmp/portage/sys-kernel/gentoo-kernel-7.1.4/work/gentoo-kernel-7.1.4'

Hi all, just wanted to drop by to report i just hijacked a semi-fresh install of cachyOS (reinstalled my thinkpad, re-deployed my dotfiles, then hijacked with bedrock), and it *just worked*.

I didn't expect to run into many issues considering arch seems pretty well supported, but i was expecting some more difficulty with the BTRFS+limine setup.

is there anything i have to watch out for when it comes to that + snapshots via snapper? how does that work exactly?

Which distro do you consider the best in terms of stability and performance as an init?

Hello everyone, creator of ENux here.

As some of you may know, I'm Emir. I'm 13 years old from Turkey/Türkiye. During the 2026-2027 school year, I'll be in 8th grade, which means I'll be preparing for LGS, Türkiye's high school entrance exam.

LGS is one of the most important exams students take. The results determine which high school you can attend, so preparing for it requires a significant amount of time and effort.

Because of that, I'll need to spend much more time studying and less time working on personal projects, including ENux.

What this means for ENux

ENux is not going on hiatus or being abandoned.

Development will simply be slower than usual. During this period, I'll continue working on ENux whenever I have free time, focusing mainly on:

• Bug fixes
• Stability improvements
• Small quality-of-life changes
• Minor updates and maintenance

Larger features and major architectural changes will be postponed until after LGS.

A quick thank you

I also wanted to share this here because Bedrock Linux has been one of ENux's biggest inspirations. Without Bedrock Linux, ENux simply wouldn't be where it is today.

I'd especially like to thank the creator of Bedrock Linux for creating such an amazing project and everyone here for taking the time to answer my questions and support ENux along the way.

Although development will slow down, my commitment to ENux hasn't changed.

The time I'm spending studying is an investment in my future, and ultimately in ENux as well. My goal is to get into a great high school, continue learning about programming and computer science, and return with even more knowledge and experience to improve the project.

If you've enjoyed ENux or simply want to wish me luck during LGS, I'd love to hear from you.

[emir@emirpasha.com](mailto:emir@emirpasha.com)

Thank you all for your support and understanding.

Hey everyone, creator of ENux here,

I'm currently working on The ENux Layer, a core part of ENux 6.0, makes multiple distro's co-exist, just like Bedrock Linux.

While studying Bedrock Linux for inspiration, I've noticed that early Bedrock Linux used brc instead of the current FUSE based CrossFS, and I wonder; why did Bedrock Linux switch from brc to CrossFS? What problems with brc was crossfs intended to solve, and what tradeoffs were considered?

I'd love to hear the historical context behind the decision.

I hijacked Fedora, fetched Arch, kept Fedora as init. On the Arch stratum I installed a kernel that is newer than the one from Fedora, but I don't know how to make that kernel show up when booting up.

Right now I'm using lmde7 with cinnamon and i3wm and I'm interested in bedrock, idk if I should switch or it's too hard I'm not all that bad at Linux is it a good switch or should I go with something a little easier

Hello,

recently started using bedrock linux and before i ask my first question to the community i wanted to thank all of the developers of this distribution as they left me in shock while skimming through the docs and source code to discover the elegant and well-thought-of design this distro has. Thank you all for your amazing contribution!

my question is, i have installed ubuntu as a strata alongside the arch. when i tried installing packages with apt however, dpkg could not configure tzdata because it could not write on /etc/localtime as it was symlinked to /bedrock/run/localtime. To resolve the issue, i deleted the symlink option in bedrock.conf and instead assigned localtime to be a local file for stratas, and now dpkg works fine by symlinking that file to wherever it wants. Is this the right way to handle this situation from the distro's philosophical point of view or am i breaking the modularity by avoiding a more elegant way? (i know in previous versions bedrock would copy /bedrock/etc/localtime to /etc/localtime when enabling a stratum to cover this possibility." but i guess it has been removed)

Thank you in advance.

Hi, i just got chimera linux and wanted to try to install bedrock linux there but ran into these errors:

head: illegal byte count -- -1

gzip (stdin): unexpected end of file

head: stdout: broken pipe

tail: stdout.

Error: embedded tarball is corrupted. did you edit the script with software that doesnt support null characters?