Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Understanding UNIX/Linux file system: Part I <- Understanding Linux filesystems Part II <- Understanding Linux superblock Part III <- An example of Surviving a Linux Filesystem Failures Part IV <- Understanding filesystem Inodes Part V <- Understanding filesystem directories Part VI <- Understanding UNIX/Linux symbolic (soft) and hard links Part VII <- Why isn’t it possible to create hard links across file system boundaries?
...a great piece of work, so I feel a bit uncomfortable about making the suggestion that you should change it. However, here goes:
Primarily what your linked articles are about is the structure of the Linux FS and how directories are laid out. What it isn't about is a comparison of BTRFS, Ext4, Ext3, Nillfs, XFS, ramfs, tempfs, squashfs (do you ever get the feeling that we have enough of them, already?).
So, I'd like to see the word 'hierarchy' in the title to emphasise the layout bit and which files go where, rather than the 'what filesystem type should I use for my new install' aspect.
...a great piece of work, so I feel a bit uncomfortable about making the suggestion that you should change it. However, here goes:
Primarily what your linked articles are about is the structure of the Linux FS and how directories are laid out. What it isn't about is a comparison of BTRFS, Ext4, Ext3, Nillfs, XFS, ramfs, tempfs, squashfs (do you ever get the feeling that we have enough of them, already?).
So, I'd like to see the word 'hierarchy' in the title to emphasise the layout bit and which files go where, rather than the 'what filesystem type should I use for my new install' aspect.
Your points are valid and we as experienced Gnu/Linux users should share our understanding and perspectives. Salasi, I agree but most new users do not understand basic UNIX/Linux structures since most are coming from a different environment. I believe a new user should be aware of structures then build upon the knowledge with file system types. Comparison and personal choice for filesystems will evolve once the user(s) begins to get the feel for uses of a Gnu/Linux. The title was selected to expose to everyone, especially the new user.
For myself, I use the principle of 'KISS': Keep It Simple Stupid. Most of my systems use 'ext2/3/4' and I find no real need to change unless a specific application/use defines the need. The linked references, especially The Linux Directory Structure Explained does use some familiar terminology for a Microsoft OS user to give comparative definition(s) to make things a little easier to understand structure and hierarchy.
Sure filesystem comparisons would help a new user but after they do understand basic structure(S). Enhance the thread as it hopefully progresses.
I also use a modified 'KISS': Keep It Simply Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Understanding Linux Filesystems
