REMOVE(9P)

🦋 NAME 🦋

okay so bestie, this is REMOVE(9P), the page for remove — remove a file from a server. it’s giving “delete request but make it protocol” 💅✨

✨ SYNOPSIS ✨

size[4] Tremove tag[2] fid[4]
size[4] Rremove tag[2]

💖 DESCRIPTION 💖

The remove request asks the file server both to remove the file represented by fid and to clunk the fid — even if the remove fails. yes, the clunk is non-negotiable, bestie 🫶. This request will fail if the client does not have write permission in the parent directory.

It is correct to consider remove to be a clunk with the side effect of removing the file if permissions allow. so like: clunk with a delete side quest, and permissions decide if the side quest actually lands ✨.

If a file has been opened as multiple fids, possibly on different connections, and one fid is used to remove the file, whether the other fids continue to provide access to the file is implementation-defined. The Plan 9 file servers remove the file immediately: attempts to use the other fids will yield a phase error. 😭 (yes, the quoted “phase error.” vibe). U9fs follows the semantics of the underlying Unix file system, so other fids typically remain usable. ngl that’s a whole different energy between Plan 9 and U9fs 🌀.

🌸 ENTRY POINTS 🌸

• Fsremove — see 9pclient(3). it generates remove messages. yes bestie, that’s the entry point, and it’s literally generating the remove messages 👑.

sign-off, bestie: the footer is just REMOVE(9P) — no source/version line and no date line are included on this page 💖🎀