Pass the LPI Linux Essentials 010-160 Questions and answers with ExamsMirror

The correct command to change the ownership of the file doku.odt to a new owner named tux is chown tux doku.odt. This command uses the chown command, which stands for change owner, followed by the name of the new owner and the name of the file as arguments. The chown command allows you to change the user and/or group ownership of a given file, directory, or symbolic link12. The other options are incorrect because they use different commands or syntax that do not change the ownership of the file. For example:

Option A uses the chmod command, which stands for change mode, and is used to change the permissions of files and directories, not the ownership3.

Option B uses the newuser command, which is used to create a new user account, not to change the ownership of a file4.

Option D uses the transfer command, which is not a valid Linux command.

Option E uses the passwd command, which is used to change the password of a user account, not the ownership of a file5.

The files /etc/passwd and /etc/group are the source of the information in the following output:

uid=1000 (bob) gid=1000 (bob) groups=1000 (bob), 10 (wheel), 150 (docker), 1001 (libvirt) (wireshark), 989

The /etc/passwd file contains information about user accounts, such as the username, password, user ID (UID), group ID (GID), full name, home directory, and login shell1. The /etc/group file contains information about groups, such as the group name, password, group ID (GID), and members2.

The output shows the UID, GID, and group membership of the user bob. The UID and GID of bob are 1000, which can be found in the /etc/passwd file. The groups that bob belongs to are bob, wheel, docker, libvirt, wireshark, and 989, which can be found in the /etc/group file. The group names are shown in parentheses after the GID, except for the last group, which has no name.

The other options are not files that store user and group information in Linux. The /etc/id file does not exist by default. The /home/index file is not a standard file and has no relation to user and group information. The /var/db/users file is not a standard file and has no relation to user and group information. References:

Linux Essentials Exam Objectives, Version 1.6, Topic 103.1, Weight 2

Linux Essentials Certification Guide, Chapter 3, Page 51-52

Linux Filesystem Hierarchy, Chapter 3, Page 17-18

Linux Users and Groups, Chapter 2, Page 9-10

The correct command to copy the two files ending in .txt to the /tmp/ directory is cp *.txt /tmp/. This command uses the wildcard character * to match any number of characters before the .txt extension. Therefore, it will copy both texts 1.txt and texts 2.txt to the destination directory /tmp/. The other options are incorrect because they use different wildcard characters or syntax that do not match the desired files. For example, option A uses ?? to match exactly two characters before the .txt extension, but the files have a space and a number, which are not considered as one character. Option C uses a backslash \ to escape the dot . before the .txt extension, but this is unnecessary and will cause the command to fail. Option D uses ? to match exactly one character before the .txt extension, but the files have more than one character. Option E uses $? to match the exit status of the previous command before the .txt extension, but this is not relevant and will cause the command to fail123 References: 1: Linux wildcards | How do wildcards work in Linux with examples? - EDUCBA 2: Wildcards in Linux explained with 10 examples | FOSS Linux 3: What are wildcard characters in Linux? – Sage-Answers

 A shell script is a file that contains a series of commands that can be executed by a shell interpreter. To execute a shell script, there are two main methods:

Method 1: Specify the path to the script file. This method requires that the script file has the execute permission, which can be granted by using the chmod command. The script file also needs to have a shebang line at the beginning, which indicates which interpreter to use for the script. For example, #!/bin/bash means to use the bash interpreter. To execute the script using this method, you can type the absolute path or the relative path to the script file. If you are in the same directory as the script file, you can use the ./ prefix to indicate the current directory. For example, ./test.sh will execute the test.sh script in the current directory.

Method 2: Pass the script file as an argument to the interpreter. This method does not require the execute permission or the shebang line for the script file. You can simply use the name of the interpreter followed by the script file name as an argument. For example, bash test.sh will execute the test.sh script using the bash interpreter.

Therefore, the correct answers are D and E. A. run test.sh is incorrect because run is not a valid command in Linux. B. ${test.sh} is incorrect because this syntax is used for variable expansion, not for executing a script. C. cmd ./test.sh is incorrect because cmd is not a valid command in Linux. References:

Linux Essentials Topic 105: The Power of the Command Line, section 105.3: Basic shell scripting.

How to Run a Shell Script in Linux [Essentials Explained] - It’s FOSS

How To Execute a Command with a Shell Script in Linux | DigitalOcean

