No, they’re almost entirely unrelated. Almost all CPUs will idle close to 0 W (with correctly working drivers). The main idle power contribution comes from the mainboard and other devices (e.g. disks). The Mini PCs you mentioned should have a very low total idle power, probably below 10W.

Check out Wolfgang on YouTube, he has some great videos on the topic: https://youtu.be/Ppo6C_JhDHM

I’ve also recently built my own NAS and I’ve gone through similar considerations. One of my mayor decisions was not to use btrfs because it’s not recommended for Raid Z1/Raid 5. With that, I landed on ZFS and TrueNAS Scale. Note that RAID expansion should be landing in both very soon.

Things with TrueNAS were pretty easy, very quick, and everything worked nicely. However, I noticed that it was constantly accessing the disks and preventing them from spinning down. I really wanted to keep the power consumption low (<20 W idle), so I eventually decided to just go with Vanilla Debian + ZFS. I can recommend that if you want to tinker with things yourself. Otherwise, I’d recommend TrueNAS Scale.

As for migration, you might be able to create a degraded pool initially, copy over the data, and add the parity disk last. Raid expansion would ofc also help there…

What kind of junk energy is there to harvest from a car (in meaningful amounts)? I guess breaking is the obvious answer, but that’s already covered by regenerative breaking. Most car-based energy harvesting systems seem to employ speedbumps that clearly take useful (kinetic) energy away from the car (probably at a very poor efficiency).

How would a turbine that takes energy from the air current generated by a passing car decrease the energy of the car?

Not sure where you got that idea from, but how would that generate a meaningful amount of energy? It seems very unlikely that such a system would ever recover the energy spent on its construction.

Sure, but those are completely different approaches. Dams have the advantage that they have a much larger capture area for water and that they can accelerate the water beyond the 10 m/s terminal velocity of raindrops.

Raindrop energy harvesting is a rubbish idea. The raindrops simply don’t have a meaningful amount of energy to begin with: https://news.ycombinator.com/item?id=36907674

Did you perform a full shutdown of Windows (Windows doesn’t fully release the partition on a normal shutdown)?

The driver should already be installed but there seems to be an issue with brltty registering the corresponding USB ID when they shouldn’t. You can probably fix it by following this guide: https://koen.vervloesem.eu/blog/how-to-stop-brltty-from-claiming-your-usb-uart-interface-on-linux/ (or this one: https://unix.stackexchange.com/a/670637)

Edit: Perhaps this has since been fixed in Mint 21 / Ubuntu 22.04.

You can make this work using ext and Timeshift rsync. I have also opted to exclude /var/lib/flatpak/ because it’s quite large. With that, my 5 snapshots currently take up about 34 GB.

However, I would recommend backing up your deb applications/packages (typically installed under/usr), as those can be critical for your system.

This “new law” was passed more than a year ago… But, it’s still a step in the right direction.

One way to do it is have a small Python (or any other scripting language really) script that performs text replacements in the Latex source file. This is much easier in Latex because it’s plain text. I don’t know of a solution that doesn’t involve writing your own code (apart from LO/Word serial letters).

Is using Latex an option? I’ve done that and it works quite nicely. You can easily populate a template e.g. using Python.

That looks like a software issue… I would try a different distro or a different version of Ubuntu (e.g. 22.04).

Did you do anything special to install Fedora it on the USB drive? I couldn’t get it to do that and would be interested in testing F40 that way.

Ah, that would put a bit of complication into things. If you want to actually accomplish this though, you should largely start with the same steps as a standard system install, using a second USB flash drive to write the distro onto the external SSD, leaving enough space to build the rest of the partitions you need.

I’ve actually tried to install Fedora on an USB SSD to play around with it. But somehow the installer just refused to select the second USB drive as an installation target. I looked for quite some time but couldn’t find a way to do it. I ended up trying to install it manually like Arch (for fun), but never got a bootable system 😅 I was able to install Arch and NixOS on the same drive without issue.

I’m actually not sure how OP could achieve something close to what they’re looking for… A regular installation certainly seems like the right choice, but that may require using an internal drive.

Yeah, NTFS being the problem actually makes a more sense.

OP could also just use the fuse driver then. I’m using it on 5.15 (Linux Mint) and it works quite well. I only had problems when I tried to use it for a Steam library.

You could also try to switch the kernel version. Ubuntu 22.04 currently supports two different versions: 5.15 and 6.5, you could switch to the other one and see if the problem also occurs there.

Makes sense.

No, I wish for something like Alma, but declarative and atomic :)

What do you miss in NixOS (Unstable)?

I think a declarative, atomic LTS distro (e.g. Alma) would be quite nice for business use.

That looks quite weird… RHEL 9.2 was patched in February. RHEL 7 and RHEL 8 have now been patched too, but RHEL 9 (9.3) is still vulnerable?