Dumb Q2 A Graphical File System Structure?

[paulster]

Would anyone know where I can get a block type diagram/Map of the file structure of linux and how it fits together?

Where and why programs get installed what permissions are located by default to those folders etc.

What i've read tried to explain it but ouch its confusing. Yep I need pictures:

[bdg1983]

The filesystem NHF's (http://www.linuxnewbie.org/nhf/intel/filesys/index.html) should get you started. Try some of the distro website to see if they have a block diagram. Quite a few Linux books do have them.

[paulster]

Thanks but at a glance it doesn't really give me anything that I didn't already know.

Examples of some of my questions, from a default install:

***Note these questions are very simplified.

1.Why do I have too desktops under 'root'. The one I can see as a gui is not the one that I access through a command line?

2. The folders Bin why do I have more than one in other directories.

3. What are/is the backbone Linux? conf files, but they are everywhere. In windows you have your registry, ini files inf files etc. What is the backbone of linux.

4. who what where, if I place something in this folder will it be accessable by all with the default settings I choose.

Again these question are very simplified so I don't expect you to answer them.

[Timbo]

I know you don't expect these questions answered, but here it goes anyway. Bin stands for Binary. you have many directories with this name because it is common, and maybe even an accepted naming practice. Binary files go in a Bin directory. As for sharing files, check out 'man chmod' Ext2 is a secure File System, so you need to give others permission to view the directory, and the individual files you want to share. I don't know the answer to your other 2 questions, I'm just a stupid newbie myself. Hope this helps though.

Timbo

[Derango]

Linux Realy dosen't have a backbone like the windows registry. Basicly, each application (well, most applications have a configuration file. Most of these files are located in the /etc/ directory. They controll the look and feel of that particular application. Most programs these days come with a configuration utility that edits the conf files for you, but with some you still need to edit them yourself.

As for conf files being spread everywhere, INI files in windows don't have to be located in a central spot either ;)

[Strike]

Originally posted by Derango:
<STRONG>Linux Realy dosen't have a backbone like the windows registry. Basicly, each application (well, most applications have a configuration file. Most of these files are located in the /etc/ directory. They controll the look and feel of that particular application. Most programs these days come with a configuration utility that edits the conf files for you, but with some you still need to edit them yourself.

As for conf files being spread everywhere, INI files in windows don't have to be located in a central spot either ;)</STRONG>
And thank God it doesn't have something as royally dumb as a registry. User space and kernel space are two distinct areas and should be kept separate. /etc is a GOOD approach. It is good to keep them all in a common repository, but not in a SINGLE FILE. Also, plaintext is THE way to go.

[Derango]

Originally posted by Strike:
<STRONG>Originally posted by Derango:
Linux Realy dosen't have a backbone like the windows registry. Basicly, each application (well, most applications have a configuration file. Most of these files are located in the /etc/ directory. They controll the look and feel of that particular application. Most programs these days come with a configuration utility that edits the conf files for you, but with some you still need to edit them yourself.

As for conf files being spread everywhere, INI files in windows don't have to be located in a central spot either ;)</STRONG>
And thank God it doesn't have something as royally dumb as a registry. User space and kernel space are two distinct areas and should be kept separate. /etc is a GOOD approach. It is good to keep them all in a common repository, but not in a SINGLE FILE. Also, plaintext is THE way to go.

I completly agree with you. If its all in a single file, then one little disk write error can blow the whole thing up. At least with linux, it will only mess up one program ;)

[Rob 'Feztaa' Park]

Originally posted by paulster:
<STRONG>2. The folders Bin why do I have more than one in other directories.</STRONG>

there are different bin folders for different purposes. I'm not entirely sure, but in my experience, /bin is for system administration programs, /usr/bin is for programs that regular users are allowed to run, and I have no idea what /usr/local/bin is for.