xyguy

There are several things like that in Fedora, which is already a good reason not to recommend it to first timers. They most likely won't know or care about nonfree codecs, they will just see a broken machine. Linux Mint understands that as a use case and has a "magic make it work" checkbox during install.

That all being said, I run Nobara and love it, but i wouldn't recommend it for new people.

I don't have a ton of faith in tplink to continue to support omada over the long term. They've also been somewhat slow to fix security problems in the past. For the same price as the omada ap you can get unifi u6 lites.

You can still run your own controller and i can vouch thaf a couple of them can cover an entire moderately sized house. I run 2 at home with pfsense on an ewaste tier dell optiplex and have for years without trouble.

I've never messed with opnsense but I assume it works just as well.

Also what type of connection are you getting from your ISP? If its a fiber connection you may be able to buy an SFP network card and replace the modem altogether.

You are correct that this is technically in code and would protect against shock hazards in a neutral error situation but you also get the opportunity for the outlet to pop during the day when nobody is home and the battery to die.

We had a situation in our old house where someone who was technically correct but didn't think it through had a gfci outlet upstream of the refrigerator outlet. Thankfully it popped while someone was home and we got everything corrected before we lost everything in the fridge.

They would most likely still have to disable secure boot.

1. The order doesnt matter as long as they are the same drives, you dont have a usb dock or raid card in front of them (ie sata/sas/nvme only)and you have enough of them to rebuild the array. Ideally all of them but in a dire situation you can rebuild based on 2 out of 3 of a Raid Z1

2. You can do that, you shouldn't but you can. I've done something similar before in a nasty recovery situation and it worked but don't do it unless you have no other option. I highly recommend just downloading the config file from your current truenas box and importing it into a fresh install on a proper drive on your new machine.

3. Sort of already mentioned it but you can take your drives, plug them into your new machine. Install a fresh Truenas scale and then just import the config file from your current setup and you should be off to the races. Your main gotcha is if the pool is encrypted. If you lose access to the key you are donezo forever. If not, the import has always been pretty straightforward and ive never had any issues with it.

4. Lots of people virtualize truenas and lots of people virtualize firewalls too. To me, the ungodly amount of stupid edge cases, especially with consumer hardware that break hardware passthrough on disks (which truenas/zfs needs to work properly) is never worth it.

That would lower the barrier to entry significantly. It doesn't address the issues with the bios but someone mildly adventurous would have a much easier time going forward.

I think something like that would have to be sponsored by and maintained by a big distro though. I'm afraid if it was a community effort the amount of bikeshedding would stop it before it even began.

Linux pre installed is the only way for most people to use it I'm afraid.

Fedora does btrfs snapshots on boot also, which is such a great feature that I'm surprised Microsoft hasn't copied it for Windows.

This is definitely the case. And by the time someone is willing to experiment with their PC its so old that the experience with Linux is hampered by the older hardware.

Definitely. I can genuinely say that the autotiling in PopOS completely changed my workflow for the better.

Absolutely. If Linux was pre installed that's what people would use. Its the switching to Linux from something else that proves so complicated.

Mostly just so they know which boot device to pick.

Admittedly that's probably not necessary or the least of someone's issues.