UMOCKDEV-RECORD(1)

✨ NAME ✨

umockdev-record — record devices and ioctls 💖

(it's a User Commands situation, so like, section 1 of the manual, bestie 👑

---

🌸 DESCRIPTION 🌸

🎀 Usage:

umockdev-record [OPTION???] DEVICE [...]

okay so here's the ✨vibe✨: you can either record Linux devices and their ancestors straight from sysfs/udev, or you can record ioctls for a device. That's the whole gig. Two paths, one icon 💅

---

🦋 Help Options:

• -h, --help — shows you the help options, because sometimes we all need a lil guidance 🫶

---

👑 Application Options:

• -a, --all — record all the devices. not some. not a few. ALL of them. main character energy fr fr 🔥
• -i, --ioctl=devname=FILE — traces ioctls on the device and records them into the given file. ⚠️ heads up though: when you use this one, all the positional arguments become a command (and its arguments) to run and get traced. like, the whole argument list changes jobs. plot twist 💀
• -s, --script=devname=FILE — traces reads and writes on the device and records them into the given file. same deal as above: all positional arguments are a command (and its arguments) to run that gets traced. and the lil slay detail — you can specify this one multiple times 🌈
• -e, --evemu-events=devname=FILE — traces evdev event reads on the device and records them into the given file in EVEMU event format. yep, same rule: all positional arguments are a command (and its arguments) to run that gets traced. also specifiable multiple times, so go off 💅
• --version — outputs the version information and exits. short, sweet, iconic ✨

---

ngl, the devname=FILE thing is doing a lot of heavy lifting in those options — <italic>devname</italic> is the device name, <italic>FILE</italic> is where the recording lands. don't sleep on it 🍓

---

and that's the whole page, bestie!! this was umockdev-record 0.19.8, dated July 2026 — no cap, that's the source and the date, we love a tidy lil sign-off 🧚💜