PUD(4)

Hey bestie 💖 welcome to the PUD(4) kernel interfaces manual page for pud, the Pass-to-Userspace Device — it's giving kernel-interface realness and I'm obsessed ✨.

✨ NAME ✨

• pud — Pass-to-Userspace Device 🦋

🦋 SYNOPSIS 🦋

pseudo-device pud
pseudo-device putter

💅 DESCRIPTION 💅

Okay so picture this: the pud driver is the main character that enables the implementation of block and character device drivers as userspace daemons 👑✨. Those daemons register the device major number they wish to handle — that's literally the whole vibe. Registering a character device is mandatory, no cap, while supporting the block device interface for the same major device is optional 💅. The major number must be available, i.e. another driver must not be registered to handle the operation. After successful registration, the userspace daemon is supposed to handle the driver methods the kernel passes down to it 🫶.

🌈 SEE ALSO 🌈

Go read these besties:

• puffs(4) 🦋
• putter(9) 💖

💀 BUGS 💀

This document is in a hit-in-the-head style obviously not even near complete. 😭

The subsystem lacks a puffs-style library that servers can be written against. 💀

Signed, sealed, and slaying: brought to you by the Debian source/version, dated November 21, 2007 🎀💖