pty_write(9)

📦 version 7.3.1, in nixpkgs unstable

hiii bestie 💖 welcome to pty_write(9) from the Kernel API Manual — today’s vibe check is “writing to a pty,” and ngl it’s kind of iconic ✨

🎀 NAME 🎀

pty_write — write to a pty, periodt 💅

✨ SYNOPSIS ✨

the way that the signature is literally right here, no cap:

ssize_t pty_write (struct tty_struct *tty , const u8 *buf , size_t c );

💅 ARGUMENTS 💅

  • tty — the tty we write from 🫶
  • buf — kernel buffer of data 📦
  • c — bytes to write 🔢

🦋 DESCRIPTION 🦋

okay so this is our “hardware” write method 👑 — yes, the quotes are doing a lot of work there, bestie 😭. Data is coming from the ldisc, which may be in a non sleeping state 😴🚫.

We simply throw this at the other end of the link, as if we were an IRQ handler receiving stuff for the other side of the pty/tty pair 🔥. That’s the whole vibe. It’s giving main character energy, fr fr 💜

not me romanticizing a kernel write path, but here we are 🙈

🔥 SEE ALSO 🔥

Kernel file ./drivers/tty/pty.c — and the related pages are pty_write_room(9), pty_resize(9), pty_start(9), pty_common_install(9), ptm_open_peer(9), ptm_unix98_lookup(9), pts_unix98_lookup(9), ptmx_open(9) — go read them, bestie 🫶

mwah 💋 this little page lives in ./drivers/tty, is dated October 2026, and goes by pty_write(9) — byeeee 🎀✨

📦 where this page comes from