To avoid this behavior, a filesystem reference must be passed as an argument: By default the program will display information about all existing filesystems. To obtain information about filesystems we can run the lsblk command, eventually with the -o option to specify the fields we want to retrieve, or by using the -fs one, which is the equivalent of using -o and provide NAME,FSTYPE,LABEL,UUID,MOUNTPOINT as arguments. On GPT partitioned disks it’s also possible to reference a filesystem by using PARTUUID or PARTLABEL. The latter is the absolutely preferred method, since it guarantees to univocally reference a filesystem, as its name states. The most typical way to reference a block device is by using its node inside the /dev directory, so for example to reference the first partition of the sda block device we use /dev/sda1 as value.Īlternative ways to reference a block device is by using its LABEL or UUID (Universal Unique IDentifier). The first field in each fstab entry holds information about the local or remote block device which should be mounted. Let’s analyze each field and its role in an entry.Įach entry line in the fstab file contains six fields, each one of them describes a specific information about a filesystem. Each field can be separated by another either by spaces or tabs. Each line in the file describes a filesystem, and contain fields used to provide information about its mountpoint, the options which should be used when mounting it etc. The first thing we must know about the fstab file is that is meant to be only read by programs and never written except by the system administrator. $ – requires given linux commands to be executed as a regular non-privileged user # – requires given linux commands to be executed with root privileges either directly as a root user or by use of sudo command No specific software is needed to follow this tutorialįamiliarity with basic concepts like ‘mountpoint’, and ‘filesystem’ Requirements, Conventions or Software Version Used Software Requirements and Conventions Used Software Requirements and Linux Command Line Conventions Category
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |