It is however more of a mitigation for bad distro installers than general good practice. If the distro installers preserved /home, you could keep it all in one partition. Because such “bad” distro installers still exist, it is good practice if you know that you might install such a distro.
If you were installing “manually” and had full control over this, I’d advocate for a single partition because it simplifies storage. Especially with the likes of btrfs you can have multiple storage locations inside one partition with decent separation between them.
This is a lot to take in; it’s basically an overview of all the interesting features of Nix. When starting out, you don’t need this kind of in-depth knowledge. I personally gathered most of what was covered here in over 6-12months of using it and I did just fine.
It might still not be for you but don’t take this as the reference point.
Yes, a slight speed decrease is expected even with good proxy services at common residential speeds. Given that yours is far above the average, a greater decrease can be expected. It shouldn’t be this much though.
If this is installed on a common “router” SOHO gateway appliance, it’s likely that its hardware is simply not able to keep up with the tunnelling workload (encryption, package handling). For troubleshooting, try the same proxy server on a more powerful machine while disabling the proxy on the gateway. If it’s faster, that’s likely your issue.
Also try a different proxy server. That particular one might simply not have enough capacity to serve you more than that.
meaning every step of building the kernel, including the steps taken to build the C compiler toolchain, are produced by code that is simple enough to check for correctness and safety.
Full-source bootstrap isn’t about just the kernel, it affects every piece of software. With GUIX and Nix, every single package can be fully traced back to the bootstrap seed.
Though it should be noted that you do require a running Linux kernel on an x86 machine in order to bootstrap.
it is not quite to the point where it /just works/ on a lot of the computer hardware that I own.
Unless we get some serious money, effort and/or regulation w.r.t. OSS firmware, that will likely never be the case.
That has nothing to do with its technology though, that’s a political issue. GUIX is a GNU project and acts like proprietary software does not exist/is not a basic necessity in 2023.
Ah I think Windows does this “helpful” thing where it installs its bootloader into the ESP of any drive if it’s already present rather than the drive you explicitly told it to install onto.
You didn’t have anything in it yet, right? Unplug all other drives and then re-install Windows onto the drive. It should work as expected after that.
IIRC Pop!_OS sets the systemd-boot timeout super short; you have to hold a key after the firmware is done or something to get to it reliably or simply increase the timeout (1s is enough, I have it set to that on my systems). systemd-boot should give you the option to boot any windows installation though, it can auto-detect them.