Skip to main content

Loading the code workspace…

LC

Understand the Initial RAM Filesystem (initramfs)

medium7/8

Understand UEFI Secure Boot and Chain of Trust Understand Bootloader Chainloading

Language

Compiler

2.0s Limit 256MB

Submit and pass all tests to enable saving to GitHub.

Implementation

Simulate initramfs operations in C.

Requirements:

Define initramfs structure with modules, devices, and init script
Implement load_module(name) that simulates loading kernel modules
Implement mount_root(device, fs_type)
Implement switch_root(new_root, init)
Show initramfs contents listing
Show module loading sequence
Show root filesystem being mounted
Show pivot_root/switch_root concept
Simulate a failure case and emergency shell
Print boot stages clearly

Test:

Show initramfs loaded
Show modules loaded
Show root mounted
Show switch root
Show failure handling

Why This Matters

Every Fedora and Arch install regenerates its initramfs with dracut or mkinitcpio after a kernel update — skip that step and the system drops to the emergency shell you're simulating here because the NVMe or LUKS driver never got loaded. This chicken-and-egg problem (drivers needed to mount root, but root not yet mounted) is the exact reason initramfs exists instead of building every driver statically into the kernel.

Hints

0 / 3 revealed

Validation Suite

main.c

Workspace 1.0

← Understand UEFI Secure Boot and Chain of TrustUnderstand Bootloader Chainloading →