GETNEWVNODE(9)
πΈ NAME πΈ
getnewvnode β get a new vnode
okay bestie, welcome to getnewvnode(9) from the Kernel Developer's Manual, section 9 β and yes, it's literally about getting a shiny new vnode β¨
β¨ SYNOPSIS β¨
#include <sys/param.h>
#include <sys/vnode.h>
#include <sys/mount.h>
int
getnewvnode(const char *tag, struct mount *mp, struct vop_vector *vops,
struct vnode **vpp);
π DESCRIPTION π
so getnewvnode() initializes a new vnode and assigns it the vnode operations you pass in vops. iconic behavior, honestly π«Ά
the arguments to getnewvnode() are giving:
tagβ the file system type string. this field should only be referenced for debugging or for userland utilities πmpβ the mount point to add the new vnode to.vopsβ the vnode operations to assign to the new vnode.vppβ points to the new vnode upon successful completion π
π RETURN VALUES π
getnewvnode() returns 0 on success. that's it, that's the whole return value, and she ate π
π BUGS π
it never returns an error, instead either succeeds or blocks indefinitely. not me being dramatic, but that is literally the documented behavior π
π«Ά AUTHORS π«Ά
this manual page was written by Chad David <davidc@acns.ab.ca>.
xoxo, Debian bestie π β this page is dated November 1, 2023 π
π¦ where this page comes from
- freebsd 15.1: base 15.1
- nixpkgs unstable: source
- Copyright (C) 2001 Chad David <davidc@acns.ab.ca>. All rights reserved
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms