nfs_mount(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nfs_mount(9) β€” like, the actual kernel API manual, bestie

okay so you're reading the nfs_mount(9) page from the Kernel API Manual and honestly? it's short, it's sweet, and it gets a file handle for you. let's go πŸŽ€


✨ NAME ✨

nfs_mount β€” Obtain an NFS file handle for the given host and path</p> πŸ¦‹

that's it. that's the whole job. it gets you a handle. icon behavior fr fr.


🌸 SYNOPSIS 🌸

int nfs_mount (struct nfs_mount_request *info , int timeo , int retrans );

three args, one int back, no cap πŸ’…


🧚 ARGUMENTS 🧚

  • info β€” pointer to mount request arguments. this is where you hand over the whole vibe of what you're asking for 🫢
  • timeo β€” deciseconds the mount waits for a response before it retries. yes bestie, *deci*seconds, not seconds, read the label ⏱️
  • retrans β€” number of times the mount retries a request. how many chances are we giving it? you decide ✨

πŸ‘‘ DESCRIPTION πŸ‘‘

Uses timeout parameters specified by caller. that's the timeo and retrans from above β€” you're the main character setting the timetable here, it does not pick for you πŸ’…

On successful return, the auth_flavs list and auth_flav_len will be populated with the list from the server β€” or a faked-up list if the server didn't provide one 🌈 and yeah, a faked-up list is the literal wording, the kernel is out here improvising and honestly? respect 😭

✨ tiny vibe check: those fields being filled in is specifically on successful return, so don't go reading them before you've checked what came back, bestie 🫢

πŸ”₯ SEE ALSO πŸ”₯

  • Kernel file ./fs/nfs/mount_clnt.c β€” go read the source, iykyk πŸ¦‹

alright bestie, that's the whole page, you ate it up πŸ“ this one came from the ./fs/nfs source, dated October 2026, and it's filed under nfs_mount(9) in the Kernel API Manual. mwah πŸ’– slay responsibly ✨

πŸ“¦ where this page comes from