How To Run the .sh File Shell Script In Linux / UNIX

 The sort command is used to sort the lines of a text file or the output of another command in alphabetical, numerical, or other order. The sort command has the following syntax: sort [options] [file…]. The file argument is the name of one or more files to be sorted. If no file is given, the sort command reads from the standard input, which is usually the keyboard or the output of another command.

The | (pipe) symbol is used to connect the output of one command to the input of another command. This allows the creation of pipelines of commands that process data sequentially. The pipe symbol has the following syntax: command1 | command2. The command1 argument is the name of the first command, whose output is sent to the input of the second command. The command2 argument is the name of the second command, which receives the output of the first command as its input.

Therefore, the command export-logs | sort sorts the output of the export-logs command in alphabetical order. The export-logs command is assumed to be a custom command that exports some logs to the standard output. The sort command receives the output of the export-logs command as its input and sorts it according to the default criteria, which is the first character of each line. The sorted output is then displayed on the screen or can be redirected to a file or another command.

The other options in the question are incorrect because they use the wrong symbols to connect the commands. The < (input redirection) symbol is used to read the input of a command from a file instead of the keyboard. The > (output redirection) symbol is used to write the output of a command to a file instead of the screen. The & (background) symbol is used to run a command in the background, which means the command does not wait for user input and allows the user to run other commands simultaneously. The <> (bidirectional redirection) symbol is used to read and write the input and output of a command from and to the same file. None of these symbols can be used to sort the output of the export-logs command. References:

Linux Essentials Version 1.6 Objectives: 3.2. Searching and Extracting Data from Files1

Linux Essentials Version 1.6 Exam Study Resources: Linux Essentials Manual - Chapter 9. The Power of the Command Line - 9.2. Searching and Extracting Data from Files - 9.2.1. The sort Command2

Linux Essentials Version 1.6 Exam Study Resources: Linux Essentials Manual - Chapter 9. The Power of the Command Line - 9.3. Turning Commands into a Script - 9.3.1. Pipes and Redirection2

Linux Essentials Version 1.6 Exam Study Resources: Linux Essentials Manual - Appendix A. Answers to the Exercises - Chapter 9. The Power of the Command Line - 9.2. Searching and Extracting Data from Files - Exercise 9.2.12

Linux Essentials Version 1.6 Exam Study Resources: Linux Essentials Manual - Appendix A. Answers to the Exercises - Chapter 9. The Power of the Command Line - 9.3. Turning Commands into a Script - Exercise 9.3.12

The execute bit in Linux is a permission bit that allows the user to run an executable file or enter a directory. For regular files, such as scripts or binaries, the execute bit must be set for the user to run them. For directories, the execute bit allows the user to access the files and subdirectories inside. Therefore, to successfully execute the script test.sh, the execute bit should be set in the file’s permissions. This can be done by using the chmod command with the +x option, for example: chmod +x test.sh. The other options are either irrelevant or incorrect. The file’s extension does not affect its executability, only its association with a program. The user executing the script does not need to be in the exec group, as long as the user has the execute permission on the file. The SetUID bit is a special permission bit that allows the user to run the file as the file’s owner, regardless of the user’s identity. This is not necessary for executing the script, and may pose a security risk. The #!./test.sh syntax is invalid, as the #! is used to specify the interpreter for the script, not the script itself. References:

Linux Essentials Version 1.6 Objectives1, Topic 1.4: Command Line Basics, Subtopic: Basic Shell Commands

Linux Essentials Version 1.6 Exam Preparation Guide2, Section 1.4: Command Line Basics, Page 16

Execute vs Read bit. How do directory permissions in Linux work?3

The correct permissions for the /tmp directory are rwxrwxrwt, which means that the owner, group, and others have read, write, and execute permissions, and that the sticky bit is set. The sticky bit is a special permission that prevents users from deleting or renaming files that they do not own in a shared directory. The /tmp directory is used for storing temporary files that may be created by different users and processes, so it needs to be accessible and writable by all, but also protected from unauthorized deletion or modification of files. The rwxrwxrwt permissions can be set by using the chmod command with either the octal mode 1777 or the symbolic mode a+trwx. References: : [File system permissions] : [Sticky bit] : [chmod]

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. Each line of the /etc/passwd file contains seven comma-separated fields, representing a user account. The fields are as follows:

Username: The string you type when you log into the system. Each username must be a unique string on the machine. The maximum length of the username is restricted to 32 characters.

Password: In older Linux systems, the user’s encrypted password was stored in the /etc/passwd file. On most modern systems, this field is set to x, and the user password is stored in the /etc/shadow file.

