First thing I’d do is to look at the client (fedora) journal for anything funky happening.

‘sudo systemctl status nfs-client’

Since it’s random I assume you won’t have any timeout in your /etc/fstab but it might be worth taking a look anyway.

Be aware that if the network drops the NFS will be disconnected and won’t auto-reconnect so this could also be the issue.

I don’t know if it plays well with container mounted volume, but looking at autofs could be a solution to auto-remount the share. I use it profusely for network mounted home directories.

“OK then do me a favor, shut it down, unplug the power for 5 second and plug it back in”

I dunno, I’m getting tired of them

Having to install things mostly through flatpaks works seamlessly until it doesn’t. Then you’re stuck in dependency hell where you have to open holes in your containers to allow access to files or binaries.

I’m at a point where I layer enough software that I don’t know If there is still value added.

I’m currently trying Fedora Kinoite and from the get go the hassle of getting a proper Firefox+codecs to watch online videos feels like a major step back.

Then you have the issue of installing software in flatpack (is: vscode, texmaker) that are either not fully working of need to have their access tweaked. Atomic distros appeal is to “just work” it doesn’t seem like it does.

Dumb and Dumber: UwU edition

The fact that zombies seems to be able to walk indefinitly in most movies/series without consuming energy bothers me more than it should.

Do they all evolve to photosynthesize!?

Damn, rust really embrace the “Hey, Can I copy your homework?” Meme. I like rust btw, it’s just funny how often I see something along the line of “it’s like X, but in rust!”

Getting closer to anatomically accurate hearts

It’s a pretty standard process to have some parts installed “loose” and tightened at a later time. It could be to ensure fitment, add rigidity or even just to protect the mating surfaces from the elements during transport.

Also it’s probably not just because Boeing is gonna open them up that they don’t fully secure them. I haven’t seen the specs but it’s quite common to have a reinspection requirements when disassembling something that was fully installed for stress and damage.

Pretty much nothing in aerospace is left to communications. The assembly manuals are not just complete, they are painfully exhaustive.

I disagree but you do you.

Edit: dammit you edit your comment a lot for someone who claims to know how to write code properly.

Because everyone knows a function stops at the if-else. Nothing ever happens afterward.

Fedora 39

I say ess cue ell for the sake of uniformity because it’s not Mysequel nor Postgresequel and the language changed from Sequel to the acronym SQL in the 70s so not really in the “too new” ballpark anymore.

There’s nothing limiting what a comment should be as far as I know.

As an example of what I mean, I’ve seen in a 10k+ lines python code a few lines of bit manipulation. There was a comment explaining what those lines did and why. They didn’t expect everyone to be proficient in bit manipulation but it made it so that anyone could understand anyway.

IMHO the issue in this situation is not the comment but that the person updating the code didn’t do his job properly which shouldn’t be an excuse not to do it from the start.

I don’t care how much you think your code is readable, plain text comments are readable by everyone no matter the proficiency in the programming language used. That alone can make a huge difference when you’re just trying to understand how someone handled a situation.

New employees are responsible of at least 75℅ of documentation clarification and process overhaul.

Keep everyone awake and on their toes.

2 is Maki Oze from fire force

Edit;: the other two seems to be from "How heavy are the dumbbell you lift?". Make sense