iptables now defaults to the nft backend (affects pretty much nothing)
Repost.
Also, my Mint install broke, uh, shit I don’t remember, 5 times? Arch broke zero times. Zero times not my own fault for forgetting I was installing something and shutting off the computer, of course. Except for the times I tried the fucking installer python script, but since I never even booted the install it doesn’t count.
Reminds me of my try of Nobara. I do clean install, it installs and starts updating itself for a long while. Afterwards it tells me to reboot, and that the update has failed. I am??? Since I am a noob, so I reboot. And the whole system fully breaks, and no trouble-shooting helps, so I have to re-install. No biggie, just mildly annoying, it was a clean install after all. Then I do some searching to figure out, what went wrong, and find out, that updates failing and the system fully breaking, and having to re-install it if you reboot, is apparently normal behavior for Nobara.
I’ve had Nobara on my PC for several years and not had a problem, though I know others have
Having said that, if I could be bothered I would probably just return to regular Fedora again so that I could have a decent package manager and updater…
“No way to prevent this” says only distro where this regularly happens
Arch explicitly says “never do this”
News from this year:
varnish, which is renamed tovinyl-cache(it’s a proxy, only affects servers)Repost.
Also, my Mint install broke, uh, shit I don’t remember, 5 times? Arch broke zero times. Zero times not my own fault for forgetting I was installing something and shutting off the computer, of course. Except for the times I tried the fucking installer python script, but since I never even booted the install it doesn’t count.
🤭 heh
Foot-guns are my PROTECTED SECOND AMENDMENT RIGHT.
Reminds me of my try of Nobara. I do clean install, it installs and starts updating itself for a long while. Afterwards it tells me to reboot, and that the update has failed. I am??? Since I am a noob, so I reboot. And the whole system fully breaks, and no trouble-shooting helps, so I have to re-install. No biggie, just mildly annoying, it was a clean install after all. Then I do some searching to figure out, what went wrong, and find out, that updates failing and the system fully breaking, and having to re-install it if you reboot, is apparently normal behavior for Nobara.
I’ve had Nobara on my PC for several years and not had a problem, though I know others have
Having said that, if I could be bothered I would probably just return to regular Fedora again so that I could have a decent package manager and updater…