You must log in or register to comment.
I always find it disappointing when I encounter an article criticizing something when it’s obvious that the author didn’t bother to research how and why it came to be. It suggests to me that they aren’t interested in informing readers so much as promoting themselves or their favorite project.
Sigh… modern “journalism”.
Gobolinux has been trying to redefine and simplify the linux filesystem for a long time already, but no one gives it a chance
Yeah it’s obviously an improvement but I guess you can’t really sell a distro on “it has a more logical filesystem layout which may cause some issues, and it’s super super niche which will definitely cause some issues”.
Probably a lost cause. I imagine Flatpak will actually work properly before the Unix filesystem hierarchy is made sane.
@FizzyOrange @morto #nix and #guix do exactly this. It is 2025.
Not exactly. It is pretty similar though, true.
Love Osnews. Been reading since the 00’s.
This is a dumb explanation and take by somebody who is stuck in their ways, and refuses to understand modern permissions systems.
The location of a binary executable matters less now than ever, and it’s location on the filesystem doesn’t matter whatsoever. It’s up to whomever packages and nothing more. As long as it’s documented, it doesn’t matter.
Your animosity is perplexing given that the article agrees with you; it even ends with:
Anyway, these are good moves, and I’m glad most prominent Linux distributions are not married to decisions made in the ’70s, especially not when they can be undone without users really noticing anything.
…and the rest of it?
Also…do you know what the word “animosity” means? This ain’t that.
…the rest of it explains the context, and then briefly says that some people will disagree with the decision, but those people should just use a different distro. What are you complaining about?
The location of a binary executable matters less now than ever, and it’s location on the filesystem doesn’t matter whatsoever. It’s up to whomever packages and nothing more. As long as it’s documented, it doesn’t matter.
But what if another program expects said user-level-system-binary in that very location?
Then it still finds what it is looking for because
/usr/sbinand/usr/binare now the same place.Then you package them differently to address the naming. It’s not rocket science.
If there are two people named “Tom” in a room, do you just give up and walk out of said room because it’s impossible to find a way to communicate in a room with two people of a similar name? No.
No, but its like you expect your Milk to be in the fridge but its not there, but instead someone put it in the fridge of your neighbour for whatever reason. Why would you look there?
Ever dealt with packaging files? You tell them where to go. It’s a simple manifest that says where files get unzipped and put on the filesystem.
You have zero idea WTF you’re talking about.
No I haven’t dealt with packaging files. But packaging files implies that you know where your files are.
But as I stated it’s not about your own files but files from someone else you rely on.
Imagine what havok you would cause when someone things it would be a great idea to put
lsorloginno longer in/binbut/sbininstead?And how does this work when you expect a binary of someone else’s package in a certain location?
Are you trolling or what?
Lolz, are you joking?
No. But you seem to be. I think you have a weird sense of humor.
