brent /etc/crypttab is specified in the Kernel documentation. All Linux Distros should comply with Kernel specific configuration files, etc. Yeah, I understand that Solus does things its own way, and that's okay. It becomes a problem when the OS doesn't get out of my way and let me take over. While Solus does use clr-boot-manager to manage the boot loader, under the hood it is merely Systemd-Boot (kudos for all the work on the boot manager too guys, as I can see the intent of making Systemd-Boot easier to understand). Thus, I can unify one Boot manager to handle booting both Linux Distros. I can use either the version of Systemd-Boot in Arch's repos or the version in Solus' repos... I choose Arch because it is simpler for me to work with simply because it is a system I know and understand and I am lazy and do not want to have to relearn managing another boot system. At this point, however my actual problem is twofold:
1) Either it's a bug or a feature, but the installer that Solus uses doesn't properly recognize LVM partitions on a decrypted drive. I went into the terminal upon booting Solus' live installer and ran the commands to decrypt both my root drive and my home drive. None of the LV partitions showed up in the installer. Only my ESP partition showed up. I tried several things to get this to work. Eventually I settled on installing Solus like Windows and backed up my /home drive just in case, and let it overwrite the whole drive. Then I went back in with an Arch ISO and resized and renamed the LV Solus created (because I didn't like the name the installer gave it), created a new LV for Arch, and proceeded to install Arch again.
2) This created two major problems. First I renamed the "root" logical volume. At this stage I also gave the partition with Solus' root filesystem on it a blkid label because I like using labels on my drives, and updated Solus' version of /etc/fstab accordingly after creating a backup of the old version. Second I deleted the Swap partition that Solus created for two reasons: first I already had one on my "home" SSD, and secondly I have that one on the "home" SSD because it is a larger one and I intend to store two root filesystems on the "root" SSD... hence the need to not use a Swap partition on that drive.
I also created a tarball backup of the Solus Boot Filesystem while installing Arch. I used that to configure Systemd Boot and I have gotten everything to work up until the point of decryption (for the record, Arch boots completely). I can type my decryption password in, but then nothing happens. Either it isn't finding the newly named root logical volume, the new location of the Swap partition, or it isn't decrypting the "home" drive as specified by /etc/crypttab.
There's still a problem with conflicting boot managers, as Solus might overwrite my configuration files for Systemd-boot and/or install a different version of Systemd-Boot than what I am currently using, but I can deal with that later. Sorry if I came off as hostile or anything. That wasn't my intention.
