Scribd
Upload
19 views

LINUX Section2-Lab

Uploaded by

ptvjay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views

LINUX Section2-Lab

Uploaded by

ptvjay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Section 2 Lab

LPIC-1, Exam 1 (101-500)


By Christine Bresnahan
Recommended Linux Distributions for this exercise:
 CentOS version 7
 Ubuntu Desktop 18.04LTS

Note: For a successful lab session, it is assumed you are using the recommended Linux distribution(s) and
the recommended version, and that your Linux systems are booted. In addition, it is assumed that you can log
into the system as a standard user as well as either the root account or a user with super user privileges.

Follow these actions to explore concepts and commands covered in this section (but please feel free to
explore as much as you want):
1. Log into your Ubuntu distro graphical user interface (GUI), using the username and password you
created when you installed the system, and open a terminal emulator app. (I let you figure this one out.
We did something similar in the previous lab on a CentOS distribution.)
2. Try out the uname command.
3. View the man pages for the uname command, by typing man uname and pressing Enter. Record some
options for the command to try at the command line.
4. Press the Q (lowercase q) key to leave the man pages.
5. Try out the uname command along with the options you recorded in step #3.
6. Use the which command on the uname program by typing in which uname and pressing Enter. Notice
the absolute directory reference displayed.
7. Use the type command on the uname program by typing type uname and pressing Enter. From the
results, is uname built into the Bash shell program or an external command? (You should discover that it
is an external command.)
8. Use the type command on the cd program. Is the cd program built into the Bash shell or an external
command? (You should discover that it is built into the Bash shell program.)
9. View your command history list, by typing history and pressing Enter.
10. Pick a command from the list and record its number.
11. Type !command-history-number, where “command-history-number” is the number you recorded in the previous
step and press Enter. Did the command display and then execute? If it did not, review the last few steps
and find your potential mistake.
12. Type ls .bash_history to show a file listing of your Bash history file.
13. Type !! and press Enter. Did your previous command run? If it did not, review the command in this step,
and see what changes you need to make.

You might also like