📄️ Bootloader Configuration
<!--
📄️ Clean Install Safety Check
When trident install is invoked, Trident ensures that it is running from either ramdisk or live media. This is an important safeguard and keeps Trident from overwriting the operating system that Trident is running in.
📄️ Deployment Chroot
<!--
📄️ Host Configuration Validation
The Trident binary can validate the syntax and structure of a Host Configuration
📄️ How Trident Consumes COSI
Trident uses a Composable Operating System Image (COSI)
📄️ How Trident Knows What to Do
<!--
📄️ Install Flow
Install Flow
📄️ Limitations of NTFS
Background
📄️ Multiboot
<!-- tl;dr for the first PR
📄️ Network Configuration
<!--
📄️ Offline Initialize
To enable update, Trident requires some state related to how an existing operating system is laid out on disk.
📄️ Operations
<!--
📄️ Partition Adoption
When Trident installs or services an operating system, there are times when
📄️ Rebuild RAID
RAID and Rebuild-RAID
📄️ Root-Verity
Root data integrity verification, or root-verity, is a specific utilization
📄️ SELinux Configuration
SELinux is an access control system on
📄️ Script Hooks
Trident allows for users to run [custom
📄️ Trident Architecture
<!--
📄️ Usr-Verity
Usr data integrity verification, or usr-verity, is a specific utilization