OSTREE-ADMIN-INIT-FS(1)
bestie, you're reading OSTREE ADMIN INIT-F(1) β the manual page for ostree admin init-fs, and it's giving βfresh root filesystem, who dis?β πβ¨
πΈ NAME πΈ
ostree-admin-init-fs β initialize a new root filesystem. yes, the whole root filesystem, not just a vibe π
β¨ SYNOPSIS β¨
ostree admin init-fs [OPTIONS...] {PATH}
π¦ DESCRIPTION π¦
okay so this command initializes an empty physical root filesystem in the designated PATH, with normal toplevels and correct permissions for each directory. it's primarily useful for operating system installers. periodt. β¨
π OPTIONS π
--modernβ equivalent to--epoch=1. slay, no notes π--epochβ this accepts an integer value in the range[0-1], inclusive. the default is zero for compatibility, bestie. when set to1, the command will skip adding a number of toplevel "API filesystems" such as/procto the toplevel of the physical root. these should be unnecessary, as they should only be mounted in the final deployment root. the main exception is/boot, which may need to be mounted in some setups before the target root. π₯Ύ
Epoch 2 is the same as 1, except that the toplevel ostree directory is mode 0700, denying access from unprivileged code. this is a new recommended best practice as it avoids access to old configuration files in /etc in previous deployments, as well as potentially old setuid binaries in /ostree/repo. highkey important, no cap πβ¨
π EXAMPLE π
like this, bestie:
$ mkdir /example
$ ostree admin init-fs --epoch=1 /example
$ ls /example
boot
that's the whole page, bestie π«Ά source/version: OSTree Β· manual: OSTREE ADMIN INIT-F(1) Β· date: whatever your copy's footer says (this one didn't show a date, no cap) π
π
π¦ where this page comes from
- arch rolling: ostree 2026.6-1 Β· LGPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms