UMOCKDEV-RUN(1)

✨ NAME ✨

umockdev-run — bestie, this is the one that runs your program inside an umockdev testbed 🧚 like a lil fake-hardware playground for your process, and it is genuinely iconic.

---

🌸 DESCRIPTION 🌸

💅 Usage 💅

umockdev-run [OPTION???]
       -- program [args..]

okay so the whole vibe here: you run a program under an umockdev testbed. you pass your options, then that lil -- divider (she's the moment, she's the boundary, respect her), and then the program plus its args. periodt. 💖

---

🎀 Help Options 🎀

• -h, --help — shows the help options. your girl when you're lost, no cap 💫

---

👑 Application Options 👑

• -d, --device=filename — loads an umockdev-record device description into the testbed. you can specify this multiple times, so stack 'em up like a charm bracelet 🎀✨
• -i, --ioctl=devname=ioctlfilename — loads an umockdev-record ioctl dump into the testbed. also multiple-times-able, go off 🦋
• -p, --pcap=sysfs=pcapfilename — loads a pcap/pcapng USB dump into the testbed. yep, multiple times is fine, we love options 👑
• -s, --script=devname=scriptfilename — loads an umockdev-record script into the testbed. multiple times, obviously 💅
• -u, --unix-stream=socket_path=scriptfilename — loads an umockdev-record script for a mocked Unix stream socket. and yes, multiple times, she's flexible 🌈
• -e, --evemu-events=devname=eventsfilename — loads an evemu .events file into the testbed. can be specified multiple times too 🍓
• --version — spits out version information and dips out immediately. no further notes, she's done 🌸

heads up bestie: for every single one of those load-y options, "can be specified multiple times" is literally in the spec, so don't be shy about repeating them 💖

---

and that's the whole page fr fr — umockdev-run 0.19.8, July 2026, from the UMOCKDEV-RUN(1) era, User Commands chapter. mwah, go run something in a fake testbed and slay 💅✨🫶