(r4) LinuxSystem < Embedded

Tags: view all tags
---++ <font face="Liberation Sans, sans-serif"><font size="6">Exercises 1: Discovering Linux</font></font>
---++ Goal:

Today’s embedded systems are more powerful than many minicomputers we had some 20 years ago. The computer I worked on when starting my job at CERN was a Digital Equipment PDP-11 minicomputer with 128kBytes (kBytes not Mbytes!) and it had a removable hard disk with 600 Mbytes of storage space. Total cost of the machine was some 80 kUS$! This machine controlled our complete linear accelerator with some 1500 control parameters (power supplies, RF parameters, vacuum, instrumentation, operator consoles ….)

The Raspberry Pi we will be using during the hands-on part of the course has 1 Gbyte of RAM, a “hard disk” of 32 Gbytes and its CPU exceeds by far that of the PDP-11 mentioned above. This means that we can run a full blown operating system on this machine. In fact we will use a special Linux flavor, adapted to small machines, very similar to the Linux system we can run on PCs.

Our first goal is therefore to become acquainted with Linux, its file structure, its commands etc. and this can be done on the PC for which we have created a dedicated bootable USB disk.
---++ Exercise 1: Explore the Linux file system

The Linux file system has a tree like structure with “/” at its root (the root of the file structure is NOT /root, which is the home directory of the super user.

Start a terminal and try out a few commands.

Use the
   * <p>ls</p>
   * <p>tree</p>
   * <p>pwd</p>
   * <p>cd</p>
commands to explore the the file system starting at the file system root. Where are the commands located, where the libraries, where is your home directory?

Linux also has hidden files, how can you see them? (Hint: Linux has zillions of commands and even more options and you will never know them all. Use the <i>man </i>(man stands for “manual”) to learn more about a command and its options).
---++ Exercise 2: Create a file system structure for all exercises of this course

In your home directory, create subdirectories <i>exercises, bin,src (</i>use<i> mkdir). </i>Within<i> exercises</i>, create directories _problems, solutions, doc_. Within each of these create a subdirectory _exercise_1_. Put the file exercises_1.odt, attached to this page (see below) into ~/exercises/problems/exercises_1 (~ stands for your home directory). Print this structure using _tree_.

Open a !LibreOffice document and write down what you have done. Save this document under the name <i>$HOME/exercises/doc/exercise_1.odt. </i>Continue to document you work during this exercise such that at the end of the exercise session you have a document describing all your work.
---++ Exercise 3: Environment variables and shell startup

Have a look at all environment variables defined (_printenv_). What are the values of HOME, PATH, LANGUAGE, LOG_NAME?

To get the value of an environment variable print it (_echo_ command) with a $ in front (e.g. echo $HOME).

Have a look at hidden files in you home directory. You will find amongst many other files a file called <i>.bashrc. </i>Open this file with an editor (gedit, emacs, vi ...it is your choice!) and edit it adding three lines concerning _.bash_profile_ close to the end of the file (compare the comments), such that end of the file looks as follows:

<img alt="bashrc.png" height="293" src="%ATTACHURL%/bashrc.png" title="bashrc.png" width="650" />

Create a new file <i>.bash_profile </i>in your home directory and enter:

<font face="Courier New, monospace"># add $HOME/bin to the execution path</font>

<font face="Courier New, monospace">PATH=$PATH:$HOME/bin</font>

Save the file.

Print the current environment variable PATH. The execute: _source $HOME/.bash_profile_. Print the execution path again and observe differences.

Now create a new environment variable MY_VARIABLE:

_export MY_VARIABLE=It’s_Me\!_ and print it. Get rid of it using _unset_.
---++ Exercise 4: Redirection and pipes

To each executable 3 input output channels are associated:
   * <p>stdin</p>
   * <p>stdout</p>
   * <p>stderr</p>
_stdin_ corresponds to your keyboard, <i>stdout </i>and _stderr_ to your screen. stdout is used for any output the program produces through its print statements while stderr is reserved for error messages.

cd to $HOME/exercises/solutions/exercise_1

Now type _ps_ _ax_ and observe the result. What does the command do?

After that type ps ax &gt; runningNow.txt followed by<i> ls</i>. What did the system do?

Linux uses plenty of very small commands, which however can be combined to make up much more complex commands. This is done by connecting stdout of one command with stdin of the following one as follows: <i>cmd1 | cmd2. </i>The “|” defines a <i>pipe, </i>where stdout of cmd1 is connected to stdin of cmd2.

Example: Copy the lyrics of the Beatles song “Yesterday” to your solutions directory. You will find it with the uploaded files at the bottom of this page. Right click on it and select "S<i>ave Link as</i>". Then find out how many lines contain the word “yesterday”. Use the commands _grep_ and _wc_ to accomplish this. Use the _cat_, <i>more </i>or _less_ command on yesterday.txt to verify your result is correct.

Finally remove runningNow.txt (using _rm_) and type ps ax| tee runningNow.txt . What is the difference to ps ax &gt; runningNow.txt?
---++ Exercise 5: File permissions

Do an ls -l in your solutions/exercise_1 directory. Then do the same thing on /bin. Who can read, modify, write each file?

Now create a new file _yesterday.sh_ in solutions/exercise_1/with:

#!/bin/sh

followed by the command you typed when counting the number of “yesterdays”. Save the file.<br /> What are the permission of it? Then type<i> chmod +x</i> <i>yesterday.sh </i>and observe the change in permissions. Type <u>./</u><i>yesterday.sh</i>, what happens?
---++ Too easy?

For those who find the above exercises too easy and who want to do more (but who will not have support for this):
   * <p>What is the current version of the Linux kernel we run?</p>
   * <p>What is the current version of the gcc C compiler?</p>
   * <p>Try to find all files that have been modified within the last 24 h.</p>
   * <p>change all occurrences of “yesterday” in the Beatles song to “today” using the stream editor</p>
   * <p>Try to find a certain string within a file system subtree</p>
   * <p>invent your own exercise</p>

---++ Further reading:

Try http://linuxcommand.org/lc3_learning_the_shell.php.

Article text.

-- %USERSIG{UliRaich - 2017-01-03}%

---++ Comments

%COMMENT%
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who
png	bashrc.png	r1	manage	34.5 K	2017-09-06 - 11:02	UnknownUser
odt	exercises_1.odt	r1	manage	79.6 K	2017-09-06 - 10:28	UnknownUser
txt	yesterday.txt	r1	manage	0.7 K	2017-09-06 - 09:58	UnknownUser
Topic revision: r4 - 2017-09-06 - uli