nemo features

Prints a matrix of which filesystems (ntfs, apfs, ext4) support which techniques (named-stream, slack-space, timestomp). Each row is one filesystem and technique pair, marked supported or unsupported.

nemo features
nemo features --mode image
nemo features --mode live

Run it before hide to check what a given image can do.

The matrix is built from the same registrations nemo uses at runtime, so it cannot drift from real behavior. Filesystem interfaces explains how it is assembled.

Modes

A supported row still depends on the target’s format, file layout, and permissions.

Live mode on Linux

Support matrix

This table covers image mode. Filesystem layout restrictions still apply. For native platform limits, see Modes.

Filesystem named-stream slack-space timestomp
ext4 internal/filesystem/ext4/ext4.go and xattr.go bounded image layouts internal/filesystem/ext4/timestomp.go
APFS internal/filesystem/apfs/namedstream.go (in-place B-tree leaf rewrite, no allocation) bounded image layouts yes
NTFS internal/filesystem/ntfs/namedstream.go (resident and non-resident, MFT-mirror aware) bounded image layouts yes
fakefs yes yes yes (test double, internal/filesystem/fakefs)

fakefs is an in-memory filesystem that implements all three capabilities on a byte-slice image. It lets internal/technique be tested without a real NTFS, APFS, or ext4 image.

A real filesystem’s Entry implements the same interfaces that fakefs.Entry already does.