xbc_init(9)

✨ xbc_init ✨

okay so this is a page from the Kernel API Manual — yes bestie, the kernel has man pages too, we love a documented king 💅 — and it's all about xbc_init, which parses your XBC file and builds the whole XBC internal tree. very main character energy honestly 🌸

---

🎀 NAME 🎀

xbc_init — parse the XBC file you handed it and build the XBC internal tree 🌳✨

---

🦋 SYNOPSIS 🦋

int xbc_init (const char *data , size_t size , const char **emsg , int
*epos );

---

💖 ARGUMENTS 💖

• data — the boot config text original data, aka the actual raw bytes you're feeding in 🍓
• size — the size of data, like how many bytes we're working with, no cap
• emsg — a pointer of const char * where the error message gets stored 🙈
• epos — a pointer of int where the error position gets stored

---

🔥 DESCRIPTION 🔥

this parses the boot config text in data. and listen — size must be smaller than XBC_DATA_MAX. not "should", must. that's the vibe check and if you fail it that's on you 😭

if it works out, it returns the number of stored nodes (>0) — slay 🎉 — or -errno if there's any error at all.

in error cases: emsg gets updated with an error message, and epos gets updated with the error position, which is the byte offset of buf. and if the error is not a parser error? then epos will be -1. iconic of it honestly 🫶

---

👑 SEE ALSO 👑

Kernel file ./lib/bootconfig.c — and honestly the whole friend group:

• xbc_prepend_embedded_cmdline(9)
• xbc_embedded_cmdline_applied(9)
• bootconfig_cmdline_requested(9)
• xbc_get_info(9)
• xbc_root_node(9)
• xbc_node_index(9)
• xbc_node_get_parent(9)
• xbc_node_get_child(9)
• xbc_node_get_next(9)
• xbc_node_get_data(9)
• xbc_node_find_subkey(9)
• xbc_node_find_value(9)
• xbc_node_compose_key_after(9)
• xbc_node_find_next_leaf(9)
• xbc_node_find_next_key_value(9)
• xbc_snprint_cmdline(9)
• _xbc_exit(9)

---

💜 and that's the whole page bestie 💜

this one's shipped straight out of ./lib, dated October 2026, and it's literally called xbc_init(9) — go build that tree, you got this 🧚✨🎀