MENU.LUA(8)

πŸ“¦ version 15.1, in freebsd 14.5, freebsd 15.1

Okay so this is menu.lua(8), from the System Manager's Manual, and it's literally the whole personality of the bootloader menu system. Buckle up πŸŽ€


✨ NAME ✨

menu.lua β€” the bootloader's dynamic menu module. That's it, that's the vibe. πŸ’–


🌸 DESCRIPTION 🌸

So menu.lua contains the main functionality you need to build a dynamic menu system. It also contains definitions for the built-in menus, and some of those are influenced by loader(8) environment variables. Sneaky but iconic. ✨

Before you hook into anything menu.lua gives you, you gotta include it, like this:

local menu = require("menu")

No cap, that's the whole entry ritual. 🫢


Menus are represented in menu.lua as a table, and that table must contain an entries key. Non-negotiable, bestie.

If the value of the entries key is itself a table, then each value in this table defines a single entry in this menu. Peep "MENU ITEM DEFINITIONS" for the structure of each entry. πŸ‘‘

entries may also be a function. That function must return a table, and each value of the returned table defines a single entry in this menu. Again, see "MENU ITEM DEFINITIONS". πŸ’…


Here are the keys you may define for a menu item β€” the whole glow-up kit:

  • entry_type β€” the type of this menu entry. See "MENU ITEM TYPES". πŸ‘€
  • carousel_id β€” a unique string id for this carousel. A carousel is a menu entry that rotates through a selection of items. This is used for storage of the carousel's current setting. 🎠
  • visible β€” a lambda that returns true if this menu item should be visible and false if it should not be visible. iykyk.
  • items β€” a table (or a lambda that returns a table) of the possible choices for this carousel.
  • name β€” a string (or a lambda that returns a string) containing the current name of this item.
  • func β€” the function executed when this entry is selected. Every type except for core.MENU_SEPARATOR may have a func. πŸ”₯
  • submenu β€” the submenu menu definition to draw when this entry is selected.
  • alias β€” a table of case-sensitive aliases for this menu entry. All menu entries that can be selected may have any number of alias entries. Yes, case-sensitive, so don't get cute. πŸ™ˆ

So like, entry_type is the only required key for every entry type. And name is required for all entry types except for core.MENU_SEPARATOR. That's the rule, periodt.


The menu item type constants are defined in core.lua(8). These are the available types, and honestly? Each one ate:

  • core.MENU_RETURN β€” return to the parent menu. If the current menu is the default menu, menu.lua will exit the menu and begin the autoboot sequence (if applicable). This type of menu entry may execute func, when selected, and has a name. πŸƒβ€β™€οΈ
  • core.MENU_ENTRY β€” a normal menu entry that executes func when selected, and has a name. The basic bestie. πŸ’…
  • core.MENU_SEPARATOR β€” a menu entry that serves as a separator. It may have a name. ───
  • core.MENU_SUBMENU β€” a menu entry that opens submenu when selected. It may have a name. πŸ“‚
  • core.MENU_CAROUSEL_ENTRY β€” a menu entry that rotates through items like a carousel. func is executed when selected, and the callback is passed the choice index, name of the current choice, and the table of choices. 🎠✨

πŸ‘‘ EXPORTED MENUS πŸ‘‘

menu.lua exports these menus, and they're all main character energy:

  • menu.default β€” the default menu to draw. Set to menu.welcome by default.
  • menu.welcome β€” the welcome menu. Contains single and multi user boot options, as well as entries to access other menus. πŸŽ€
  • menu.boot_options β€” the "Boot Options" menu.
  • menu.boot_environments β€” the "Boot Environments" menu. This menu is only visible if the system is booted on a ZFS partition and more than one boot environment was detected at boot. πŸ’€ (conditional queen)

🌈 EXAMPLES 🌈

Replacing the default boot menu with a simple boot menu

So you wanna replace the default boot menu with a simple boot menu? Slay, here's how:

local core = require("core")
local menu = require("menu")

