PBE-DEPLOY(1)
π PBE(1) β the pbe deploy era π
okay bestie, welcome to PBE, section 1 of the manual. this is the part where we talk about pbe deploy, and honestly? it's giving main character energy. β¨
πΈ COMMAND pbe deploy πΈ
first things first, the vibe check β here's the whole usage line, copied with love and zero typos:
pbe deploy [-h] [-q] [-d] [--kernel-src KSRC] [--local-build]
[--tmpdir-path TMPDIR_PATH] [--keep-tmpdir] [-H HOSTNAME] [-U USERNAME]
[-K PRIVKEY] [-T TIMEOUT]
so what does it do? it compiles and deploys pbe drivers to the SUT (System Under Test), and that SUT can be can be either local or a remote host, depending on the -H option. π
by default, literally everything gets built on the SUT. but if you're feeling independent, --local-build lets you build on your own local system instead. π
and where do we go looking for these drivers? great question, bestie. on the local host, pbe searches these directories, in this exact order:
./drivers/idle$WULT_DATA_PATH/drivers/idle$HOME/.local/share/wult/drivers/idle/usr/local/share/wult/drivers/idle/usr/share/wult/drivers/idle
no cap, that's the whole search list. π¦
β¨ OPTIONS pbe deploy β¨
here's every single flag, no skipping, no summarising, we keep it thorough around here. π«Ά
-hβ show this help message and exit. the classic "help me pls" button. π-qβ be quiet. shhh. π€«-dβ print debugging information. for when you need the tea. π--kernel-src KSRCβ path to the Linux kernel sources to build drivers against. the default is/lib/modules/$(uname -r)/buildon the SUT. and heads up: if--local-buildwas used, then this path is considered to be on the local system, not the SUT. π--drivers-make-optsβ options and variables to pass tomakewhen the drivers are built. for example, passCC=clang LLVM=1to use clang and LLVM tools for building the drivers (this is required when the kernel was build with clang/LLVM). π₯--local-buildβ build drivers locally, instead of building onHOSTNAME(the SUT). be your own build machine, queen. π--tmpdir-path TMPDIR_PATHβ whenpbeis deployed, a random temporary directory is used. use this option to provide a custom path instead. it will be used as a temporary directory on both local and remote hosts. this option is meant for debugging purposes. π§--keep-tmpdirβ do not remove the temporary directories created while deployingpbe. this option is meant for debugging purposes. (the temp dirs stay, like they're moving in permanently. π )-H HOSTNAME,--host HOSTNAMEβ name of the host to run the command on. π-U USERNAME,--username USERNAMEβ name of the user to use for logging into the remote host over SSH. the default user name isroot. π-K PRIVKEY,--priv-key PRIVKEYβ path to the private SSH key that should be used for logging into the remote host. by default the key is automatically found from standard paths like~/.ssh. πβ¨-T TIMEOUT,--timeout TIMEOUTβ SSH connect timeout in seconds, default is8. β±οΈ
ok bestie, quick reminder:--tmpdir-pathand--keep-tmpdirare both meant for debugging purposes, so don't get too comfy with them in your everyday flow. π
that's the whole page, fr fr. you ate this. periodt. π β¨
this iconic page is from the PBE manual, dated 2024-05-28, and it signs off as PBE() β mwah, take care of her. πππ¦
π¦ where this page comes from
- fedora 43: wult 1.12.48-2.fc43 Β· BSD-3-Clause AND GPL-2.0-only
- fedora 44: wult 1.12.48-2.fc44 Β· BSD-3-Clause AND GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms