Pass the LPIC Level 1 101-500 Questions and answers with ExamsMirror

The cut command is used to extract selected portions of each line of a file or a stream. The -f option is used to specify the fields to be extracted, separated by commas. The -d option is used to specify the delimiter that separates the fields. The default delimiter is the tab character. The cut command can only select output by field position, not by field content. The cut command can also work on non-ASCII text, such as UTF-8 encoded text. The cut command can use different input and output delimiters, but only if the output delimiter is specified by the --output-delimiter option. The cut command cannot reorder fields, meaning that the output fields will always appear in the same order as the input fields. To reorder fields, other commands such as awk or sed can be used. References:

LPI 101-500 Exam Objectives, Topic 103.7, Weight 4

LPI Learning Materials, Chapter 3.7, Basic Scripting

Web Search Results, 

The modprobe command is used to add or remove modules from the Linux kernel. The modprobe command can automatically resolve and load the dependencies of a module, which are the other modules that the module depends on. The modprobe command reads the modules.dep file, which is generated by the depmod command, to determine the dependencies of a module. The syntax of the modprobe command is:

modprobe [options] module [module parameters]

The module is the name of the module to be loaded or removed. The module parameters are optional arguments that can modify the behavior of the module. The options are optional, and they can modify the behavior of the modprobe command, such as displaying the dependencies, listing the modules, or specifying the configuration file.

For example, to load the e1000e module, which is a driver for Intel Gigabit Ethernet adapters, along with any required dependency modules, use the following command:

modprobe e1000e

This command will load the e1000e module and any other modules that it depends on, such as the crc32c module. You can verify the loaded modules by using the lsmod command, which lists the modules and their dependencies, sizes, and usage counts.

The other options are not correct because:

A. depmod: This command is used to generate the modules.dep file, which contains the dependency information for the modules. The depmod command does not load or remove any modules, but it prepares the modules.dep file for the modprobe command to use. The depmod command is usually run automatically when a new kernel or module is installed, and it does not need to be run manually by the user.

B. insmod: This command is used to insert a single module into the kernel. The insmod command does not resolve or load any dependencies of the module, and it requires the full path to the module file as an argument. The insmod command is a low-level command that is rarely used by the user, and it is usually invoked by the modprobe command internally.

D. module_install: This command does not exist in the Linux system. There is no such command as module_install in the Linux documentation or the man pages.

E. loadmod: This command does not exist in the Linux system. There is no such command as loadmod in the Linux documentation or the man pages.

References:

modprobe(8) - Linux manual page

How to Load and Unload Kernel Modules in Linux - Linux Handbook

Linux Kernel Module Programming Guide - TLDP

When piping the output of find to the xargs command, the option to find that is useful if the filenames have spaces in them is -print0. The -print0 option prints the full file name on the standard output (STDOUT), followed by a null character, instead of a newline. This allows the xargs command to use the -0 option to read items from the standard input (STDIN) delimited by null characters, instead of spaces or newlines. This way, filenames with spaces are not split into separate arguments. For example, find . -name “*.txt” -print0 | xargs -0 grep “hello” will find all the text files in the current directory and its subdirectories that contain the word hello, even if the filenames have spaces in them. The -rep-space, -nospace, and -ignore-space options are not valid options for the find command. References: LPI Exam 101 Detailed Objectives, Topic 103: GNU and Unix Commands, Weight: 25, Objective 103.3: Perform basic file management, find command, xargs command

A hard link is a directory entry that points to the same inode as another file. An inode is a data structure that stores the metadata and the location of the data blocks of a file. A hard link is not a separate file, but an additional name for an existing file. Therefore, the following statements are true for hard linked files:

The hard linked files have the same permissions and owner. Since the hard linked files point to the same inode, they share the same attributes, such as the file type, the file size, the access permissions, the owner, the group, and the timestamps. Any changes made to one hard link will affect the other hard links as well. For example, if you change the permissions of one hard link, the other hard links will have the same permissions. You can use the stat command to view the attributes of a file or a hard link.

The hard linked files share the same inode. This is the definition of a hard link. The inode number is a unique identifier for each file on a filesystem. The hard linked files have the same inode number, which means they point to the same data blocks on the disk. You can use the ls -i command to view the inode number of a file or a hard link.

The hard linked files must be on the same filesystem. A hard link cannot cross different filesystems or partitions, because each filesystem has its own inode table. A hard link can only point to an inodethat exists on the same filesystem as the hard link. If you try to create a hard link to a file on a different filesystem, you will get an error message saying:

ln: failed to create hard link ‘link’ => ‘file’: Invalid cross-device link

The other statements are not true for hard linked files, because:

The output of stat will report hard instead of regular file. This is not true, because the stat command does not distinguish between a regular file and a hard link. The stat command will report the same file type for both the original file and the hard link, which is regular file. The only way to tell if a file is a hard link is to check the link count, which is the number of directory entries that point to the same inode. If the link count is more than one, it means there are hard links to the file. You can use the stat -c %h command to view the link count of a file or a hard link.

The hard linked files are indicated by a -> when listed with ls -l. This is not true, because the -> symbol is used to indicate a symbolic link, not a hard link. A symbolic link, also known as a soft link, is a special type of file that contains a path to another file or directory. A symbolic link does not point to the same inode as the target file, but to the name of the target file. A symbolic link has its own inode number, file type, permissions, and timestamps, which can be different from the target file. You can use the ls -l command to view the file type, permissions, and name of a file or a symbolic link. A symbolic link will have the file type l and the name will be followed by a -> symbol and the path to the target file. For example:

lrwxrwxrwx. 1 user user 9 Aug 29 15:10 link -> file

References:

Hard links and soft links in Linux explained | Enable Sysadmin

Hard Link in Linux: Everything Important You Need to Know

A Brief Introduction to Hard and Soft Links in Linux - LinuxForDevices

How to create links between files in the Linux? - Online Tutorials Library

What is a hard link? – definition by The Linux Information Project (LINFO)

The mkfs command creates a file system on a given device partition. If the type of file system is not specified, the default file system type is ext2. This is mentioned in the man page of mkfs1 and also in the article by How-To Geek2. Ext2 is an older file system that does not support journaling, which is a feature that allows the file system to recover from crashes or power failures. Ext2 is not very commonly used nowadays, as most Linux systems prefer ext4 or other file systems that support journaling and other features. References:

How to Use the mkfs Command on Linux - How-To Geek

mkfs(8): build file system - Linux man page

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.

References:

Linux Filesystems Explained — ext2/3/4, XFS, Btrfs, ZFS

Linux File Systems: Ext2 vs Ext3 vs Ext4

What is a Linux SWAP Partition and Why is it Important?

When using regular expressions, the ^ character matches the beginning of a line. For example, ^Hello will match any line that starts with Hello. The ? character matches zero or one occurrence of the preceding character or group. For example, colou?r will match both color and colour. The * character matches zero or more occurrences of the preceding character or group. For example, ab*c will match ac, abc, abbc, abbbc, and so on. The + character matches one or more occurrences of the preceding character or group. For example, ab+c will match abc, abbc, abbbc, and so on, but not ac. Thecharactermatchestheendofaline.Forexample,Worldwill match any line that ends with World.References:[LPI Exam 101 Detailed Objectives], Topic 103: GNU and Unix Commands, Weight: 25, Objective 103.7: Use regular expressions with the standard Linux utilities, Regular Expressions

The /etc/inittab file is a plain text file that contains information about the initialization process of the system. It defines the default run level, the available run levels, and the actions to be taken when entering or leaving a run level. The default run level is the mode of operation that the system starts up into, and it determines which services and processes are running. The default run level is specified by a line similar to the following in the /etc/inittab file:

id:5:initdefault:

The number after the first colon indicates the default run level, which can range from 0 to 6. The meaning of each run level is:

0 — Halt

1 — Single-user text mode

2 — Not used (user-definable)

3 — Full multi-user text mode

4 — Not used (user-definable)

5 — Full multi-user graphical mode (with an X-based login screen)

6 — Reboot

To change the default run level, edit the /etc/inittab file as root and change the number to the desired run level. For example, to change the default run level to 3, use the following command:

sudo nano /etc/inittab

And change the line to:

id:3:initdefault:

Then save and exit the file. The changes will take effect on the next reboot.

References:

SysV Init Runlevels - Red Hat Customer Portal

F.4. SysV Init Runlevels - Red Hat Customer Portal

init - How can I see or change default run level? - Ask Ubuntu

 The nice command is used to start another command with a given nice level. 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 default nice level is 0, and the range is from -20 to 19. Only the superusercan assign a negative nice level to a process. The nice command can also be used to display the current nice level of a process by using the -n option. References:

LPI 101-500 Exam Objectives, Topic 103.3, Weight 3

LPI Learning Materials, Chapter 3.3, Process Management

Web Search Results, 1

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