floquant

Also if you have a fast internet connection, check out https://netboot.xyz/

Afaik the maintainer(s) have provided a reasonable explanation and cleared up the reproducible builds part

Just use the appropriate command for the hash type, i.e. sha256sum <filename> (iirc, might be wrong, man is your friend)

Huh, I guess that’s the same nutomic? Didn’t know that.

No I’m not using Kali for “hacking” I’m experimenting if I can play games on it

Sorry but… why on earth would you do that? Kali is a specialized distro, it’s not made for day to day desktop use, much less for gaming on it. If you want to game on Linux, pick either a generic or gaming-oriented distro, and use Kali in a VM or dualboot.

deleted by creator

I think the problem is NFS more than Gnome - even umount chokes on an unresponsive share

I’ve also seen GUI used (e.g. by QMK)

If the private keys have a passphrase they’re already encrypted. The fact that it’s a text file doesn’t mean it’s a plaintext file. But for improved security, you could use a Yubikey or similar hardware token.

What’s their angle? US companies can seemingly get a pass on copyright infringement if it’s for training AI. Why say that?

Pretty interesting, kudos to them for building a different system and not yet another distro. The end result of having a ton of pre-installed software in the hope that it covers your hardware and workflows makes it a pass for me as I’m all about being lightweight and modular, but it does seem like an almost perfect grandma distro.

The connection is that while the “system drive” (C:\ in Windows, / in Linux) for each system has its own partition, the EFI partition is shared. This is the partition where the files needed to load the respective OSes live, aka the entries you see in the bootloader. You could create a new EFI partition and tell Linux to use that one, but then you would have to select the OS from the boot devices in the BIOS, so no one does that.

Also is the fix to manually increase the size of that partition?

Well, yes, but the problem is that it’s at the start of the drive, usually. That means you can not expand it without moving the main Windows partition, which is a pretty bad idea (terrible on HDDs) as it’s prone to data loss. If your OEM put it at the end then you’re very lucky and it’s a quick operation, although it might require to delete some OEM-specific partition (which only serves to give you the branded wallpapers and bloatware if you factory reset from within Windows)

Honestly, if you don’t distrohop this shouldn’t be a problem. I had to do a stupid installation dance to have a 500MiB EFI partition, but I was motivated to do it because:

1. I hate Microsoft
2. I wanted to fuck around with kernels, bootloaders, and distros

No one mentioned this yet, but a possible issue is that Windows, for some damn reason, still creates a 100MiB EFI partition, although by EFI spec It should be at least 256 iirc

This can cause the /boot/EFI partition to fill up. Some distros/bootloader are more affected than others, but I’ve had it happen a couple of times

So you’re suggesting running a kneecapped system over USB rather than reinstalling grub twice a year?

A legitimate backdoor is still a backdoor. If you have security measures and a way to bypass them, you don’t have security measures.

deleted by creator

Storing files encrypted and decrypting them on-demand is called “encryption at rest”. Linux supports it but is not enabled by default. You can also encrypt /boot to get FDE (Full Disk Encryption) to ensure that the kernel or bootloader is not tampered with. Look into LUKS

Should be, but why?

You don’t need to change drivers strictly, just add the new ones then remove the old ones later. It’s just to avoid having issues with display output on your first boot - although you should pretty much always get some video out even without the correct drivers

If you’re switching vendors it’s not a bad idea to install the drivers beforehand. Otherwise no, just swap & cable.