fix(dmsquash-live): update documentation

Command line should have preference over image content driven
configuration when there is a conflict between the two.

Follow-up to 0e780720efe6488c4e07af39926575ee12f40339 .

diff --git a/man/dracut.cmdline.7.asc b/man/dracut.cmdline.7.asc
index f5afcbf6af7cd0f720e073343e21e3eb7e7b03d5..858991fa93cc20f62812dc13efb7d19b505c99db 100644 (file)
--- a/man/dracut.cmdline.7.asc
+++ b/man/dracut.cmdline.7.asc
@@ -1176,9 +1176,9 @@ device LABEL, and _<uuid>_ is the device UUID.
 * _none_ (the word itself) specifies that no overlay will be used, such as when
 an uncompressed, writable live root filesystem is available.
 +
-If a persistent overlay __is detected__ at the standard LiveOS path, the
-overlay & overlay type detected, whether Device-mapper or OverlayFS, will be
-used.
+If a persistent overlay __is detected__ at the standard LiveOS path,
+and rd.live.overlay.overlayfs is not set to 1, the overlay type (either
+Device-mapper or OverlayFS) will be detected and it will be used.
 --
 +
 [listing]
@@ -1233,9 +1233,6 @@ with ext4 and xfs.  On non-vfat-formatted devices, a persistent OverlayFS
 overlay can extend the available root filesystem storage up to the capacity of
 the LiveOS disk device.
 +
-If a persistent overlay is detected at the standard LiveOS path, the overlay &
-overlay type detected, whether OverlayFS or Device-mapper, will be used.
-+
 The **rd.live.overlay.readonly** option, which allows a persistent overlayfs to
 be mounted read-only through a higher level transient overlay directory, has
 been implemented through the multiple lower layers feature of OverlayFS.