Linux course fhs file hierarchy standard

Linux course fhs file hierarchy standard

1. File Hierarchy System

2. Current systems
I listed the / directory on the system I was working
on got this.
bin boot dev etc home lib lib64 lost+found
media mnt opt proc root run sbin sys tmp usr
var

3. Common FHS
The next slide has a diagram of the common FHS
tree.

4. Linux Hierarchy System

5. / root
Just a single slash ( / ) denotes the root directory.
Some students while learning Unix or Linux are
not able to see the tree and do not ask.
They just accept the term tree.

6. Directory “tree”
You shall see images like

7. Where is the tree

8. Where is the tree

9. Where is the tree
and

10. Where is the tree

11. Directory “tree”
To see the tree and what computer science and
ICT ( information and communications
technology ) people call a tree.
I shall turn the diagram side ways or upside down
so you can “see” the tree they are referring to.

12. Where is the tree

13. Where is the tree
No you can see
why this is called
the “root”

14. Where is the tree
No you can see
why this is called
the “root”

15. FHS details
Now we shall start with each directory and explain
what is in it.

16. The File Hierarchy Standard

17. /bin
Bin is the short form for binary.
When programs are made, they are written in high
level languages which humans can make sense
of.
The examples are PHP, C, Pascal, C++, Python,
and hundreds more.

18. /bin
These languages are translated into a binary form
which the CPU can run.
The technical term for this translation is compiled.
The technical term for “the CPU can run” is
execute.
Some people refer to them as exe files for short
and this is short for executable.
In Linux and Unix they are called binary files and
bin is used for the short name for the directory.

19. /bin
So the bin directly contains programs which are
commonly used and are related to the operating
system.
Examples are ls for listing files akin to dir in DOS.
cp for copying files which is like copy in DOS.

20. /bin
Technically not all files in the bin directory are
compiled files.
There can also be shell scripts in the directory
which are interpreted when they are executed.
This point of shell scripts also goes for other bin
directories like
/sbin, /usr/bin, /usr/sbin

21. The File Hierarchy Standard

22. /boot
Due to some technical limitations of the BIOS
(Basic Input Output System) which is software
located on the motherboard. Sometimes it needs
the boot partition to be located near the beginning
of the harddisk (sector zero).
Because of this a separate partition is made and
the /boot directory is located there to allow
support for the BIOS.

23. /boot
Whether your BIOS needs a separate partition or
not, the startup files for the boot loader of the
operating system shall be located in this /boot
directory.
This is where the executable copy of the kernel
shall be found.
The kernel is the core part of the operating system
which manages ALL of the hardware.

24. The File Hierarchy Standard

25. /dev
Almost all of the devices have a device file
associated with them in Linux.
All of the device files are located in the /dev
directory.
If you read or write to a file in this directory, you
shall be actually communicating with a device.

26. /dev
For example.
if you give the command
cat /dev/audio > /tmp/file.audio
the mic shall be activated and your shall be
recording audio.
Press control C to stop the recording.

27. /dev
Now if you give the command
cat /tmp/file.audio > /dev/audio
The speakers shall be activated and your shall be
able to hear what was recorded.

28. The File Hierarchy Standard

29. /etc
This is where all of the configuration files for
almost all of the softwares are kept.
This way the administrator can backup only a few
megabytes and have a copy of all of the
configuration files of all of the softwares installed.
To restore a system, the administrator only needs
the install all of the software from the CD and/or
the internet and all of the things shall be back as
before.

30. /etc
If the software is a server and does not use a
database and does not use data files.
And only does caching like proxy servers, DHCP
servers, Routers, and such, they shall work
perfectly.
For other applications which have data and a
database, these files also need to be backed up.
But you avoid having to copy all of the programs
in the bin directories completely.

31. /etc
If the software is a server and does not use a
database and does not use data files.
And only does caching like proxy servers, DHCP
servers, Routers, and such, they shall work
perfectly.
For other applications which have data and a
database, these files also need to be backed up.
But you avoid having to copy all of the programs
in the bin directories completely.

32. The File Hierarchy Standard