Newsvine
  • Welcome
  • Help
  • Report Bug
  • Conversation Tracker
  • Your Column
  • Replies
  • Friends
Type Comments Since You Last CheckedArticle Source Last Checked Stop Tracking All Clear Tracking All
Advertise | AdChoices
Log In | Register
Close the Login Panel
Existing users log in below. New users please register for a free account.

New Users:

Existing Users:

E-Mail:
Password:
Forgot Password?
Please enter the e-mail address or domain name you registered with:
E-Mail/Domain:
Back to Login
Log Out
  • Top News
  • Local News
  • World
  • U.S.
  • Sports
  • Politics
  • Tech
  • Entertainment
  • Science
  • Business
  • Health
  • Odd News
  • More
    • Arts
    • Education
    • Environment
    • Fashion
    • History
    • Home & Garden
    • Not News
    • Religion
    • Travel
Visit Pid's column >>

PID

Home Page
Technologist
Articles Posted: 4  Links Seeded: 8
Member Since: 11/2005  Last Seen: 4/15/2011

What is Newsvine?

Updated continuously by citizens like you, Newsvine is an instant reflection of what the world is talking about at any given moment.

Get a Free Account
Help
Fun Stuff
  • Your Clippings
  • Leaderboard
  • E-Mail Alerts
  • Top of the Vine
  • Newsvine Live
  • Newsvine Archives
  • The Greenhouse
  • Recommended Articles
  • Wall of Vineness
Put a Seed Newsvine link on your own site

Why is the Linux filesystem layout still so obscure?

Sun Jan 22, 2006 5:53 AM EST
technology, internet, web, linux, computing, servers, filesystem
By Pid
Advertise | AdChoices

I've been using Linux as a server platform for approaching 10 years - I'm pretty familiar with the layout of the file system, and the tools used to navigate the shell - but only through experience and plenty of trial and error.

It occurred to me during conversation with an acquaintance (and Linux novice) that one of the barriers to familiarity with the operating system is the relatively obscure nature of the important directories, and the location of important files. There is no way to intuit the layout, a user must gain a certain level of expertise through study before they are competent.

This strikes me as an extraordinary oversight, especially as most of the Linux distributors aim to improve the accessibility of their version, and thus gain market share.

Now, before the opponents and proponents of the various operating camps light their torches and mob bulletin boards demanding blood, consider, dear reader, the following...

Modern system administrators have to patch and/or upgrade the software on their systems with alarming frequency - enterprise class businesses have processes and resources to do this in an orderly fashion, testing before deployment, using alternative hardware, et cetera.

Smaller businesses (which make up a notable part of Linux market share) have less resource and higher dependance on single or low units of servers - updating these systems often involves installing newer versions of software alongside live versions on the same machine, and switching between them in order to effect the change.

While there is nothing to prevent users from installing software wherever they please on a Linux server, there is nothing to encourage them to adopt good practice, no intuitive layout and nothing that really makes it easier to manually update/patch their software*.

Have modern requirements for server and desktop systems outgrown the old layout, and do they justify a re-examination of the default filesystem layout?

Here's a simple example of how it could be structured:

/servers/databases/mysql/mysql5.01
/servers/web/apache/apache2.1
/system/libraries/ssl

If you don't agree with the above, then think up your own, it's just an example.

So here's my final question: Would radically changing, and standardising the filesystem layout improve the usability, make it easier to learn or administer and increase the adoption of Linux systems?

*N.B. We're just talking filesytem layout here, not "Yum", not "Redhat update", not anything similar.

  • Enjoy this article? Help vote it up the 'Vine.

Back To Top | Front Page

Published to:

  • Pid's Column, All of Newsvine
  • Groups: none
  • Regions: none
  • Public Discussion (11)
orsus

I would like to see more descriptive foldernames, and grouping catalogs together like your example would also help maintaining the system.
I'm relatively new on linux, and having problems finding out where the hell that application I just installed went.
The real issue is:

  • Who will decide the new standard?
  • How long will the transition take?

