xmount(1)
π xmount(1) π
okay bestie, sit DOWN, because xmount is about to be your new obsession β this is the xmount manual page, and I'm gonna walk you through it like we're texting at 2am π¦
β¨ NAME β¨
xmount β the tool to crossmount between multiple input and output harddisk image files. crossmounting?? it's giving matchmaker but for disk images fr fr π
π SYNOPSIS π
xmount [fopts] <xopts> <mntp>
π DESCRIPTION π
okay so xmount lets you convert on-the-fly between multiple input and output harddisk image formats. literally while you're using it, no pre-conversion era. π It creates a virtual file system using FUSE (Filesystem in Userspace) that contains a virtual representation of the input image. virtual representation?? she's that girl.
The virtual representation can be in:
- raw DD
- Apple's Disk Image format (DMG) π
- VirtualBox's virtual disk file format (VDI)
- Microsoft's Virtual Hard Disk Image format (VHD)
- VmWare's VMDK file format
and the input images can be:
- raw DD
- EWF (Expert Witness Compression Format)
- AFF (Advanced Forensic Format v3 & possibly v4 β check
xmount --info, iykyk π) - VDI (VirtualBox Virtual Disk Image)
- QCOW (QEMU Copy On Write) files
It is also possible to apply morphing functions to input images. like??? you can combine multiple input images into one output image, or reconstruct raids on-the-fly. raids!! reconstructed!! on-the-fly!! π₯
And finally β and this is the part that ate, no cap β xmount also supports virtual write access to the output files that is redirected to a cache file. This makes it possible to boot acquired harddisk images using QEMU, KVM, VirtualBox, VmWare or alike. booting images?? main character energy fr π
πΈ OPTIONS πΈ
π« fopts: (Options specific to FUSE) π«
-dβ Enable FUSE's and xmount's debug mode. π-hβ Display this help message. bestie needs help sometimes, it's fine π«Ά-sβ Run single threaded.-o no_allow_otherβ Disable automatic addition of FUSE'sallow_otheroption.-o <fmopts>β Specify fuse mount options.
β οΈ heads up: this will also disable automatic addition of FUSE's allow_other option! it's a package deal, sorry not sorry π
β¨ xopts: (Options specific to xmount) β¨
--cache <cfile>β Enable virtual write support.<cfile>specifies the cache file to use. π--in <itype> <ifile>β Input image format and source file(s). May be specified multiple times.
For a list of supported <itype> types, run xmount --info and look under "loaded input libraries".
<ifile> specifies the source file. If your image is split into multiple files, you have to specify them all! not some of them. ALL of them. periodt. π
--inopts <iopts>β Specify input library specific options.<iopts>specifies a comma separated list ofkey=valueoptions.--infoβ Print out infos about used compiler and loaded libraries. π§--morph <mtype>β Morphing function to apply to input image(s). If not specified, defaults to"combine".
For a list of supported <mtype> types, run xmount --info and look under "loaded morphing libraries".
--morphopts <mopts>β Specify morphing library specific options.<mopts>specifies a comma separated list ofkey=valueoptions.--offset <off>β Move the output image data start<off>bytes into the input image(s).--out <otype>β Output image format. If not specified, defaults to"raw".
<otype> can be "raw", "dmg", "vdi", "vhd", "vmdk", "vmdks". π
--owcache <file>β Same as--cache <file>but overwrites existing cache file. π€--rocache <file>β Same as--cache <file>but does not allow further writes.
π read-only girlies, this one's for you. once it's written, it's written. no takebacks.
--sizelimit <size>β The data end of input image(s) is set to no more than<size>bytes after the data start.--versionβ Same as--info.
π¦ mntp: π¦
- Mount point where virtual files should be located. π
π BUGS π
Hopefully none. π If you find any, please e-mail to <bugs@sits.lu>. do it, they wanna hear from you, bestie π
β EXAMPLE β
To xmount an EWF image from your acquired disk as a raw DD image under /mnt, use the following command:
xmount --in aewf ./acquired_disk.E?? /mnt
To xmount the same ewf image as vdi file, you would use a command like this:
xmount --in aewf ./acquired_disk.E?? --out vdi /mnt
And to enable virtual write support on a raw DD input image xmounted as VDI file:
xmount --in raw ./acquired_disk.dd --out vdi --cache ./disk.cache /mnt
see?? three commands and you're literally a forensic disk image girlie now. it's giving effortless. π
okay that's the whole page bestie, go forth and crossmount πβ¨π¦
this iconic piece of documentation was written by Daniel Gillen, dated Mar 15, 2024, and it lives in the xmount(1) manual β version and all, we stan an organized queen π π πΈ
π¦ where this page comes from
- debian trixie: xmount 1.2.0+ds-1+b1 Β· GPL-3.0-or-later
- epel 10: xmount 1.2.0-1.el10_2 Β· GPL-3.0-or-later
- epel 9: xmount 1.2.0-1.el9 Β· GPL-3.0-or-later
- fedora 43: xmount 1.2.0-1.fc43 Β· GPL-3.0-or-later
- fedora 44: xmount 1.2.0-6.fc44 Β· GPL-3.0-or-later
- ubuntu questing: xmount 1.2.0+ds-1build1
- ubuntu resolute: xmount 1.2.1+ds-1 Β· GPL-3.0-or-later
- ubuntu stonking: xmount 1.3.1+ds-1 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms