NaN

Btrfs can send a snapshot to another machine, but there is no pretty gui for it.

Most file systems cannot do this.

Adding the nofail option to the fstab entry will continue boot if the drive isn’t present.

Vorta, Deja Dup (duplicity), duplicati are some others.

Btrfs is well supported.

Btrfs uses snapshots and subvolumes. It is not a traditional partition and can restore to itself.

I think Timeshift is primarily a snapshotting tool for a quick rollback if something breaks. I would not consider it a full backup tool, there are tools that are much more robust and configurable for keeping files safe and elsewhere.

That is for “Site-specific data served by this system” like /srv/www. Can mount anything anywhere of course.

They were defined sure, but without distribution adherence they weren’t actually, this has been the case for a long time. Out of all the distributions, Gentoo is probably one of the most sensitive to this issue since most others have used initramfs or initrd for decades and Gentoo has always made it optional.

If the post was about FHS adherence I’d agree more.

I don’t know if this is really a “so broken” instance. /bin and /usr/bin (or sbin) have never been well separated, to the point where many distributions just symlink to /usr anyway. If you don’t want an initramfs to provide binaries you need them somewhere accessible.

Newer kernels are available, they even have a gui for it. Why would a Cinnamon user care about KDE or GNOME updates? (Some of which are broken on Fedora, like rdp login)

Mint Debian can run 6.7 right now.

For stuff that is still maintained but also legacy, military and contracting benefit from being a pretty insular community. Contractors are full of military retirees. What this does is give a pool of people who worked with the products for a very long time on one side who move over into maintaining them on the other, less knowledge is lost. It still happens and things must change eventually, but they manage to delay things where someone else like a bank might have a harder time when their knowledgeable employee leaves and they’re hiring people off the street.

Red Hat has long benefitted from being the primary enterprise Linux company based in the US (no, we don’t count Oracle). SUSE created US-based Rancher Government Solutions to get some of that business and it seems to have been getting a lot of interest, despite being early days. They did a good job of focusing on modern technologies and immutable systems.

That’s also empty weight on the Learjet, gross weight is higher. This one is presumably that weight with the batteries so I suspect is smaller. Wish there were more details.

That is a clickable menu that explains exactly what the permissions are.

Firefox on flathub is an official one, that’s not what this warning is.

Clicking the potentially unsafe item lists the exact permissions.

It can access hardware devices, like your webcam or game controller. Likely --device=all in flatpak speak but I haven’t looked.

Neither has its own extension repository, so maintaining support enables side loading but isn’t all that useful for normal people or those who want their extensions to be up to date.

Brave shields work better than the built-in protection in Vivaldi, so it’s less of an issue there but still frustrating.

Yes, and they don’t develop Firefox (legally can’t) since they made a for-profit entity for that purpose.

The Mozilla Corporation does not accept donations.

Poorly written article with little substance but a zinger of a headline. Think they’re trying to take advantage of announcements of Intel and TPM security flaws in the past to get more clicks.

This is a UEFI firmware issue that can be patched by BIOS vendors. It is an issue at a very low level, but not an issue with Intel or the TPM.

The exploit is in the UEFI firmware code for handling the TPM and used for privilege escalation in that firmware, “TPM won’t save you” doesn’t really make sense because no shit. The vulnerability doesn’t mean the TPM unseals its contents though, and I’m curious if the exploit modifies the PCR values enough that OS security could trigger (Bitlocker recovery and whatever). Wouldn’t help if the malicious software was already there though.

“Breaking userspace” is often considered a bug even if the code doing so is working as intended. Deleting user data because they bundle a config file deep in the directory tree for a completely different use case was not intended behavior even if one of them is defensive about the logic.

Firefox just pulled the browser out of it to focus on one thing, Thunderbird did the same with communications. Seamonkey still does it all.