Introduction

Welcome, intrepid sysadmin! You’re about to embark on a journey to install Bedrock Linux, the meta-distribution that lets you “breed” other Linux distros into one. Think of it as the Linux version of Swiss Army Knife meets Pokémon. By the end of this guide, you’ll run Arch’s package manager, Debian’s stability, and Fedora’s freshness in one harmonious environment.

Why Choose Bedrock Linux?

Bedrock Linux breaks the traditional distro silo. Instead of being locked into one ecosystem, you create a patchwork of your favorite features. It’s like building a custom car from parts of a Ferrari, Tesla, and vintage VW Beetle—only more stable.

System Requirements

• 64-bit x86 CPU (Intel or AMD)
• 2nbspGB RAM minimum (4nbspGB recommended)
• Disk space: 10nbspGB for base, plus extras per bred distro
• Internet connection for downloads
• One working Linux environment to create installation media

Step 1: Preparing Installation Media

Downloading the ISO

Grab the latest Bedrock Linux ISO. It’s lightweight (~100nbspMB) because it’s a bootstrapper, not a monolithic distro.

Creating a Bootable USB

• Insert a USB stick (≥2nbspGB).
• Identify it: lsblk or sudo fdisk -l.
• Write with dd (replace /dev/sdX):

  sudo dd if=bedrock.iso of=/dev/sdX bs=4M status=progress  sync

Step 2: Boot and Partition Disk

Reboot, select USB in BIOS/UEFI, and you’ll land in a minimal shell.

Partitioning

# Launch fdisk (or cfdisk): 
sudo fdisk /dev/sda

# Example partition table:
# /dev/sda1  EFI   512M
# /dev/sda2  root  20G
# /dev/sda3  swap  4G
  

Format partitions:

sudo mkfs.fat -F32 /dev/sda1
sudo mkfs.ext4 /dev/sda2
sudo mkswap /dev/sda3  sudo swapon /dev/sda3
  

Step 3: Install Base System

Mount your new root:

sudo mount /dev/sda2 /mnt

Create directories and mount EFI:

sudo mkdir -p /mnt/boot/efi
sudo mount /dev/sda1 /mnt/boot/efi
  

Run the Bedrock bootstrap script:

sudo sh -c curl -sSL https://bedrocklinux.org/install  sh

This touches /mnt/bedrock-install and downloads necessary components.

Step 4: Chroot into Bedrock

# Enter the chroot:
sudo mount --bind /dev /mnt/dev
sudo mount --bind /sys /mnt/sys
sudo mount --bind /proc /mnt/proc
sudo chroot /mnt /bin/sh
  

You’re now inside the future of your meta-distribution.

Step 5: Configure the Bootloader

Within chroot:

# Install systemd-boot for UEFI
bootctl --path=/boot/efi install

# Create loader entry:
cat > /boot/efi/loader/entries/bedrock.conf << EOF
title   Bedrock Linux
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options root=LABEL=ROOT rw
EOF
  

Adjust vmlinuz-linux and initramfs-linux.img names to match your kernel.

Step 6: Post-Installation Configuration

1. Set Up Networking

• Install dhcpcd or NetworkManager.
• Enable service: systemctl enable dhcpcd.

2. Create a User

passwd root
useradd -m -G wheel yourname
passwd yourname
  

Edit /etc/sudoers to allow %wheel ALL=(ALL) ALL.

3. Breeding Distributions

Bedrock’s brc tool lets you “adopt” other distros. For example, to utilize Arch’s pacman:

brc arch-bootstrap
source /bedrock/arch/brc
pacman -Syu
  

Now you can pacman -S htop and enjoy Arch’s AUR helpers too.

4. Package Management Across Breeds

Each bred distro remains sandboxed but accessible. A quick table:

Troubleshooting Common Issues

• Bootloader fails: Double-check loader.conf paths and UEFI settings.
• Networking missing: Ensure you installed and enabled a network service.
• “Command not found” in breeds: Remember to source the relevant brc script.
• Filesystem corruption: Run fsck on the partition from a rescue USB.

Tips and Tricks

• Keep your /etc/fstab tidy—use LABEL instead of /dev/sdXY.
• Use aliases in your shell to switch breeds quickly.
• Back up /bedrock directory—it holds your breed metadata.
• If in doubt, ask the cheerful rubber-duck debugging method: explain your steps aloud!

Resources and References

• Official Bedrock Linux Website
• Bedrock Linux on GitHub
• ArchWiki: Bedrock Linux
• brc Man Page

Congratulations! You now wield the power of multiple distros under one kernel. Go forth and customize—just don’t forget to document how you mixed your flavors, or you’ll spend next week debugging why your mail client is pulling from Fedora!