BOOTPEF(8)

📦
version 2.4.3 · 2 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 BOOTPEF(8) 💖

ok so bestie, welcome to the System Manager's Manual, section 8 — this is bootpef, and it's lowkey the main character of BOOTP extension file compiling. no cap. 🎀

✨ NAME ✨

bootpef — the BOOTP Extension File compiler. that's it, that's the whole job. 💅

🌸 SYNOPSIS 🌸

bootpef [ -c chdir ] [ -d debug-level ] [-f config-file ] [ client-name [...]]

🦋 DESCRIPTION 🦋

okay so here's the vibe: bootpef builds the Extension Path files described by RFC 1497 (tag 18). that's literally its whole thing. ✨

and if you pass any client-name arguments? then bootpef compiles the extension files for only those clients. not all of them, bestie. just the ones you named. very picky, very demure. 🙈

👑 OPTIONS 👑

  • -c chdir-path — sets the current directory that bootpef uses while it's creating extension files. this is highkey useful when the extension file names are given as relative pathnames, and bootpef needs to be in the same current directory as the TFTP server — which is typically /tftpboot. 🫶
  • -d debug-level — sets the debug-level variable, which controls how many debugging messages get generated. like, for example, -d4 or -d 4 will set the debugging level to 4. yes bestie, both spellings, slay. 🔥
  • -f config-file — sets the name of the config file that specifies the option data to be sent to each client. it's giving "tell me what to send and to whom." 💌

🌈 SEE ALSO 🌈

⭐ REFERENCES ⭐

  • RFC951 BOOTSTRAP PROTOCOL (BOOTP)
  • RFC1497 BOOTP Vendor Information Extensions
🫶 friendly lil reminder bestie: this page lives under the MAINTENANCE COMMANDS umbrella, and it's dated 4 Dec 1993 — yes, 1993, the lore is ancient and we respect it. periodt. 💜

and that's the whole page, no notes, BOOTPEF(8) ate and left no crumbs. 💖✨🎀

📦 where this page comes from