Revert "system: Add a 'needed-for-boot?' field to 'mapped-device'."

This reverts commit 3b09332adf7ce8e976a4d117a62c586a53af04aa, which
turned out to be a bad idea because we need to have dependency
information between the device-mapping service and the file-system
service that uses it.

1 files changed, 4 insertions, 12 deletions

diff --git a/doc/guix.texi b/doc/guix.texi
index 53bfb293b6..7c059b923a 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -3837,27 +3837,19 @@ detailed below.
 Objects of this type represent device mappings that will be made when
 the system boots up.
 
-@table @asis
-@item @code{source}
+@table @code
+@item source
 This string specifies the name of the block device to be mapped, such as
 @code{"/dev/sda3"}.
 
-@item @code{target}
+@item target
 This string specifies the name of the mapping to be established.  For
 example, specifying @code{"my-partition"} will lead to the creation of
 the @code{"/dev/mapper/my-partition"} device.
 
-@item @code{type}
+@item type
 This must be a @code{mapped-device-kind} object, which specifies how
 @var{source} is mapped to @var{target}.
-
-@item @code{needed-for-boot?} (default: @code{#f})
-This Boolean value indicates whether the device mapping must be made at
-boot time---i.e., from the initial RAM disk, before any user file
-systems are mounted.
-
-You would set it to @code{#t} for instance when the mapped device is
-used by the root file system.
 @end table
 @end deftp