[Solved]Need guidance for /etc/fstab

[gardenair]

I have created five partitions for a DOS/Legacy BIOS system

[grknight]

Make sure you have 6 columns for each fstab entry. Currently, it seems you have combined the 5th and 6th together. There needs to be a space between the numbers.

[gardenair]

Yes, it was my mistake.

https://ibb.co/tmn07c5

[pietinger]

[figueroa]

Since you are only using four partitions, you don't need an extended partition. Simply things and just make four primary partitions.

You don't need a separate boot partition. A separate boot partition adds unnecessary complexity.

For the way I use UUID in the fstab, see the following:

[gardenair]

Thanks once again. As I am going ahead Gentoo is opening a new topic/world. It is a sea. It is a reality that If someone wants to learn Linux he/she must use Gentoo and play with it. Each topic is itself a complete book.
Well "figueroa" I use separate boot partitions as I see in most cases on tutorials they make. One thing I know is that making separate "/boot" is used when we need more than one Linux kernel. (If I am correct).
In your home partition, there is " user, exec,noatim". exec means " (allow executing binaries and scripts) what do "user and noatim mean?

[NeddySeagoon]

gardenair,

exec means that things can be executed from that location. As its the default, it need not be included in fstab.
Think about using noexec in places to deny an attacker opportunities to run programs. Even on /home if your users are not trusted.

user allows any user to mount and the same user to unmount the filesystem. Its only useful on optical media.
A logged in user cannot unmount /home as they will always have an open file there that they cannot close without logging out.

noatime (you missed the e) does not record the time the file was last accessed in the directory. This saves a lot of directory writes.
That's good on SSD and a small speed improvement too.

For the rationale behind a small /boot partition at the start of the drive you need no understand something of the history of the PC. It "just grew" and was never designed to be the way it is now.

== edit ==

Using kernel assigned device names like /dev/sda1 is fine and safe while there is only one device. The kernel assigns names in device detection order, so with two or devices (sda and sdb) naming is not deterministic. They may be swapped. The UUID is a unique property of a filesystem, so that always works in fstab.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[Hu]

[figueroa]

gardenair
There are man pages for fstab and mount, and, of course, bottomless internet resources.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi

[gardenair]

Thanks all for guiding me.One thing more I want to add that when adding partition label by UUID then the user must awake in adding entry in his /etc/fstab
Example

[Hu]

You can more easily avoid such mistakes by never writing the UUID at all. Instead, you should get a tool to show you the UUID in a form that your editor can insert it into fstab without you ever typing any of digits of the UUID.

[sabayonino]

Look at genfstab