stuner
If you don’t want to reinstall the OS, you can probably use Clonezilla: https://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live/doc/03_Disk_to_disk_clone
Maybe you need to update the drive ids for your bootloader (grub) afterwards, not sure about that.
Edit: Maybe the advanced “-g auto” option does that for you.
It seems that 18.04 was the last release for 32-bit x86 (i386): https://askubuntu.com/questions/1376090/latest-version-of-ubuntu-for-i386-architecture-32-bit
But you could just go for Debian which still supports it.
I do think it can achieve that while waiting for network packets (see e.g. https://www.anandtech.com/show/16252/mac-mini-apple-m1-tested).
But in terms of money savings it would rarely make sense, as you need to make it back during the time you run the system. If we assume 6 years lifetime then it would only make sense to pay $120 more. But yes, I’d also go for a system that runs regular Linux :)
I don’t have one (and I don’t want one), but Anandtech measured the M1 version at 4.2W in idle. https://www.anandtech.com/show/16252/mac-mini-apple-m1-tested I think you can also get that from other Mini PCs (e.g. NUCs).
I would disagree with idle power not being important for a home server. Most of the time, your system will be doing very little and wait for something to happen. I also don’t think a typical server has a display attached. Wolfang explains this quite well: https://youtu.be/Ppo6C_JhDHM?t=94&si=zyjEKNX8yA51uNSf
I don’t have a Mac Mini, but for always-on systems, the idle power consumption can become quite significant.
- Gaming PCs can consume up to 100W (876 kWh / year).
- My AMD B650 NAS consumes about 17W in idle (150 kWh / year).
- A NUC / Mac Mini can idle as low as 5W (44 kWh / year).
If you pay 0.30$/kWh, running your old 100W gaming PC all the time would cost you 263$ per year. My NAS is 45$ per year…
It also depends on what you need/want from the machine. The Mac Mini doesn’t have any HDDs and can’t run a regular Linux distro, for example.
This seems very one-sided. Sure, the disclosure was not handled perfectly. However, this post completely ignores the terrible response by the CUPS team.
The point on NAT is certainly fair and prevented this from being a much bigger issue. Still, many affected systems were reachable from the internet.
Lastly, the author tries to downplay the impact of an arbitrary execution vulnerabilty because app armour might prevent it from fully compromising the system. Sure, so I guess we don’t need to fix any of those vulnerabilities /s.
This article is conflating terms that I need help distinguishing between. The other commenter mentioned that Ubuntu is a type of Debian but this article lists Debian and Ubuntu as distributions.
I’d say that the article is correct in calling them separate distributions.They are certainly related (both part of the Debian family), but I think most people would consider them to be separate distributions. Software built for Ubuntu 24.04 may work on Debian 12, but it might also not. For a beginner, I think it’s most useful to consider them to be separate things.
It sounds like a weird idea at first, but maybe it could actually work. Kind-of like running two trains on top of each other instead of after each other. I guess the downside would be the need for bespoke rolling stock and larger platforms. I think, it would generally be preferable to double the frequency or run longer trains. But it could be interesting if you’ve already exhausted those.