Free Practice Questions for LPI 101-500 Exam

The most likely reason for getting an error when creating a hard link to an ordinary file is that the source and the target are on different filesystems. A hard link is a directory entry that points to the same inode as the original file. An inode is a data structure that stores the metadata and location of a file on a filesystem. A hard link cannot span across different filesystems because each filesystem has its own inode table and numbering scheme. Therefore, a hard link can only refer to a file that exists on the same filesystem as the link. This is mentioned in the article by How-To Geek1 and the man page of ln2. The other options are not valid reasons for getting an error when creating a hard link. The source file being hidden, read-only, or a shell script does not affect the ability to create a hard link, as long as the user has the appropriate permissions. The source file being already a hard link also does not prevent creating another hard link to the same file, as long as the maximum number of links per inode is not exceeded. This is explained in the article by Linuxize3 and the man page of ln

The utility that can be used to change how often a filesystem check is performed on an ext2 filesystem without losing any data stored on that filesystem is tune2fs. This command can adjust various parameters of a Linux ext2, ext3, or ext4 filesystem, such as the maximum mount count, the check interval, the reserved blocks percentage, and the default mount options. To change the check interval, the -i option can be used, followed by a time value. For example, to set the check interval to 180 days for the filesystem on /dev/sda1, the following command can be used:

sudo tune2fs -i 180d /dev/sda1

This command will modify the superblock of the filesystem, which contains the metadata and configuration information, without affecting the data stored on the filesystem. The other options are incorrect because they are not suitable for changing the check interval of an ext2 filesystem. Option A is wrong because there is no such utility as mod2fs. Option B is wrong because fsck is a utility for checking and repairing filesystems, not changing their parameters. Option D is wrong because mke2fs is a utility for creating ext2 filesystems, which will erase the existing data on the partition. Option E is wrong because there is no such utility as fixe2fs.

For more information on how to use the tune2fs command, you can refer to the following articles:

15 tune2fs command examples in Linux [Cheat Sheet] - GoLinuxCloud

Linux tune2fs command With Examples - GeeksforGeeks

tune2fs command-file system management - Linuxstar

tune2fs Command Examples - Gianforte School of Computing

tune2fs Command - IBM

According to the Filesystem Hierarchy Standard (FHS), the /usr/local/ directory is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated. The /usr/local/bin/ directory is for local binaries that are not managed by the distribution package manager. These binaries should be accessible to all users on the system. Therefore, binaries that have been compiled by the system administrator should be placed in /usr/local/bin/ to follow the FHS. References:

Filesystem Hierarchy Standard - Linux Foundation

Filesystem Hierarchy Standard (FHS) | Linux# - Geek University

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 system configuration file named /etc/inittab is commonly used to set the default runlevel. This file contains information about the initialization process of the system, and it defines the default runlevel, the available runlevels, and the actions to be taken when entering or leaving a runlevel. The default runlevel is the mode of operation that the system starts up into, and it determines which services and processes are running. The default runlevel 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 runlevel, which can range from 0 to 6. The meaning of each runlevel 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 runlevel, edit the /etc/inittab file as root and change the number to the desired runlevel. For example, to change the default runlevel 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.

The correct commands to create an ext3 filesystem on /dev/sdb1 are /sbin/mke2fs -j /dev/sdb1 and /sbin/mkfs -t ext3 /dev/sdb1. These commands format the partition /dev/sdb1 with the ext3 filesystem type. The first command uses the mke2fs utility with the -j option, which enables journaling. The second command uses the mkfs utility with the -t option, which specifies the filesystem type. Both commands are equivalent and can be used interchangeably. The other options are incorrect because they use the wrong syntax or parameters for the commands. Option C is wrong because the -c option for the mkfs command checks the device for bad blocks, not the filesystem type. Option D is wrong because there is no such utility as mke3fs. The correct utility name is mke2fs.