The following options can be added to the kernel command line to control the behavior of Citadel at boot. Most of them are intended for development, testing or installation and are not needed for normal operation.
citadel.noverityMount resource images and the root filesystem without dm-verity integrity checking, and skip verification of image header signatures. The root filesystem can then be remounted read-write in order to modify it (see the Developer Guide).citadel.nosignaturesSkip verification of the signature on image headers. Unlikecitadel.noverity, dm-verity is still enforced, so images remain mounted read-only with per-block integrity checking.citadel.installBoot into the installation environment instead of a normal desktop session. The system runs live from the installation media without setting up LVM volumes or disk partitions, and the graphical Citadel installer is started.citadel.overlayMount a tmpfs-backed overlay filesystem over the read-only root filesystem. Any changes made to the root filesystem are written to memory and disappear on reboot. This allows experimenting with the system configuration without disabling dm-verity or modifying the disk.citadel.channel=name[:pubkey]Select the channel from which resource images are loaded, for examplecitadel.channel=dev. If a hex-encoded public key is supplied after the channel name, it is used to verify image signatures for that channel, allowing images signed with a different key to be installed.citadel.verboseEnable informational logging for the Citadel boot tools.citadel.debugEnable debug-level logging for the Citadel boot tools. This is the most verbose logging level.citadel.swayHistorically this option started the Sway tiling window manager session instead of GNOME. The session switcher which implemented it has been removed from recent versions of Citadel, so this option currently has no effect.