![]() I do have some criticisms, there are some flaws in the FHS. And even a lot of Linux software counts on the FHS being obeyed, though if you’re building from a source from a system not very compliant you can use the configure script’s arguments to make the changes to how the program builds so it’ll look in the right places. Prediction really is important for a filesystem hierarchy. The FHS makes it also easy for me to figure out where something is likely to be, be it a configuration file or an asset for a program I use that I want to fiddle with. But it’s extremely exhaustive and can even be confusing.Ī good way to explain POSIX’s FHS is to say, “everything is in its place, and there is a place for everything.” The FHS spec file has a much more detailed explanation of how a POSIX filesystem is meant to look like. They are incorrect and its because they don’t understand it. Love it.Ī lot of people new to Linux think it’s directory structure is a horrible gaggle of directories and very disorganized. I love the Filesystem Hierarchy Standard. For example, /srv/cvs contains CVS related data.Contains server specific services related data.For examples, /media/cdrom for CD-ROM /media/floppy for floppy drives /media/cdrecorder for CD writer.Temporary mount directory for removable devices.Temporary mount directory where sysadmins can mount filesystems.add-on applications should be installed under either /opt/ or /opt/ sub-directory.Contains add-on applications from individual vendors.Library filenames are either ld* or lib*.so.*.Contains library files that supports the binaries located under /bin and /sbin.Kernel initrd, vmlinux, grub files are located under /boot.Home directories for all users to store their personal files.For example, when you install apache from source, it goes under /usr/local/apache2 /usr/local contains users programs that you install from source./usr/lib contains libraries for /usr/bin and /usr/sbin.For example: atd, cron, sshd, useradd, userdel If you can’t find a system binary under /sbin, look under /usr/sbin. /usr/sbin contains binary files for system administrators.If you can’t find a user binary under /bin, look under /usr/bin. /usr/bin contains binary files for user programs.Contains binaries, libraries, documentation, and source-code for second level programs.Files under this directory are deleted when system is rebooted.Directory that contains temporary files created by system and users.This includes - system log files (/var/log) packages and database files (/var/lib) emails (/var/mail) print queues (/var/spool) lock files (/var/lock) temp files needed across reboots (/var/tmp).Content of the files that are expected to grow can be found under this directory.This is a virtual filesystem with text information about system resources.For example: /proc/ directory contains information about the process with that particular pid. This is a pseudo filesystem contains information about running process.Contains information about system process. ![]() These include terminal devices, usb, or any device attached to the system.This also contains startup and shutdown shell scripts used to start/stop individual programs.Contains configuration files required by all programs.For example: iptables, reboot, fdisk, ifconfig, swapon.But, the linux commands located under this directory are used typically by system aministrator, for system maintenance purpose. ![]() Just like /bin, /sbin also contains binary executables.Commands used by all the users of the system are located here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |