Home Explore Blog Models CI



nixpkgs

nixos/doc/manual/administration/system-state.chapter.md
89ce2762c7f3dfafde428b7a9ddf8bbbecb03019e2b65550000000030000023c
# Necessary system state {#ch-system-state}

Normally — on systems with a persistent `rootfs` — system services can persist state to
the filesystem without administrator intervention.

However, it is possible and not-uncommon to create [impermanent systems], whose
`rootfs` is either a `tmpfs` or reset during boot. While NixOS itself supports
this kind of configuration, special care needs to be taken.



```{=include=} sections
nixos-state.section.md
systemd-state.section.md
zfs-state.section.md
```

Chunks
160ef414 (1st chunk of `nixos/doc/manual/administration/system-state.chapter.md`)
Title: Necessary System State on Impermanent Systems
Summary
This section discusses the challenges of persisting system service state on "impermanent systems," where the `rootfs` is either a `tmpfs` or resets during boot, unlike conventional systems with a persistent `rootfs`. While NixOS supports such configurations, it necessitates special attention to state management. The text indicates that subsequent sections will delve into how NixOS, systemd, and ZFS handle state in these environments.