BOOM(5)

📦
version 1.6.8 · 2 versions
  • 1.6.8 · centos-stream 10, centos-stream 9, fedora 43, fedora 44 (latest)
  • 1.6.6 · fedora 43
, in centos-stream 10, centos-stream 9, fedora 43, fedora 44

💖 BOOM(5) 💖

okay bestie, buckle up — this is boom(5), straight out of the FILE FORMATS MANUAL, and it's literally just the glow-up guide for the boom config file. no cap, it's short, it's cute, it's giving "read me in 3 minutes and slay". ✨

🌸 NAME 🌸

boom.conf — the boom configuration file, aka the vibe-setting document for your whole boom setup 🎀

🦋 SYNOPSIS 🦋

/boot/boom/boom.conf

that's it. that's the path. she's iconic, she's a single file, she holds the whole personality. 💅

✨ DESCRIPTION ✨

so boom.conf gets loaded during the initialisation of boom (like, the very first thing, before boom has even had her morning iced coffee ☕). inside are configuration keys that affect boom's global behaviour and also control the setting of boom's legacy configuration support.

the file is structured in INI format, which means:

  • section headers show up in square brackets [like this] 👑
  • configuration values are key-value pairs, one pair per line, no multitasking

🌈 SECTIONS 🌈

global

the global section holds the boot_path and boom_path keys, which let you override where /boot lives and where the /boot/boom configuration directory lives, respectively. yes, you can relocate both. main character moves. 💫

legacy

the legacy section is where you turn on and configure support for non-BLS boot loader configuration formats. it's the vintage section, the thrifted-fits section. 🧚

to enable legacy boot loader support, set the enable key to yes or true, and set the format key to the format you need — and heads up, currently only grub syntax is supported.

if the sync key is true, the legacy configuration gets automatically written whenever entries are added, removed, or modified. she keeps herself up to date, no reminders needed. 🫶

cache

the cache section holds the settings that control the behaviour of the boom boot image cache. 🔥

  • the enable key turns the boot image cache on or off. and bestie, listen: if the cache is disabled, the boom cache command and cache-related options such as --backup are not available. gone. unavailable. not invited to the party. 😭
  • the path to the on-disk cache can be changed by setting the cache_path key. by default, the cache lives in a subdirectory of /boot, at /boot/boom/cache. alternately, a separate file system can hold the cache — mounted at this path, or at another location specified in boom.conf. in that case, the cache file system should be configured to be mounted at the same location in all installed operating system instances. consistency is the whole point, fr fr. 💀
  • if the auto_clean key is enabled, boom will automatically remove cache entries when they're no longer used by a boom boot entry. self-cleaning queen behavior. 🧹✨

👑 AUTHORS 👑

Bryn M. Reeves <bmr@redhat.com> — the author, the icon, the legend 💜

🔗 SEE ALSO 🔗

and that's the whole page, bestie 🎀 this one came from the Linux manual, dated Mar 09 2018, and it's the BOOM(5) page — go forth and configure your boot loader with confidence. mwah. 💖🌟🍓

📦 where this page comes from