GENKFS(1)
π¦ 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 π
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/linkto/var/target, you should make a link in yourmodelthat 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
- nixos 26.05: genkfs 1.3.2
- nixpkgs unstable: genkfs 1.3.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms