Free LPIC-1 Exam 101, Part 1 of 2, version 5.0 Practice Questions

The Linux root partition is the partition that contains the root filesystem, which is the top-level directory of the filesystem hierarchy. The root filesystem contains the essential files and directories that are needed to boot the system, such as the kernel, the init system, the configuration files, the libraries, the binaries, and the device files. The root partition can be formatted with different filesystems, depending on the support of the kernel and the boot loader. Some of the common filesystems that can be used on Linux root partitions are:

ext3: This is the third extended filesystem, which is a journaling filesystem that provides metadata and data integrity, fast recovery, and backward compatibility with ext2. ext3 is widely supported by most Linux distributions and boot loaders, and it is considered stable and reliable. ext3 has been the default filesystem for many Linux distributions, such as Debian, Ubuntu, Fedora, and CentOS, until it was replaced by ext4.

XFS: This is a high-performance 64-bit journaling filesystem that supports large files and volumes, parallel I/O, extent-based allocation, and online defragmentation. XFS is designed for scalability and efficiency, and it is suitable for applications that handle large amounts of data, such as databases, video editing, and data warehousing. XFS is the default filesystem for Red Hat Enterprise Linux and SUSE Linux Enterprise Server, and it is also supported by other Linux distributions and boot loaders.

The other options are not valid filesystems for Linux root partitions, because:

NTFS: This is the New Technology File System, which is the default filesystem for Windows operating systems. NTFS supports features such as journaling, encryption, compression, and access control. NTFS is not natively supported by the Linux kernel, and it requires a third-party driver, such as ntfs-3g, to read and write to NTFS partitions. NTFS is not compatible with the Linux boot loader, and it cannot be used as the root filesystem for Linux.

VFAT: This is the Virtual File Allocation Table, which is an extension of the FAT32 filesystem that supports long file names. VFAT is a legacy filesystem that is mainly used for compatibility with older Windows and DOS systems. VFAT does not support features such as journaling, permissions, and symbolic links, and it has limitations on the file and volume size. VFAT is not suitable for the root filesystem for Linux, and it is not supported by the Linux boot loader.

swap: This is not a filesystem, but a special type of partition that is used to store the memory pages that are not currently in use by the system. swap is used to extend the physical memory of the system, and it can improve the performance and stability of the system. swap is not a mountable partition, and it cannot be used as the root filesystem for Linux.

The umask value that will result in the default access permissions of 600 (rw-------) for files and 700 (rwx------) for directories is 077. This is because the umask value is an octal number that represents the permissions that are not given to the files or directories. To calculate the umask value, we need to subtract the desired permissions from the maximum permissions, which are 666 for files and 777 for directories. For example, if we want the files to have the permissions 600 (rw-------), which means read and write for the owner and no permissions for the group and others, we need to subtract 600 from 666, which gives us 066. Similarly, if we want the directories to have the permissions 700 (rwx------), which means read, write, and execute for the owner and no permissions for the group and others, we need to subtract 700 from 777, which gives us 077. The umask value is the minimum of these two values, which is 077. The first digit of the umask value is for the special permissions, such as setuid, setgid, and sticky bit, and it is usually set to 0. Therefore, the final umask value is 077. For more information on how to use the umask command, you can refer to the following articles:

What Is umask in Linux, and How Do You Use It? - How-To Geek

Umask command in Linux with examples - GeeksforGeeks

What is UMASK and how to set UMASK in Linux/Unix?

How to Set and Update the Default Umask Value - phoenixNAP

The command that shows all shared libraries required by a binary executable or another shared library is ldd. This command queries the dynamic linker to find out which libraries are needed by the given file and displays them on the standard output. For example, to see the shared libraries required by the /bin/ls program, we can run:

ldd /bin/ls

The output will look something like this:

linux-vdso.so.1 (0x00007ffd8a7f6000)

libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f0c5a6c4000)

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0c5a4d3000)

libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007f0c5a445000)

libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0c5a441000)

/lib64/ld-linux-x86-64.so.2 (0x00007f0c5a8a5000)

libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0c5a41e000)

The output shows the name and the path of each shared library, as well as the address where it is loaded in memory. If the library is not found, the output will show not found instead of the path. The linux-vdso.so.1 library is a special case, as it is a virtual library that is not actually present on the filesystem, but is injected by the kernel into every process12.

 The renice command changes the nice level of a running process. The nice level is a value that affects the scheduling priority of a process. A lower nice level means a higher priority and a higher nice level means a lower priority. The renice command requires the process ID (PID) of the target process and the new nice level as arguments. For example, renice -n 10 1234 will change the nice level of the process with PID 1234 to 10. References: LPI Exam 101 Detailed Objectives, Topic 103: GNU and Unix Commands, Weight: 25, Objective 103.3: Perform basic file management, renice command