User ID (UID): The user identifier is a number assigned to each user by the operating system to refer to a user. It is used by the kernel to check for the user privileges and grant access to system resources. The UID 0 is reserved for the root user and cannot be assigned to any other user.

Group ID (GID): The user’s group identifier number, referring to the user’s primary group. When a user creates a file, the file’s group is set to this group. Typically, the name of the group is the same as the name of the user. User’s secondary groups are listed in the /etc/group file.

User ID Info (GECOS): This is a comment field. This field contains a list of comma-separated values with the following information: User’s full name or the application name, Room number, Work phone number, Home phone number, Other contact information.

Home directory: The absolute path to the user’s home directory. It contains the user’s files and configurations. By default, the user home directories are named after the name of the user and created under the /home directory.

Login shell: The absolute path to the user’s login shell. This is the shell that is started when the user logs into the system. On most Linux distributions, the default login shell is Bash.

Therefore, the correct answers are B, C, and E. The user’s storage space limit (A) is not stored in the /etc/passwd file, but in the /etc/quota file. The encrypted password (D) is not stored in the /etc/passwd file, but in the /etc/shadow file. References:

Linux Essentials Topic 104: The Linux Operating System, section 104.4: Runlevels and Boot Targets.

Linux Essentials Topic 106: Security and File Permissions, section 106.1: Basic security and identifying user types.

Linux Essentials Topic 106: Security and File Permissions, section 106.2: Creating users and groups.

Understanding the /etc/passwd File | Linuxize

Understanding the /etc/passwd File - GeeksforGeeks

passwd(5) - Linux manual page - man7.org

Understanding /etc/passwd file in Linux - DEV Community

 In Linux, every file and directory is associated with an owner and a group. The owner is the user who created the file or directory, and the group is the group to which the owner belongs. Therefore, each file is owned by exactly one user and one group. This is true for option A. The other options are false for the following reasons:

Option B: The owner of a file does not always have full permissions when accessing the file. The permissions are determined by the file mode, which can be changed by the owner or the root user. The file mode specifies the read, write, and execute permissions for the owner, the group, and others. The owner can have different permissions than the group or others.

Option C: The user owning a file does not have to be a member of the file’s group. The owner can change the group ownership of the file to any group on the system, regardless of whether the owner belongs to that group or not. However, only the root user or a user with the CAP_CHOWN capability can change the group ownership to a group that the owner is not a member of.

Option D: When a user is deleted, all files owned by the user do not disappear. The files remain on the system, but their owner is changed to an invalid user ID (UID). The files can still be accessed by the group or others, depending on the permissions. The files can also be reclaimed by the root user or a user with the CAP_CHOWN capability, who can change the owner to a valid user.

Option E: The owner of a file can be changed once it is assigned to an owner. The owner can transfer the ownership to another user, or the root user or a user with the CAP_CHOWN capability can change the owner to any user on the system. The command to change the owner of a file is chown. References: 1: Chown Command in Linux (File Ownership) | Linuxize 2 3: Linux File Permissions and Ownership Explained with Examples 4 2: 3 Ways to Find File Owner in Linux - howtouselinux 1

DHCP stands for Dynamic Host Configuration Protocol. It is a protocol that provides quick, automatic, and central management for the distribution of IP addresses within a network. It also configures other network information, such as the subnet mask, default gateway, and DNS server information, on the device1. DHCP uses a client/server architecture, where a DHCP server issues unique IP addresses and automatically configures the devices that request them2. DHCP allows devices to move freely from one network to another and receive an IP address automatically, which is helpful with mobile devices1.

The other options are not protocols used for automatic IP address configuration. NFS stands for Network File System, which is a protocol that allows a user to access and modify files over a network as if they were on their own computer. LDAP stands for Lightweight Directory Access Protocol, which is a protocol that provides access to a centralized directory service that stores information about users, groups, computers, and other resources on a network. SMTP stands for Simple Mail Transfer Protocol, which is a protocol that enables the sending and receiving of email messages over a network. DNS stands for Domain Name System, which is a protocol that translates domain names into IP addresses and vice versa. References:

Linux Essentials Exam Objectives, Version 1.6, Topic 105.1, Weight 4

What Is DHCP? (Dynamic Host Configuration Protocol) - Lifewire

Dynamic Host Configuration Protocol (DHCP) | Microsoft Learn

Dynamic Host Configuration Protocol - Wikipedia

How does AutoIP work? - Barix

[Network File System - Wikipedia]

[Lightweight Directory Access Protocol - Wikipedia]

[Simple Mail Transfer Protocol - Wikipedia]

[Domain Name System - Wikipedia]