rd.znet=ctc,0.0.0600,0.0.0601,protocol=bar
--
+OverlayFS
+~~~~~~~~~
+Requires the dracut 'overlayfs' module.
+
+**rd.overlayfs=**1::
+Enables the use of the *OverlayFS* kernel module, if available, to provide a
+copy-on-write union directory for the root filesystem. OverlayFS overlays are
+directories of the files that have changed on the read-only base (lower)
+filesystem. The root filesystem is provided through a special overlay type
+mount that merges at least two directories, designated the lower and the upper.
+If an OverlayFS upper directory is not present on the boot device, a tmpfs
+directory will be created at `/run/overlayfs` to provide temporary storage.
+Persistent storage can be provided on vfat or msdos formatted devices by
+supplying the OverlayFS upper directory within an embedded filesystem that
+supports the creation of trusted.* extended attributes and provides a valid
+d_type in readdir responses, such as with btrfs, ext4, f2fs, & 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.
++
+The **rd.overlayfs.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.
+
Booting live images
~~~~~~~~~~~~~~~~~~~
Requires the dracut 'dmsquash-live' module.
This shortage could be remedied by building the root filesystem with more
allocated free space, or the OverlayFS based overlay mount method can be used.
-When the *_rd.live.overlay.overlayfs_* option is specified or when
+When the *_rd.overlayfs_* option is specified or when
*_rd.live.overlay=_* points to an appropriate directory with a sister at
`/../ovlwork`, then an OverlayFS based overlay mount is employed. Such a
persistent OverlayFS overlay can extend the available root filesystem storage
by the **root=**live:__<path|url>__ device.
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
+and *_rd.overlayfs_* is not set to 1, the overlay type (either
Device-mapper or OverlayFS) will be detected and it will be used.
--
+
that memory is given back to the kernel when the filesystem does not claim it
anymore.
-**rd.live.overlay.overlayfs=**1::
-Enables the use of the *OverlayFS* kernel module, if available, to provide a
-copy-on-write union directory for the root filesystem. OverlayFS overlays are
-directories of the files that have changed on the read-only base (lower)
-filesystem. The root filesystem is provided through a special overlay type
-mount that merges at least two directories, designated the lower and the upper.
-If an OverlayFS upper directory is not present on the boot device, a tmpfs
-directory will be created at `/run/overlayfs` to provide temporary storage.
-Persistent storage can be provided on vfat or msdos formatted devices by
-supplying the OverlayFS upper directory within an embedded filesystem that
-supports the creation of trusted.* extended attributes and provides a valid
-d_type in readdir responses, such as with btrfs, ext4, f2fs, & 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.
-Requires the dracut 'overlayfs' module.
-+
-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.
-Requires the dracut 'overlayfs' module.
-
-
ZIPL
~~~~
Requires the dracut 'zipl' module.
EXT_KEYMAP:: vconsole.keymap.ext
+rd.live.overlay.overlayfs:: rd.overlayfs
+
+rd.live.overlay.readonly:: rd.overlayfs.readonly
+
Configuration in the Initramfs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_/etc/conf.d/_::
getargbool 0 rd.live.ram && live_ram="yes"
getargbool 0 rd.live.overlay.reset && reset_overlay="yes"
-getargbool 0 rd.live.overlay.readonly && readonly_overlay="--readonly" || readonly_overlay=""
+getargbool 0 rd.overlayfs.readonly -d rd.live.overlay.readonly && readonly_overlay="--readonly" || readonly_overlay=""
getargbool 0 rd.live.overlay.nouserconfirmprompt && overlay_no_user_confirm_prompt="--noprompt" || overlay_no_user_confirm_prompt=""
overlay=$(getarg rd.live.overlay)
getargbool 0 rd.writable.fsimg && writable_fsimg="yes"
[ -z "$overlay_size" ] && overlay_size=32768
getargbool 0 rd.live.overlay.thin && thin_snapshot="yes"
-getargbool 0 rd.live.overlay.overlayfs && overlayfs="yes"
+getargbool 0 rd.overlayfs -d rd.live.overlay.overlayfs && overlayfs="yes"
# Take a path to a disk label and return the parent disk if it is a partition
# Otherwise returns the original path
ROOTFLAGS="$(getarg rootflags)"
if [ "$overlayfs" = required ]; then
- echo "rd.live.overlay.overlayfs=1" > /etc/cmdline.d/20-dmsquash-need-overlay.conf
+ echo "rd.overlayfs=1" > /etc/cmdline.d/20-dmsquash-need-overlay.conf
fi
if [ -n "$overlayfs" ]; then