README: mention why YAML was chosen

[safcm/safcm.git] / README.adoc

diff --git a/README.adoc b/README.adoc
index f120694f97abdfe5adbc728996efccee8d7be8b0..8f1684f0d6aed68ba41ae6e0da7fcb2441bf9d68 100644 (file)
--- a/README.adoc
+++ b/README.adoc
@@ -43,9 +43,10 @@ contains the files, packages, services and commands which should be applied to
 all hosts which are members of this group.
 
 The configuration of all managed hosts is stored in a directory on the local
-host. Safcm uses https://yaml.org/[YAML] for all configuration files. However,
-tasks like copying a file require no explicit configuration (see the
-documentation for details).
+host. Safcm uses https://yaml.org/[YAML] for all configuration files for its
+natural syntax. Strict type checks prevent potential pitfalls of more complex
+YAML syntax. Tasks like copying a file require no explicit configuration (see
+the documentation for details).
 
 Files consist of a tree of files (regular files and symbolic links) and
 directories with permissions, user/group and content. Files can use
@@ -135,6 +136,7 @@ future, others are due to the design of safcm.
     ** GNU/Linux with common commands (`uname`, `id`, `stat`, `sha512sum`,
        `cat`, `mktemp`, `rm`, `ln`, `chmod`)
     ** FreeBSD (same commands, but uses `sha512`)
+    ** OpenBSD (same commands, but uses `sha512`)
   * SSH server
   * to install packages:
     ** `apt-get` (Debian or derivative)