• 1 Post
  • 18 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle




  • Please let me know if you figure it out. I opted the detached header approach a few years ago because it had most of the same benefits without the headache and poor support. I’m wondering if it might be possible to replicate what Grub is doing as it us relatively trivial but that doesn’t mean easy. Basically you’d have a Secure Boot signed bootloader that is able to boot a protected file system (secondary /boot) where your kernel & initramfs, or combined image exists. This secondary boot partition can be a lot more flexible though so it could even read a sparse-baded file that has a file system stored in it, and then from there you’d unlock the second layer of encryption. My guess is it can be done using something besides Grub and you’d have full access to all the algorithms available under cryptsetup.



  • Sysv didn’t have to have a lot of documentation. It was simple to understand what it did, and the underlying system was mostly shell scripting. It didn’t try to be and do everything.

    I don’t hate systemd. I prefer it now for the most part. I really do think Lennart Poettering is incredibly skilled and intelligent. I am just frustrated that so much gets pushed without adequate resources and support to weigh what is production-ready, and what is bleeding edge. I’ve already had systemd bite me in the ass at least once where they made a significant unannounced change to systemd-cryptsetup. I had to go find answers by reading through pull request and GitHub issue comments, and it wasn’t easy to find either. The community acted like it wasn’t a big deal that it caused systems to no longer boot. Move fast & break things isn’t the message that will win over larger companies.




  • Windows permissions can be tricky… I’ll give them that. A lot of the tools Microsoft provides are not very straightforward.

    However, PowerShell and tools from Sysinternals suite, or open source tools as well, make it a lot easier.

    Managing permissions on Linux, especially if doing the ACL thing, can be complicated too. I’ve really never ran into many permission issues myself. psexec has been helpful too when needing to access things as the SYSTEM user and not get those stupid prompts asking me to change permissions for protected folders.





  • That’s rad… I have a set of Ansible playbooks/roles/collections already for most system-wide settings. I have a love-hate relationship with Ansible though, but it gets the job done. I may try for cloud-init first until I reach its limitations. I’ve gotten pretty good at the Arch install too, although setting up the disks with LUKS was the most challenging part. Fortunately, the few times I’ve broke things I’ve been able to boot the installer ISO and mount my LUKS volumes from memory, but I couldn’t tell you how I set them up in the first place. 🤣 However I do it, I really just want to automate the process so that I can add new nodes and expand should I decide to rent out colocation space someday.