Or you can just avoid hacking your hosts file and breaking other tools, and set your Snap and Apt proxy configuration to a non-existent value, or firewall their ability to reach those hosts.
Or configure them properly by disabling auto-updates, configure unattended-upgrades appropriately for your needs, and only update your apt packages from a known, internal mirror endpoint that doesn't change until you point it to a new timestamp.
That's how it works in the real world, in production. It's not 1994, we don't hack hosts files anymore.
> I do have one of the VisionFive 2 boards, but I’m more interested in the Milk-V Oasis board that’s supposedly coming near the end of the year.
The Milk-V Oasis is out, but are you saying there's going to be another revision of that board?
I'm torn between the Lichee (7-node, 28 cores), the Milk (1 node, 64 cores), or the VisionFive 2.
If I was going to build out a lab for shared use across a number of engineers building packages and ci/cd for Linux, what would be the best option now, while we all wait for the hardware to improve in H2/2024?
Their Oasis [1] board is going to use SiFive's IP, the main cluster is 12 P P670 cores, and 4 E cores. There are also 8 X280 cores as an "NPU", also RISC-V but with a slightly different ISA.
Or configure them properly by disabling auto-updates, configure unattended-upgrades appropriately for your needs, and only update your apt packages from a known, internal mirror endpoint that doesn't change until you point it to a new timestamp.
That's how it works in the real world, in production. It's not 1994, we don't hack hosts files anymore.