There is a difference here.

Unlocking home later in the boot process is not a problem, so the you can indeed have a keyfile on your root and get your home unlocked and mounted after root is done.

Swap however needs to be available early, at least if you want to use it for hibernation.

This would -at least as far as I understand it- limit your swap’s functionality for hibernation etc. Because there your swap needs to be available early. You can still do it in theory, but the key file then would need to be included in you initrams, which kind of defeats the purpose.

There is however a much more easier option: either use LVM on luks (so the volume is decrypted with the password and then contains both, root and swap) or just use the same password for root and swap while switching over to the systemd hooks (as those encryption hooks try unlokcing everything with the first provided password by default, and only ask for additional password if this fails).

EDIT: Seeing that you crossposted this from an archlinux-specific community: You can find the guide here. It’s for using a fully enrcypted system with grub as bootloader, but the details (in 8.3 and 8.4) are true for all boot methods. Replace the busybox hooks with their systemd equivalents (in minitcpio.conf for archlinux but again this isn’t limited to that init system), then add “rd.luks.name=<your swap’s uuid=swap” to your kernel parameters and also replace the “cryptdevice=UUID=<your root’s uuid>:root” that should already be there for an encrypted system (that’s the syntax for the busybox hook) with “rd.luks.name=<your root’s uuid>=root”. On startup you will be asked for your password as usual, but then both root and swap will be decrypted with it (PS: the sd-encrypt hook only tries this once… so if you screw up and misstype your password on the first try, you will then have to type it again two times, once for root, once for swap…)

And just lke with the war on drugs, countries will realize it’s a lost cause. And will then instead try to coopt the system to spread their own desinformation. If you can’t win, exploit it for your own gains…

Welcome to our wonderful post-factual age.

Cuddling up to the hard right might look like a strategical move but it never works. Normalising them only shifts the discussion further to the right. And let’s face it… in this post-factual time where all that matters is the narratives, giving them a platform will only help to brain-wash more people into believing right-wing fake-solutions to actual problems.

No… the Crowdstrike debacle primarily shows the dangers of today’s corporate culture in software development.

Ship as fast as possible, fix issues later if necessary…

The software is the problem if it’s produced with a corporate mentality of “ship first, fix later”.

It’s the other way around. All those PCs are bluescreening at boot. So that prevents fixing the system remotely and on a large scale. Now poor IT guys have to fix evey single one by hand.

Dual booting with Windows is always a pain, because Windows likes to nuke and replace your boot menu. The safest bet is keep Windows strictly separated: You create a 2nd efi system partition on your second drive with linux, use a boot loader there and then set everything up to start that as default. And then you configure the boot loader to chainload windows from it’s own ESP on disk one. This way Windows is oblivious about linux systems it might try to damage. And you can then set the boot loader menu to a default or to default to the last system booted. (2 separate ESPs on on disk might work, but that is not supported by UEFI, so it depends on your hardware’s implementation if they are recognized or if it just stops after having found the first…).

I would assume what you did was install the Linux boot loader (efi file) as the default like removable drives do (so grub’s efi file installed as esp/EFI/BOOT/BOOT64.efi which is the default for removably drives to take priority; done via grub-install with the --removable flag, some installations might use this by default…)

Zen Kernel is the opposite of “optimized for gaming”.

It was once the default kernel for out-of-the-box gaming simply because it had fsync patches integrated. But since fsync is in the normal kernel for quite some time now zen is obsolete for that purpose.

I mean it’s still an okay choice for any desktop environment but it is definitely not optimized for gaming as it sacrifices throughput and is more tailored to multitasking of a lot of smaller things running to provide a snappy desktop experience.

Doing that improved performance for Windows apps on Linux when using Wine or Valve’s Proton that is based on the former. […] benchmarks that show games running better with average improvement rates ranging from 50% to 150% when using the new driver compared to not using it.

Talking about improvements for Wine and Proton then providing no actual data for Proton (which is already using a completely different mehod for syncs - yes the basic wine method sucks) is either stupid or intentionally misleading.