Linux2 - Revision history

GethinWilliams: /* A final example */

2013-08-20T10:39:41Z

A final example

2013-08-20T10:07:36Z

Automating things

2010-07-05T15:59:21Z

2008-12-09T16:46:38Z

Environment Variables

2008-12-09T16:46:12Z

A final example

2008-12-09T16:44:53Z

Launching, monitoring and controlling jobs

2008-12-09T16:39:49Z

Automating things

2008-12-09T16:38:17Z

Pipelines

2008-12-09T16:37:54Z

Output redirection

2008-11-19T16:32:25Z

Getting the content for this practical

@@ Line 481: / Line 481: @@
 </pre>
-Then look at the html file using the SSH transfer file icon again.
+Then look at the html file using a web browser:
 Although this script is a bit silly, it combines most things you will ever need to do, namely:

@@ Line 146: / Line 146: @@
 </pre>
-Now use the file transfer icon in SSH to look into <tt>thumbnails.zip</tt>.
+Now use '''unzip -l''' to look into <tt>thumbnails.zip</tt>:
 This is a very simple script but already it shows that a simple batch file like this can perform some complex operations and make your life simpler. Let's go a bit further now.

@@ Line 10: / Line 10: @@
 The files for this practical are hosted in a version control system. To obtain them, just type the following command:
 <pre>
-$ svn export http://source.ggy.bris.ac.uk/subversion-open/linux2/trunk linux2
+$ svn export https://svn.ggy.bris.ac.uk/subversion-open/linux2/trunk linux2
 </pre>

@@ Line 476: / Line 476: @@
 =Environment Variables=
-The variables we have seen so far lived only inside our shell scripts. It is possible to have persistent variables. They are called environment variables. Actually, there are already plenty of environment variables declared for you. Just type <tt.env</tt> and be surprised at how much is there already.
+The variables we have seen so far lived only inside our shell scripts. It is possible to have persistent variables. They are called environment variables. Actually, there are already plenty of environment variables declared for you. Just type <tt>env</tt> and be surprised at how much is there already.
 You can ignore most of them but some of them are really important. They can ve re-used in shell scripts for instance.

@@ Line 466: / Line 466: @@
 </pre>
-Then look at the html file in your web browser.
+Then look at the html file using the SSH transfer file icon again.
 Although this script is a bit silly, it combines most things you will ever need to do, namely:

@@ Line 294: / Line 294: @@
 * check if you script is still running via <tt>ps</tt>
 * kill it
 Now that you can stop jobs and control their behaviour, it is time to learn how to build some more advanced shell scripts.

@@ Line 70: / Line 70: @@
 Most commands we have seen so far are fairly powerful but have a limited scope. This is intentional as the Linux command line allows to create a pipeline of commands to achieve a complex behaviour. For instance, <tt>ls</tt> is good at listing things and <tt>more</tt> is good at displaying things so let's pipe them together. This is done by using the pipe sign "<tt>|</tt>".
 <pre>
-$ ls -l ~ | more
+$ ls -l ~ | less
 -> more takes over the window if the output spans more than one screen
 </pre>

@@ Line 18: / Line 18: @@
 In the [[Linux1]] practical, we have discovered a few Linux commands. Some of these commands use input from the keyboard (standard input) and output data to the screen (standard output). It is possible to (a) redirect input and output and (b) link commands together to perform complex actions. The files for this section are in the <tt>example1</tt> directory.
 <pre>
-$ cd ../example1
+$ cd linux2/examples/example1
 </pre>

@@ Line 8: / Line 8: @@
 = Getting the content for this practical =
-The necessary files for this practical are hosted in a version control system. To obtain them, just type the following command:
+The files for this practical are hosted in a version control system. To obtain them, just type the following command:
 <pre>
 $ svn export http://source.ggy.bris.ac.uk/subversion-open/linux2/trunk linux2