Eats where the locals eat, doesn’t ride the tuk-tuk

OK, the text was wrapping weird on my screen and it didn’t look like that was part of the same path.

Have you tried giving it a simpler path?

It needs to be pointed to a specific mount point, not just the mounts folder.

For example, /mounts/mountname

After creating the mount point name, setting the permissions correctly, and updating fstab, it should start to show up as a fixed drive.

You need to create a permanent mount point for it. Then it will be seen as a non-removable drive.

I experienced the same thing when I installed Bazzite.

Yeah, I’m not panicking, but I agree with everything you said.

I want to believe that someone at IBM realizes what they lost if they fuck up Red Hat, but I’m sure we all know better than to count on it.

It’s just a bummer we have to have this conversation at all. Even when a corporation tries to start out on the right foot, odds are stacked in favor of enshittifying.

Yeah, I agree. The big picture is concerning, though this latest instance just happens to not be a red flag. We’re not enshittified yet, but it’s a short jump depending on IBM’s next decisions.

Considering Red Hat’s core is development, it’s not necessarily a bad thing to merge things like legal, HR, finance, and accounting with IBM’s own departments.

The trouble is, once the parent company starts merging some departments, shareholders often push to merge more departments.

If the right people hold sway at IBM, Red Hat won’t continue that route to the point of fucking up the OS. But that’s a big “if.”

Probably no need to rush into anything. It sounds like the reorg is moving a data security team into Red Hat, and isn’t necessarily enshittifying anything.

A backup plan is always good, but this could wind up being a nothingburger.