Take the Linux Filesystem Tour | Hacker News Reader

Take the Linux Filesystem Tour

tuxradar.com

100 pointsgiis19 comments

The man pages[1][2][3] for the hier command on various BSDs are also worthwhile reads if you want to familiarize yourself with *NIX directory structures in general.

[1] http://www.freebsd.org/cgi/man.cgi?query=hier

[2] http://www.openbsd.org/cgi-bin/man.cgi?query=hier

[3] http://netbsd.gw.com/cgi-bin/man-cgi?hier

Absolutely gorgeous. [2] in particular.

A lot of this is driven by historical concerns of large institutional installations that don't really apply to most Linux users today. We're set up for the possibility that /usr is a read-only NFS share for use by multiple processor architectures. This is an increasingly rare scenario, but it's the justification for why /var was split from /usr and /usr/share was split from /usr/lib.

It's bordering on unreadable at the moment. Turns out you can't just slam a bunch of advertising markup on top of a web page and assume it all works fine. Who knew.

A good introduction to the Linux file system hierarchy for the uninitiated. Thanks for sharing.

Sort of. It doesn't really cover the unification of / and /usr binaries and libraries that's ongoing.

Look at the date, the article is from 2009.

That's only Fedora/RedHat though. I'd love to see that in Debian, but there is no movement towards it yet.

The design of the website is awful. Its very difficult to read the content.

I am not a fan of the Linux default directory structure.

But this web site's design? I see black sans-serif paragraphs of text on a white background. Plain, yes. Maybe a bit too plain. But awful?

That's not what I see... http://oi57.tinypic.com/205rx9i.jpg

When overlay adverts go horribly, horribly wrong...

That image is from tinypic, that's even worse!

I use ad-blocker+ on chrome. Probably it helped me to overcome these issues.

Rather than following the Filesystem Hierarchy Standard like most Unix-like systems, each program in a GoboLinux system has its own subdirectory tree, where all of its files (including settings specific for that program) may be found. Thus, a program "Foo" has all of its specific files and libraries in /Programs/Foo.

http://www.gobolinux.org/

Great! /s

"I heard you liked DLL Hell, so we ported it to Linux"

Separate directories do not imply conflicting versions colliding (which I guess it what you refer to?). In fact, I'd say is it less likely. Can you eloborate?

I'll bet it's fine if you have ad-blocker and similar, but it's atrocious, bordering on unreadable, if you don't. If you write for the web, and you care about your readership, you need to look at your own pages with browsers they are likely to use, and no extensions. And with extensions as well, because while some of your readers will use vanilla browsers with no extensions, some will have heavily personalized setups.

Don't take it for granted that what you see is what everyone sees. It's just not true.

If you didn't enable CSS it would look fine. I certainly don't entrust the presentation of content to web designers, that would be idiotic.

Reply on news.ycombinator.com