I think it would take years for a new standard to emegre, and in the meantime we would have 2 standards battling on our box. So i guess we just have to stick with what works...

    Reply#1 - Sun Jan 22, 2006 6:23 AM EST
    JW_00000

    Isn't the filesystem more or less standarized by the "Filesystem Hierarchy Standard" (http://www.pathname.com/fhs). I thought most Linux OSes used directories like /usr, /dev, /bin, /lib, /home... However, I'm just starting with Linux, and the filesystem is still obscure to me. When I want to change a configuration, or when I'm just searching something, it still takes a long time. I don't get why some apps are at /usr/bin, some at /usr/share and some at /etc/*name*. Most have a file at all those locations. On Windows, each application has a C:Program Files*name* directory, but on Linux the files are about everywhere.

      Reply#2 - Sun Jan 22, 2006 7:18 AM EST
      Pid

      You're right, JW, the filesystem does currently use those directories - I'm wondering *why* it still does, and whether improvements could be made. I didn't mention un-installing, but it's another issue that people find difficult to deal with, precisely because it's hard to keep track of where all the files end up.

      bin, share & etc all have slightly different purposes, and files are placed there accordingly - it's just hard to understand if you're new, as it's non-intuitive.

      • 1 vote
      Reply#3 - Sun Jan 22, 2006 8:25 AM EST
      Ivan Pavlov

      I must agree that the learning curve for Linux is higher than for Windows, but I see this as the price to pay for using free software. There are several issue related to the question.

      First of all, if we speak of Linux as a server platform there is not much justification in making the filesystem layout more usable. After all, usability in this case falls back to strictly personal tastes. Most sysadmins (at least the ones I know) are perfectly happy with the standard layout. Moreover, nothing prevents those who find that fS layout does not suit their needs, to change it (at the cost of more difficult maintenance afterwards). I cannot agree that "being difficult to learn" is an issue at all - Cisco certifications are also difficult but this does not stop people from studying.

      Secondly, the average desktop user has very little to do with the filesystem itself, so this is not an issue.

      Thirdly, Windows filesystem layout is even more difficult to understand. Just try to find out which DLL's does a program use and which registry entries it has made. In that respect Linux is just transparent.

      I think the whole problem is that some people are just too lazy, and get frustrated too quickly. The real problem with the speedier adoption of Linux according to me is, the lack of good documentation and the lack of a comprehensive troubleshooting knowledge base (newsgroups and mailing lists do not always work).

        Reply#4 - Sun Jan 22, 2006 9:35 AM EST
        monkeywork

        With modern distributions it shouldn't be a concern for the "joe user" what the filesystem named - modern desktop enviroments make browsing the files system a snap. Applications get installed automagically, and configurations done via wizards and control panels.

        If you want to manage a linux server then spending 10-15 minutes to understand the "general rule" of what directory is for what will help you with 90% of your tasks.

        • 1 vote
        Reply#5 - Sun Jan 22, 2006 12:08 PM EST
        Ed Greve

        Pid, you could always install linux from scratch and set up the directories the way you want. That would be a fun challenge if you've got some spare time and a spare partition laying around. Maybe that would give you a good idea of a reccomendation to make to the FHS or something. I definitely agree with you that the layout could be better...

          Reply#6 - Sun Jan 22, 2006 12:34 PM EST
          Strife

          There actually exists a projet to "modernize" the filesystem layout in Linux, though unfortunately I cannot remember the name of it and so haven't been able to find it yet by Googling. The idea is essentially to model it a little bit after OS X's layout, which is much more transparent in many respects.

          I certainly think that this could be a nice thing for users with relatively little experience, and in the long run it would be good for all. However, in the short term, one would have to be careful with this as it may cause complications in converting everything over to a new directory structure. Big changes require big commitments, and while I would eventually like to see this as a change, I don't think that it's the most pressing need in getting Linux to be easier to use for most people. First thing's first, I suppose is what I am trying to say.

            Reply#7 - Sun Jan 22, 2006 12:56 PM EST
            Brian C

            Yesss. The filesystem is one of the most fundamental parts of an interface, so it should not be the hardest part to understand!

              Reply#8 - Sun Jan 22, 2006 2:38 PM EST
              splaice

              Linux is a "UNIX like" operating system so it models it's filesystem layout after it. There is a ton a reasons for this but mainly because of comptability with UNIX standard and heritage. To change it would break things and adoption of the changes would be slow since what is there works.

              The thing to look at is do you really understand the layout? A file system layout is itself a namespace, and you need to understand the elements of it and their purpose to understand it. Things will be a lot less confusing once you understand the layout. Google found a good page explaining this here.

              Another thing to realize is that generally when working from your shell you don't really need to know where things live. Your shell (sh, bash, etc) has the ability to pull this namespaces together to be accessible as equals by setting your PATH enviornment properly. You don't need to know where 'ls' lives if it is in your PATH.

              Secondly I am not adverse to a new layout but it should be done as an adjunct layout and namespace. I actually really think higher level things in a linux system should use a seperate namespace for things like GNOME, KDE, or other user applications. OSX already has a model for this, and you will notice though OSX still has your standard unix file system layout along with it. They don't want break the standard and expectations for the unix parts of the system.

              • 1 vote
              Reply#9 - Sun Jan 22, 2006 4:22 PM EST
              Pid

              Thanks for all your replies, there are some good points & no flames! Nice.
              A few points:

              A general point is that I'm not arguing with the level of learning, or difficulty required to become an expert - but that good Linux documentation (see JW's link above) is hard to find, and much of its Unix heritage is non-intuitive and obscure. The filesystem man pages don't come with a history lesson, to explain why things are so.

              Nor am I proposing to start the project, I'm asking if changes could be made that would improve the filesystem.

              By specifying a new layout, you'd require software to conform to new installation rules, yes this is a BIG deal.

              I'm happy with my servers, I know how they work, and where things are: but it's taken me many years to accrue this level of expertise, though admittedly I did start when configuring card drivers for X could take days. [sigh]

              Ivan I don't agree with your first point, in principal, but I do recognise that it's often the case that free software requires users to compromise in some way. I just think that we could do better. Many of the visual tools and autoinstallers were developed precisely because it's was so hard to deal with these issues manually.

              Ed I could configure the system the way I liked, but then installation of new software would be much harder, as I'd have to tweak all the 'configure' & 'make' options to reflect the alternative layout - the exact opposite of my interest in making things easier.

              For those of you who are adept with the OS, consider from the novice's point of view, a common concept: how does one completely uninstall a piece of software?

              Finally JW posted a link the to FHS, probably the best general explanation of the what's and why's of the current layout.

              • 1 vote
              Reply#10 - Mon Jan 23, 2006 5:11 AM EST
              splaice

              Maybe you should consider giving GoboLinux a whirl. Someone else appears to have scratched the same itch you have already.

              • 1 vote
              Reply#11 - Mon Jan 23, 2006 5:34 AM EST
              Leave a Comment:
              You're in Easy Mode. If you prefer, you can use XHTML Mode instead.
              You're in XHTML Mode. If you prefer, you can use Easy Mode instead.
              (XHTML tags allowed - a,b,blockquote,br,code,dd,dl,dt,del,em,h2,h3,h4,i,ins,li,ol,p,pre,q,strong,ul)
              Newsvine Privacy Statement
              As a new user, you may notice a few temporary content restrictions. Click here for more info.
              FUN STUFF:
              • Leaderboard |
              • E-Mail Alerts |
              • Top of the Vine |
              • Newsvine Live |
              • Newsvine Archives |
              • The Greenhouse |
              COMPANY STUFF:
              • Code of Honor |
              • Company Info |
              • Contact Us |
              • Jobs |
              • User Agreement |
              • Privacy Policy |
              • About our ads
              LEGAL STUFF:
              • © 2005-2012 Newsvine, Inc. |
              • Newsvine® is a registered trademark of Newsvine, Inc. |
              • Newsvine is a property of msnbc.com