diff options
author | Ludovic Courtès <ludo@gnu.org> | 2022-01-16 15:51:13 +0100 |
---|---|---|
committer | Ludovic Courtès <ludo@gnu.org> | 2022-01-16 23:56:55 +0100 |
commit | 084b76a70a6b302529f3450e6d07f1d105a10f7d (patch) | |
tree | ba4369076caba3d6881a5a52ff5e0528393a4c8d /doc | |
parent | 86e782e2b6838fe425074c2b4758633ceefb639a (diff) |
machine: ssh: Add 'safety-checks?' field.
Fixes <https://issues.guix.gnu.org/52766>.
Reported by Michael Rohleder <mike@rohleder.de>.
* gnu/machine/ssh.scm (<machine-ssh-configuration>)[safety-checks?]: New
field.
(machine-check-file-system-availability): Return the empty list when
'safety-checks?' is false.
(machine-check-initrd-modules): Likewise.
* doc/guix.texi (Invoking guix deploy): Document it.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/guix.texi | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/guix.texi b/doc/guix.texi index 5d18e44f91..ea603ab56a 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -35682,6 +35682,16 @@ returned by @command{guix describe}) to determine whether commits currently in use are descendants of those deployed. When this is not the case and @code{allow-downgrades?} is false, it raises an error. This ensures you do not accidentally downgrade remote machines. + +@item @code{safety-checks?} (default: @code{#t}) +Whether to perform ``safety checks'' before deployment. This includes +verifying that devices and file systems referred to in the operating +system configuration actually exist on the target machine, and making +sure that Linux modules required to access storage devices at boot time +are listed in the @code{initrd-modules} field of the operating system. + +These safety checks ensure that you do not inadvertently deploy a system +that would fail to boot. Be careful before turning them off! @end table @end deftp |