Edit: Probably try @nanook@friendica.eskimo.com's solution of systemctl daemon-reload first.
Yes. When booting, your system has an initial image that it boots off of before mounting file systems. You have to make sure the image reflects the updated fstab.
Borg with Vorta’s my go to as well. Resistance is futile.
Did you update your initramfs after? The new fstab doesn’t apply until you refresh that
I find that I’ll do the bare minimum in GIMP (like that one healing extension), and then I’ll copy what I have over to Inkscape to do the rest.
The filter preview feature seems really nice!
Honestly, Inkscape is at the very least almost as good as Illustrator - call me deluded but I find more intuitive in many cases.
Now if only GIMP could actually have some money pumped into it and a sane UI… 😒
How are you guys pronouncing this?
Personally, I’ve found it sounds kind of nice when said like “Loon tea”.
That’s why I’m starting to prefer LTSC.
I think distros at least do some stuff beyond repackaging the latest software, namely default configurations (or lack thereof).
For instance, technically Debian has the packages to do SELinux, but it's Fedora (and OpenSUSE, I think?) that actually come out the box with them.
They are also continually improving, if slowly, their package managers to improve the experience of sourcing new software, as seen with work on apt and dnf.
You are right overall that new distro releases have little meaning any more. If anything, I think they are a good method for managing the upgrades to new software; when a release comes out, breakages can be addresses all at once and solved for a couple of years, whereas rolling release requires a person to be vigilant and repair breakages more often. That is not to pan rolling - I use Debian Testing on my desktop. As much as I like newer software, though, I am thinking of staying on Trixie after it becomes stable, as I get tired of applying updates all the time and then something breaking that is incredible difficult to diagnose.
Yeh, something is borked with your network settings. The port that's connected seems to be trying to connect over IPv6, but unless you're doing something weird, it should be IPv4 It should be in your network settings GUI.
If ip a shows your NIC, I'd recommend checking your networking settings (you can do this via GUI in your DE's settings) to see if everything is set correctly e.g is automatic DHCP enabled? (It seems so, based on the error messages. That's just an example.)
I had a situation the other day where my laptop ethernet port was being assigned to an oddball subnet that had no network connection. As it turned out, I had set the port to share internet in order to set up a Google TV (my dorm network requires a MAC address, but the TV had an old version where you couldn't get the MAC address until after TV setup, which required a network connect) and had never reversed the setting.
That's not necessarily the problem here.
Normally, Fedora would boot on both types of systems, too. However, OP wants to copy an already-existing UEFI install or at least the config to a legacy system, not (necessarily) to find a distro that could be installed from a normal live installer on both boot types.
Thus the Nix recommendations, as theoretically, one centralized config could be copied between systems to create a similar environment on different systems.
On another note, for actually doing it, it looks like Fedora uses Dracut, so you just need to run
sudo dracut -f.