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 to 1, the command will skip adding a number of toplevel "API filesystems" such as /proc to 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