Free LPI 101-500 Practice Exam with Questions & Answers | Set: 2

The dd command can be used to create a new file that is 100kB in size. The dd command copies data from one source to another, using specified input and output block sizes. To create a new file that is 100kB in size, the dd command can use /dev/zero as the input source, which provides an endless stream of zeros, and specify the output file name, the output block size (bs) and the count of blocks to copy. For example, dd if=/dev/zero of=file.txt bs=1k count=100 will create a file named file.txt that is 100kB in size. The file command can be used to determine the type of a file. The mkfile command is not a valid Linux command. The touch command can be used to create a new empty file or update the access and modification times of an existing file, but it does not specify the size of the file. References: [LPI Exam 101 Detailed Objectives], Topic 103: GNU and Unix Commands, Weight: 25, Objective 103.3: Perform basic file management, dd command, file command, touch command

The BIOS (Basic Input/Output System) is a firmware program that is stored in a ROM chip on the motherboard, and it performs some basic tasks when the system is powered on, such as:

initializing the hardware components and peripherals

performing the power-on self-test (POST) to check the system integrity

selecting a boot device from the boot order list

loading and executing the bootloader program from the boot device

The boot device is the data carrier that contains the bootloader, which is a small program that is responsible for loading and executing the kernel. The boot device can be a hard disk, a USB drive, a CD-ROM, or a network device. The BIOS has a boot order list, which is a sequence of possible boot devices that the BIOS will search for a valid bootloader. The boot order list can be configured by the user through the BIOS setup utility, which is usually accessed by pressing a key such as F2, F10, or Del during the POST.

The BIOS will search for a bootloader by means of a special signature, which is a sequence of bytes that indicates the presence of a bootloader. The signature is usually located in the first sector of the boot device, which is called the boot sector or the master boot record (MBR). The BIOS will read the boot sector of each boot device in the boot order list, and check if the last two bytes are 0x55 and 0xAA, which are the standard boot signature. If the boot signature is found, the BIOS will load the boot sector into memory and execute it. If the boot signature is not found, the BIOS will move on to the next boot device in the boot order list. If none of the boot devices have a valid boot signature, the BIOS will display an error message such as:

No bootable device – insert boot disk and press any key

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 correct device file name for the second partition on the only SCSI drive is /dev/sda2. This is because SCSI drives use the naming scheme sdX, where X is a letter starting from a for the first drive, b for the second drive, and so on. The partitions on each drive are numbered from 1 to the maximum number of partitions supported by the drive. Therefore, the first partition on the first SCSI drive is /dev/sda1, the second partition on the first SCSI drive is /dev/sda2, the first partition on the second SCSI drive is /dev/sdb1, and so on. The other options are incorrect because they do not follow the SCSI naming scheme. Option A is wrong because it uses the naming scheme for IDE drives, which is hdX. Option C is wrong because it uses the naming scheme for BSD drives, which is sdXaY, where X is a number and Y is a letter. Option D is wrong because it uses the naming scheme for Solaris drives, which is sdXpY, where X is a number and Y is a number. References:

[LPI Linux Essentials - 2.1 Using Devices, Linux Filesystems, Filesystem Hierarchy Standard]

[LPI Linux Essentials - 2.2 Mounting, Unmounting Filesystems]

[LPI Linux Essentials - 2.3 Disk Partitions]

Device file - ArchWiki

What is the Linux drive naming scheme? - Ask Ubuntu

The correct command to change the quota for a specific user is edquota. This command allows you to edit the quota limits for a user, a group, or a file set. You can specify the name of the user that you want to edit the quotas for after the command. For example, to change the disk quota for user ‘linuxconfig’, you can use the following command:

sudo edquota -u linuxconfig

This command will open an editor with the current quota information for the user ‘linuxconfig’. You can modify the soft and hard limits for the block and inode usage as per your requirements. You can also use the -p option to copy the quota settings from another user. For example, to copy the quota settings from user ‘ramesh’ to user ‘linuxconfig’, you can use the following command:

sudo edquota -p ramesh -u linuxconfig

The other commands are not suitable for changing the quota for a specific user. The repquota command displays a summary of the current quota usage and limits for the users or groups. The quota -e command turns off the disk quota for the current user. The quota command shows the disk quota and usage for the current user or for the users specified on the command line. For more information on how to use disk quota on Linux, you can refer to the following articles:

How to use disk quota on Linux with examples

5 Steps to Setup User and Group Disk Quota on UNIX / Linux

The first program the Linux kernel starts at boot time when using System V init is /sbin/init. System V init is a traditional init system that uses a series of shell scripts to initialize and manage the system services. The init program is the parent of all other processes and it is responsible for reading the /etc/inittab file and executing the appropriate scripts for each runlevel. The /sbin/init program is part of the 101.1 Determine and configure hardware settings topic of the LPI Linux Essentials certification program12. References:

Linux Essentials - Linux Professional Institute Certification Programs1

Exam 101 Objectives - Linux Professional Institute2

A guide to System V Init3

Linux Init Levels Explained: Init 0 - Init 64

Init Systems Unveiled — Understanding the Differences Between Systemd and SystemV5

The command that searches for packages owning the file /etc/debian_version is dpkg –S /etc/debian_version. The dpkg command is the low-level tool for installing, removing, configuring, and querying Debian packages. The -S or --search option takes a file name or a pattern as an argument and searches for the packages that contain the matching files. The output shows the package name and the file name separated by a colon. For example, running dpkg -S /etc/debian_version will produce the output base-files:/etc/debian_version, indicating that the file /etc/debian_version belongs to the base-files package. The other commands are either invalid or do not perform the desired task. The apt-get command is used to download and install packages from the Debian repositories, but it does not have a search option. The apt command is a high-level tool for managing packages, but it does not have a -r option. The find command is used to search for files in the file system, but it does not have a -dpkg option. The apt-file command is used to search for files in the packages available in the Debian repositories, but it requires a subcommand such as search or show before the file name or pattern. References:

Linux Essentials - Linux Professional Institute Certification Programs1

Exam 101 Objectives - Linux Professional Institute2

dpkg(1) - Linux manual page3

apt-get(8) - Linux manual page

apt(8) - Linux manual page

find(1) - Linux manual page

apt-file(1) - Linux manual page

[character list] matches any one of the characters in the list. ? matches any single character. * matches any number of characters, including none.

Therefore, the wildcard ttyS[1-5] will match any filename that starts with ttyS and ends with a digit from 1 to 5, such as ttyS1, ttyS2, ttyS3, ttyS4, or ttyS5. However, it will not match ttyS0, which has a 0 at the end.

The wildcard tty?[0-5] will match any filename that starts with tty, followed by any single character, followed by a digit from 0 to 5, such as ttyS0, ttyS1, ttyS2, ttyA0, ttyB5, or ttyZ4. This wildcard will match all the given filenames.

The wildcard tty*2 will match any filename that starts with tty and ends with 2, such as ttyS2, ttyA2, ttyB2, or ttyZZZ2. This wildcard will match ttyS2, but not the other two filenames.

The wildcard tty[A-Z][012] will match any filename that starts with tty, followed by a capital letter from A to Z, followed by a digit from 0 to 2, such as ttyA0, ttyB1, ttyC2, ttyZ0, or ttyZ2. This wildcard will match ttyS0 and ttyS2, but not ttyS1, which has a 1 at the end.

The wildcard tty[Ss][02] will match any filename that starts with tty, followed by either S or s, followed by either 0 or 2, such as ttyS0, ttyS2, ttys0, or ttys2. This wildcard will match ttyS0 and ttyS2, but not ttyS1, which has a 1 at the end.