menu.default = {
        entries = {
                {
                        entry_type = core.MENU_ENTRY,
                        name = "Boot",
                        func = core.boot,
                },
                {
                        entry_type = core.MENU_CAROUSEL_ENTRY,
                        carousel_id = "unique_boot_entry_name",
                        items = {"NO", "YES"},
                        name = function(_, choice, _)
                                return "Option: " .. choice
                        end,
                        func = function(_, _, _)
                                loader.setenv("some_envvar", "some_value")
                        end,
                },
        },
}

Look at that carousel go. Obsessed. 🎠

Adding another option to the welcome menu

Wanna add another option to the welcome menu? Say less:

local core = require("core")
local menu = require("menu")

local my_entry = {
        entry_type = core.MENU_ENTRY,
        name = "Fancy Boot",
        func = core.boot,
},

local stock_entries = menu.welcome.entries
function menu.welcome.entries()
        local ents = stock_entries()
        ents[#ents + 1] = my_entry
        return ents
end

(Yes, that trailing comma after the table in the original is exactly how it's written. Copy it character for character, bestie β€” we don't "fix" things here. ✨)

Creating a vendor submenu or other vendor menu option

To create a vendor submenu or other vendor menu option, override menu.welcome.all_entires.vendor like so β€” and yes, all_entires is spelled exactly like that in the original, no cap, don't @ me:

local core = require("core")
local menu = require("menu")

-- Fill in with vendor specific entries
local vendor_options = {
        entries = {
        ...
        },
}

local welcome_entries = menu.welcome.all_entries
welcome_entries.vendor = {
        entry_type = core.MENU_SUBMENU,
        name = color.highlight("V") .. "endor Options",
        submenu = vendor_options,
        alias = {"v", "V"},
        visible = function()
                return true
        end,
}

So in the above example, vendor_options is a local variable that defines the vendor submenu. πŸ’– (Note the inconsistency between all_entires and all_entries β€” that's literally in the source page, so we're keeping both exactly as-is. 🫢)

Adding an additional option to menu.boot_options

To add an additional option, change the menu.boot_options.entries array. The following illustrates this concept β€” it's giving "silly example" and I respect it:

-- This is a silly example that rotates local_option through the values
-- 0 to 4.  local_option would still need to be used elsewhere.
local local_option = 0

-- The `entries` of a menu may either be a table or a function.  In this
-- example we're augmenting a menu that just has a static table, but if we
-- wanted to be more robust then we would need to instead check the type
-- of `stock_options` here to determine our next move.
--
-- If `entries` is a table, then the stock menu system won't be changing it
-- so we can just add our menu option as we do below.
--
-- If `entries` is a function, then we would need to provide a new function to
-- replace `entries` that does a core.deepCopyTable() of the result and adds
-- the below item to it.  The deep copy is necessary to avoid duplicating our
-- new menu item and allowing the menu to alter its behavior however it pleases.
local stock_options = menu.boot_options.entries
stock_options[#stock_options + 1] = {
        entry_type = core.MENU_ENTRY,
        name = function()
                return color.highlight('L') ..
                    "ocal Option     : " .. local_option
        end,
        func = function()
                local_option = (local_option + 1) % 5
        end,
        alias= {"l", "L"}
}
⚠️ Important vibe check: if entries is a function, you can't just bolt your item on. You'd need to provide a new function to replace entries that does a core.deepCopyTable() of the result and adds the item to it. The deep copy is necessary to avoid duplicating your new menu item and allowing the menu to alter its behavior however it pleases. That's not me being dramatic, that's literally the spec. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

loader.conf(5), core.lua(8), loader(8)

Go read them, bestie, they're literally right there. πŸ“š


⭐ HISTORY ⭐

The menu.lua file first appeared in FreeBSD 12.0. A legend was born. πŸ‘‘


πŸŽ€ AUTHORS πŸŽ€

The menu.lua file was originally written by Pedro Souza <pedrosouza@FreeBSD.org>. Later work and this manual page was done by Kyle Evans <kevans@FreeBSD.org>. Shoutout to both, fr fr 🫢


✨ and that's the whole page, bestie ✨ β€” this one came from the Debian edition, dated March 29, 2025, sitting at MENU.LUA(8) in the System Manager's Manual. Go forth and build menus that slay πŸ’…πŸŒΈ

πŸ“¦ where this page comes from