From 85c1c30fd9ab350ad254736d0950d07639b9f6e8 Mon Sep 17 00:00:00 2001 From: Janne Heß Date: Wed, 13 Sep 2023 18:22:12 +0200 Subject: nixos/switch-to-configuration: Never unmount / or /nix Also adds a huge test for fstab handling --- .../development/what-happens-during-a-system-switch.chapter.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'nixos/doc/manual/development') diff --git a/nixos/doc/manual/development/what-happens-during-a-system-switch.chapter.md b/nixos/doc/manual/development/what-happens-during-a-system-switch.chapter.md index 9cbec729803..5d6d67f1aa9 100644 --- a/nixos/doc/manual/development/what-happens-during-a-system-switch.chapter.md +++ b/nixos/doc/manual/development/what-happens-during-a-system-switch.chapter.md @@ -21,8 +21,9 @@ If the action is `switch` or `test`, the currently running system is inspected and the actions to switch to the new system are calculated. This process takes two data sources into account: `/etc/fstab` and the current systemd status. Mounts and swaps are read from `/etc/fstab` and the corresponding actions are -generated. If a new mount is added, for example, the proper `.mount` unit is -marked to be started. The current systemd state is inspected, the difference +generated. If the options of a mount are modified, for example, the proper `.mount` +unit is reloaded (or restarted if anything else changed and it's neither the root +mount or the nix store). The current systemd state is inspected, the difference between the current system and the desired configuration is calculated and actions are generated to get to this state. There are a lot of nuances that can be controlled by the units which are explained here. -- cgit 1.4.1