MOUNT3(3)
β¨ MOUNT3 β¨
okay bestie, welcome to MOUNT3 β that's manual page MOUNT3(3), from the mount3 module, version 3.0 π
This page is all about packet.nfs.mount3 β the MOUNTv3 decoding module. Sit down, get comfy, we're decoding some NFS mount protocol stuff together π¦
πΈ NAME πΈ
packet.nfs.mount3 β the MOUNTv3 decoding module π
π CLASSES π
class DUMP3res(baseobj.BaseObj)
struct DUMP3res {
mountentry3 *mountlist;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class EXPORT3res(baseobj.BaseObj)
struct EXPORT3res {
exportnode3 *exports;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class MNT3args(baseobj.BaseObj)
struct MNT3args {
dirpath3 path;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class MNT3res(baseobj.BaseObj)
union switch MNT3res (mountstat3 status) {
case const.MNT3_OK:
MNT3resok mountinfo;
default:
void;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class MNT3resok(baseobj.BaseObj)
struct MNT3resok {
fhandle3 fh;
rpc_auth_flavors auth_flavors<>;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class MOUNT3args(packet.utils.RPCload)
union switch MOUNT3args (mount_proc3 procedure) {
case const.MOUNTPROC3_NULL:
void;
case const.MOUNTPROC3_MNT:
MNT3args opmnt;
case const.MOUNTPROC3_DUMP:
void;
case const.MOUNTPROC3_UMNT:
UMNT3args opumnt;
case const.MOUNTPROC3_UMNTALL:
void;
case const.MOUNTPROC3_EXPORT:
void;
};
Methods defined here: β¨
__init__(self, unpack, procedure)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class MOUNT3res(packet.utils.RPCload)
union switch MOUNT3res (mount_proc3 procedure) {
case const.MOUNTPROC3_NULL:
void;
case const.MOUNTPROC3_MNT:
MNT3res opmnt;
case const.MOUNTPROC3_DUMP:
DUMP3res opdump;
case const.MOUNTPROC3_UMNT:
void;
case const.MOUNTPROC3_UMNTALL:
void;
case const.MOUNTPROC3_EXPORT:
EXPORT3res opexport;
};
Methods defined here: β¨
__init__(self, unpack, procedure)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class UMNT3args(baseobj.BaseObj)
struct UMNT3args {
dirpath3 path;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class exportnode3(baseobj.BaseObj)
struct exportnode3 {
dirpath3 dir;
groupnode3 *groups;
exportnode3 *next;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class groupnode3(baseobj.BaseObj)
struct groupnode3 {
name3 name;
groupnode3 *next;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class mount_proc3(packet.utils.Enum)
enum mount_proc3
class mountentry3(baseobj.BaseObj)
struct mountentry3 {
name3 hostname;
dirpath3 directory;
mountentry3 *next;
};
Methods defined here: β¨
__init__(self, unpack)β Constructor π«Ά
Sets up the object's private data according to the arguments you give it. Arguments can come in as positional, named, or a lil combo of both β whatever vibe you're on, it's valid π
class mountstat3(packet.utils.Enum)
enum mountstat3
class rpc_auth_flavors(packet.utils.Enum)
enum rpc_auth_flavors
π FUNCTIONS π
dirpath3(unpack)fhandle3(unpack)β Basic Data Types βname3(unpack)
π¦ SEE ALSO π¦
go read these next, bestie, they're part of the lore:
π BUGS π
No known bugs. Not one. We're clean, we're thriving, we're unbothered β¨
π AUTHOR π
Jorge Mora (mora@netapp.com) β the icon who made this happen π«Ά
and that's the whole page, bestie!! this was NFStest 3.2, dated 21 March 2023 β mwah, go forth and decode some MOUNTv3 ππΈβ¨
π¦ where this page comes from
- debian trixie: nfstest 3.2-3
- fedora 43: NFStest 3.2-14.fc43 Β· GPL-2.0-or-later
- fedora 44: NFStest 3.2-16.fc44 Β· GPL-2.0-or-later
- ubuntu noble: nfstest 3.2-2
- ubuntu questing: nfstest 3.2-3
- ubuntu resolute: nfstest 3.2-3build1
- ubuntu stonking: nfstest 3.2-5
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms