101-500 Exam Dumps - LPIC-1 Exam 101, Part 1 of 2, version 5.0

Pressing the Ctrl-C combination on the keyboard while a command is executing in the foreground sends the SIGINT(2) signal code. The SIGINT(2) signal means interrupt and is usually sent when the user presses Ctrl-C on the keyboard. The signal causes the process to terminate, unless it is caught or ignored by the process. The SIGHUP(1) signal means hang up and is usually sent when the terminal or network connection is disconnected. The SIGQUIT(3) signal means quit and is usually sent when the user presses Ctrl-\ on the keyboard. The SIGKILL(9) signal means kill and is used to force the process to terminate immediately, without any chance to catch the signal or perform any cleanup. The SIGTERM(15) signal means terminate and is the default signal sent by the kill command. References: LPI Exam 101 Detailed Objectives, Topic 103: GNU and Unix Commands, Weight: 25, Objective 103.3: Perform basic file management, Signal List

The correct option to pass to a filesystem’s entry in /etc/fstab in order to mount the file system without root privileges is:

D. user

The /etc/fstab file is a configuration file that contains information about the filesystems on a Linux system. The /etc/fstab file defines how and when the filesystems are mounted by the mount command or the system. The /etc/fstab file has six fields for each filesystem entry, separated by whitespace. The fields are:

device: the device name or the UUID of the filesystem

mountpoint: the directory where the filesystem is mounted

type: the filesystem type, such as ext4, xfs, vfat, etc.

options: the mount options that modify the behavior of the mount operation, such as ro, noauto, user, etc.

dump: a flag that indicates whether the filesystem should be backed up by the dump command, 0 for no and 1 for yes

pass: a flag that indicates the order of filesystem checks by the fsck command at boot time, 0 for no check, 1 for root filesystem, and 2 or higher for other filesystems

The user option is a mount option that allows any non-root user to mount the filesystem. By default, only the root user can mount filesystems, unless they are specified in the /etc/fstab file with the user option. For example, to allow any user to mount a USB drive with the device name /dev/sdb1 to the directory /mnt/usb, the /etc/fstab entry would look like:

/dev/sdb1 /mnt/usb vfat user 0 0

The user option also implies the noexec, nosuid, and nodev options, which prevent the execution of binaries, the setuid and setgid bits, and the device files on the mounted filesystem, respectively. These options can be overridden by using the exec, suid, and dev options after the user option.

The other options are not correct because:

A. auto: This option indicates that the filesystem should be mounted automatically by the mount -a command or at boot time. This option does not affect the ability of non-root users to mount the filesystem. By default, all filesystems in the /etc/fstab file have the auto option, unless they are explicitly marked with the noauto option.

B. norestrict: This option does not exist in the mount command or the /etc/fstab file. There is no such option as norestrict in the Linux documentation or the man pages.

C. noauto: This option indicates that the filesystem should not be mounted automatically by the mount -a command or at boot time. This option does not affect the ability of non-root users to mount the filesystem. The noauto option is usually used for removable devices or network shares that are only mounted on demand.

 The common Linux commands for file management are mv, cp and mkdir. The mv command moves or renames files and directories. The cp command copies files and directories. The mkdir command creates directories. The copy and move commands are not valid Linux commands. References:

LPI Exam 101 Detailed Objectives, Topic 103: GNU and Unix Commands, Weight: 25, Objective 103.1: Work on the command line

LPI Linux Essentials Study Guide, Chapter 3: Working on the Command Line, Section 3.2: Basic Commands, Page 55

GRUB Legacy and GRUB 2 are different versions of the GNU GRUB boot loader, which is used to load Linux and other operating systems. One of the differences between them is the naming convention for partitions. In GRUB Legacy, partition numbers start at 0, while in GRUB 2, they start at 1. For example, the first partition of the first hard disk would be (hd0,0) in GRUB Legacy and (hd0,1) in GRUB 2. This change was made to avoid confusion with the Linux device names, which start at 1, such as /dev/sda1. Another reason for this change was to make GRUB more consistent with other operating systems, such as Windows and BSD, which also start partition numbers at 1. References:

GNU GRUB Manual 2.06: Changes from GRUB Legacy

What are the differences between GRUB and GRUB2 Boot Loader

To create a symbolic link, also known as a symlink or a soft link, you need to use the ln command with the -s option. The syntax of the ln command is:

ln -s target link

The target is the file or directory that the link will point to, and the link is the name of the link. The link can be either an absolute or a relative path. If the link is omitted, the link will have the same name as the target in the current directory.

In this question, the target is foo.conf and the link is bar.conf. Therefore, the correct command to create a symbolic link called bar.conf pointing to foo.conf is:

ln -s foo.conf bar.conf

This command will create a file named bar.conf in the current directory, which will point to the file foo.conf in the same directory. If you want to specify a different directory for the target or the link, you need to provide the full path. For example, if you want to create a symbolic link called bar.conf in the /etc directory, pointing to the file foo.conf in the /home/user directory, you need to run:

ln -s /home/user/foo.conf /etc/bar.conf

The other options are not correct because:

B. ln foo.conf bar.conf: This command will create a hard link, not a symbolic link. A hard link is a direct reference to the physical location of a file on the disk, not a path to another file or directory. A hard link cannot point to a directory, and it cannot cross different filesystems or partitions. A hard link shares the same inode number as the original file, and it is indistinguishable from the original file. A symbolic link has its own inode number, and it is a separate file that points to the target file or directory.

C. ln -s bar.conf foo.conf: This command will create a symbolic link called foo.conf pointing to bar.conf, which is the opposite of what the question asks. The order of the arguments matters when using the ln command. The first argument is the target, and the second argument is the link.

D. ln bar.conffoo.conf: This command is not valid because it is missing a space between the target and the link. The ln command requires two separate arguments for the target and the link, separated by a space. If you run this command, you will get an error message saying:

ln: failed to access ‘bar.conffoo.conf’: No such file or directory

The modes of the vi editor that are correct are insert mode and command mode. The vi editor is a modal editor, which means that it has different modes for different operations. The insert mode allows the user to insert text into the file. The command mode allows the user to execute commands, such as saving, quitting, moving the cursor, searching, replacing, and so on. The user can switch between the modes by pressing certain keys, such as Esc, i, a, o, and others. The edit mode, change mode, and review mode are not valid modes of the vi editor. References: LPI Exam 101 Detailed Objectives, Topic 103: GNU and Unix Commands, Weight: 25, Objective 103.8: Use vi to create and edit files, vi editor

The correct permissions and ownership for the file /etc/passwd are:

B. -rw-r–r-- 1 root root 531 Jun 5 22:45 /etc/passwd

The /etc/passwd file is a plain text-based database that contains information for all user accounts on the system. It is owned by root and has 644 permissions. The file can only be modified by root or users with sudo privileges and readable by all system users. The permissions and ownership of the file are important for the security and functionality of the system. The permissions and ownership of the file can be viewed by using the ls -l command. For example:

ls -l /etc/passwd

The output of the command will show the following information:

-rw-r–r-- 1 root root 531 Jun 5 22:45 /etc/passwd

The first column shows the permissions of the file, which are composed of 10 characters. The first character indicates the file type, which is - for regular files. The next nine characters indicate the permissions for the user (owner), the group, and the others, respectively. Each set of three characters indicates the read ®, write (w), and execute (x) permissions. A dash (-) means no permission. In this case, the permissions are:

rw- for the user, which means the user can read and write the file, but not execute it.

r-- for the group, which means the group can only read the file, but not write or execute it.

r-- for the others, which means the others can only read the file, but not write or execute it.

The second and third columns show the owner and the group of the file, which are both root. The root user is the superuser or the administrator of the system, who has full access and control over the system. The root group is the primary group of the root user, which usually has no other members.

The fourth column shows the size of the file in bytes, which is 531 in this case. The fifth and sixth columns show the date and time of the last modification of the file, which are Jun 5 22:45 in this case. The last column shows the name of the file, which is /etc/passwd in this case.

The other options are not correct because:

A. -rw------- 1 root root 531 Jun 5 22:45 /etc/passwd: This option has the wrong permissions for the file. The permissions are 600, which means only the user (root) can read and write the file, and the group and the others have no permissions at all. This would prevent the system users from reading the file, which would cause problems for the login process and other utilities that rely on the file.

C. -rw-r–r-- 1 1 531 Jun 5 22:45 /etc/passwd: This option has the wrong owner and group for the file. The owner and group are both 1, which is the numeric ID of the user and group. However, the numeric ID of the root user and group is 0, not 1. The user and group with the numeric ID of 1 are usually bin, which is a system user and group that own some system binaries and directories. The bin user and group should not own the /etc/passwd file, as this would compromise the security and functionality of the system.

D. -rw------- 1 1 531 Jun 5 22:45 /etc/passwd: This option has both the wrong permissions and the wrong owner and group for the file. The permissions are 600, which means only the user can read and write the file, and the owner and group are both 1, which is the numeric ID of the bin user and group. This would prevent the system users from reading the file, and give the bin user and group full access to the file, which would cause problems for the security and functionality of the system.

The permissions -rwSr-xr-x mean that the file is readable and writable by the owner, readable and executable by the group, and readable and executable by others. The S in the owner’s permissions indicates that the file has the SetUID bit set, which means that when the file is executed as a command, it will run with the effective user ID of the file owner, rather than the user who executed it. This allows the command to perform privileged operations that the user normally cannot do. For example, the /bin/passwd command has the SetUID bit set, so that it can modify the /etc/shadow file, which is only writable by root. References: LPI Linux Administrator, File Permissions and Attributes