wadfs – WAD file system|
wadfs [ –Dr ] [ –m mtpt ] [ –S srvname ] [ WAD ]|
Wadfs serves a file tree mounted at mtpt (default /mnt/wad) that
provides access to a WAD file's contents. |
The command line options are:
A WAD is a concatenation of uncompressed files, referred to as lumps. A lump may contain either data, or be used as a marker to indicate the beginning or end of a section, segregating lumps of the same format.
Wadfs represents section start markers as directories, and regular lumps and end markers as files. For convenience, lump file names are in lower case, and are translated to the upper case internally.
At startup, if the path to a WAD file is provided as argument, wadfs will attempt to parse it and construct a file tree. Otherwise, wadfs starts with a blank tree instead.
Two additional files are provided in the file system's root directory: SIG and WAD. Reading from and writing to SIG allows accessing and changing the WAD's type. The only possible values are PWAD (the default) and IWAD.
WAD returns the new WAD file resulting from the recompilation
of the lump tree.
WAD file structure
Wadfs imposes a number of additional restrictions on structure
Open doom2.wad and play a MUS file:|
Wadfs first appeared in 9front (August, 2017).|
Many WAD files in the wild do not conform to all the rules exposed
above, in particular ones using DeHackEd engine modifications.
WAD's using end markers outside of a section, typically F_END,
will lose them. |
Repairing broken WAD files can be a pain.