TAPEFS(4)

✨ NAME ✨

okay so this is TAPEFS(4) from the Kernel Interfaces Manual, and the lineup is literally 32vfs, cpiofs, tapfs, tarfs, tpfs, v6fs, v10fs, zipfs — all here to mount archival file systems. 💖

🎀 SYNOPSIS 🎀

fs/32vfs [ -b blocksize ] [ -m mountpoint ] [ -p passwd ] [ -g group ]
file
fs/cpiofs
fs/tapfs
fs/tarfs
fs/tpfs
fs/v6fs
fs/v10fs
fs/zipfs

🦋 DESCRIPTION 🦋

These commands interpret data from traditional tape or file system formats stored in file, and mount their contents (read-only) into a Plan 9 file system. No cap, read-only is the whole vibe. 🫶

The optional flags are doing the most in the best way:

• -p passwd, -g group — these optional flags specify Unix-format password (respectively group) files that give the mapping between the numeric user- and group-ID numbers on the media and the strings reported by Plan 9 status inquiries. iykyk.
• -m mountpoint — introduces the name at which the new file system should be attached; the default is /n/tapefs. iconic default behavior.
• -b blocksize — the block-size flag in the 32vfs synopsis; the page calls out 512 byte block size (the default) and 1KB for pre-FFS Berkeley VAX systems. ✨

Now the format-by-format tea, bestie:

• 32vfs — interprets raw disk images of 32V systems, which are ca. 1978 research Unix systems for the VAX (512 byte block size, the default), and also pre-FFS Berkeley VAX systems (1KB block size). historical main character energy fr fr.
• cpiofs — interprets cpio tape images (constructed with cpio's c flag).
• tarfs — interprets tar tape images.
• tpfs — interprets tp tapes from the Fifth through Seventh Edition research Unix systems.
• tapfs — interprets tap tapes from the pre-Fifth Edition era.
• v6fs — interprets disk images from the Fifth and Sixth edition research Unix systems (512B block size).
• v10fs — interprets disk images from the Tenth Edition research Unix systems (4KB block size).
• zipfs — interprets zip archives (see gzip(1)).

🌈 SOURCE 🌈

These commands are constructed in a highly stereotyped way using the files fs.c and util.c in /src/cmd/tapefs, which in turn derive substantially from ramfs(4). the way that reusable architecture ate, honestly. 💅

🍓 SEE ALSO 🍓

• intro(7)
• ramfs(4)

and that's the page, bestie: TAPEFS(4) from the Kernel Interfaces Manual — no extra source/version or date line beyond that footer, periodt. 🎀