Linked by Kevin Adams on Fri 9th May 2003 23:04 UTC
Linux "Lately, there has been lots of discussion on the current state of Linux as a desktop system, and articles pop up here and there, occasionally with very good ideas. However, none have surprised me more than this one. It was all very hyphothetical, but had pretty radical ideas on how the author thought the Linux directory tree should be reorganized." Read more about GoboLinux, a Linux distro that uses a new style directory tree at
Permalink for comment
To read all comments associated with this story, please click here.
To change or not to change?
by Ano Nymous on Sat 10th May 2003 11:32 UTC

At work we use linux, mostly Redhat now. My collegues are true gurus when it comes to programming and systems design and such. But do they know where to find each and every file in (Redhat) linux? No! And they have used linux forever. I've installed servers and workstations for about million times so I pretty much know where each file is (in redhat) so they ask me when they don't want to spend time on locating a file since they might not even know the name of the file they need to find! So I don't quite think the current filesystem hierarchy is that clear.

People who say the current fsh is just fine and should not be changed propably know it well and don't realize that others may not and don't even want to, they just want to get their work done. If YOU think nothing should be changed, read the previous sentence repeatedly until you understand it!

Someone mentioned that putting each app in its own directory would be not-so-good idea. I disagree. If each app had its own directory, all the files related to that app could be stored in a _one_single_ place. Need to edit the conf? Just go to the app's directory and there it is. And as I recall, Mosfet (of KDE Liquid fame) wrote an article about it some time ago too. Check out ROX and GNUStep too.

Why is it that the best system to date already existed in the 80's and have since disappeared? What system, you ask. NeXT/OpenStep (OSX is a derivative of NeXT), of course! For example, in NeXT you didn't have to know where a configuration file was located, or what its' name was. You had a single interface to _all_ configuration stuff (don't remember the details). You would just ask the interface "what is the value of this variable?" or you could tell it to "set the value of this variable to this". Apps would use the same interface. And no, I have never used NeXT, everything I know about it is from reading stuff from the web. I could tell you more about it, but it's sunny outside so I'll get on my bike and go for a ride!