GENKFS(1)

πŸ“¦ version 1.3.2, in nixos 26.05, nixpkgs unstable

πŸ¦‹ NAME πŸ¦‹

genkfs β€” Writes KFS filesystems into ROM dumps. Yes bestie, this is the GENKFS(1) page πŸ’–

✨ SYNOPSIS ✨

genkfs input model

πŸ’… DESCRIPTION πŸ’…

input is the ROM file you would like to write the filesystem to. model is a path to a directory that will be copied into / on the new filesystem. That's the whole main-character setup, no cap.

Symbolic links are supported but they have special constraints, bestie. Instead of making symlinks that make sense in the context of your model filesystem, make symlinks that make sense in the context of the final filesystem.

So if you want the resulting filesystem to have a symlink from /var/link to /var/target, you should make a link in your model that points to /var/target β€” even if your local filesystem does not have anything interesting at /var/target. This is where you gotta think in final-filesystem brain 😭

In other words, to make the final filesystem have that link from /var/link to /var/target, run this command on model/:

ln -s /var/target model/var/link

🌈 EXAMPLES 🌈

genkfs input.rom ./temp

Creates a KFS filesystem in input.rom and copies the contents of ./temp to the root of the new filesystem. Slay, that's the example.

πŸ‘‘ AUTHORS πŸ‘‘

Maintained by Drew DeVault <sir@cmpwn.com>, who is assisted by other open source contributors. For more information about genkfs development, see https://github.com/KnightOS/genkfs.

okay bestie, that's the whole page β€” this was GENKFS(1), dated 01/01/1980 πŸ’–

πŸ“¦ where this page comes from