libnvme(2)
π NAME π
enum nvme_fctype β the Fabrics Command Types, bestie. It's literally the little enum that says which Fabrics commands exist. Periodt.
β¨ SYNOPSIS β¨
Okay so here's the whole vibe, exactly as it lives in the header:
enum nvme_fctype {
nvme_fabrics_type_property_set ,
nvme_fabrics_type_connect ,
nvme_fabrics_type_property_get ,
nvme_fabrics_type_auth_send ,
nvme_fabrics_type_auth_receive ,
nvme_fabrics_type_disconnect
};
That's it, that's the whole squad. Six constants, no drama, no extra members. Slay. π
π Constants π
Sit down, take a sip of your strawberry matcha π, and let me introduce you to every single one of them. No skipping, no summarising β all six, in order, fr fr.
nvme_fabrics_type_property_setβ Property set. Yeah, that's the whole description. Property set. Iconic for being so short ngl.nvme_fabrics_type_connectβ Connect. She's the one who shows up and makes the connection happen. Main character energy tbh.nvme_fabrics_type_property_getβ Property Get. The getter to the setter's setter. Balanced, as all things should be. π¦nvme_fabrics_type_auth_sendβ Authentication Send. Sending that auth info out into the world, confident, unbothered. β¨nvme_fabrics_type_auth_receiveβ Authentication Receive. Her whole job is receiving. Respect it. π«Άnvme_fabrics_type_disconnectβ Disconnect. She said "and that's my time" and left the group chat. Leaving is self-care, lowkey. π
Heads up bestie: that is literally every constant listed, and every description, in the exact order the original gives them. I did not add a single thing, because adding fake behaviour to a manpage is not the vibe. π
That's the whole page, mwah π β this was the API Manual for libnvme, page libnvme(2), covering enum nvme_fctype, and it was signed, sealed and dated July 2026. Bye bestie, go forth and Fabrics. ππ
π¦ where this page comes from
- ubuntu stonking: libnvme-dev 1.16.2-1build1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms