Oh dear xenu.

Yes i know that usr,share,sbin are fast to type and probably are what they are because of legacy but damn. I´m constantly in xterm and more and more i think that maybe I should install locate for just finding bits and pieces of program files, configuration files etc. Yes most importantly conf,ini etc are in home but you know what i mean.

What kind of twisted mind categories things like this. My bookshelves are categories by year, author, name etc.. My data collections are categorized in folders/filenames. Would i ever put for example recipes in order where I rip all the recipes and re categories them by ingredients from single recipes. There would be 10 sheets of saying how many eggs and i had to find other corresponding sheets form other categories and combine them.

My brain hurts. Now please if you have any good advices how to understand or just ignore this thing please tell me. Let´s just say one thing. I will not tolerate any kind of "yes it should be there but it might be also". Going directory and finding it empty or just surfing in xterm is just making me mad.

End of rant. Sorry. Yes now i feel better

Well there is a reason why the folders are name as such, bin contains exectables, usr contains user apps (I think), /dev is memory mapped devices etc. etc.

This make updating/reinstalling real easy for me in Linux becuase I have all my config files under /home mount on another disk and just update the OS - so if my OS becomes bust I don't care cos my files are safe.

http://tldp.org/LDP/Linux-Filesystem...Hierarchy.html

Probably getting to know what they were derived from could help a little...

bin - binaries
sbin - system binaries
dev - devices
lib - libraries
mnt - mount points
home - home directory for all users
root - home directory for root user
etc - configuration files for host system

love the linux hierarchy, but definitely not a big fan of the default MyDocs folder. that is ******ed IMO

as ysss and gwj already pointed out, there's a good reason for the filesystem structure. it takes time getting used to (as every new thing does), but once you know your way around, you'll know your way around any linux/*nix system. well, a little at least

for finding files, may i suggest:
this will search the whole filesystem for a file or directory containing the string "myfile". you can also search a specific directory by if you know the exact name of the file,
will find it faster.

if you want to know where a package stores it's files, use
to search for a specific installed package, use
to search for available (but not yet installed packages) use

Thank you very much for these good advices. Some of them i already know. But but...jees. For me it´s really important that on some level things work and are categorized as they are in my brain or in my physical world. I know that i should adapt myself and learn to think different, but sometimes it´s just frustrating.

hmm that's the reason why i like spotlight on my Mac. but the idea of having just one (or two, if you count the /media directory) where the user should fiddle around with... is useful.

i started with a C64 (without directories) moved to DOS (and windows), to linux/BSD and now i work with Mac.... so i'm used to all of these concepts and think that the Mac approach is the best of all worlds.
the idea of absolutely not caring where you place your files, combined with the ability to have your own structure.
that is perfect, but you need the right tools for that and the N900 doesn't have them.