33. How to read this book#

This book has been designed so that you can actively engage with the material. We have constructed an online environment that you can login to from your browser. Once you have logged in you can then start a “server” that you can then access in your browser. This server is identical to the server that was used to author the content of the book and has all the software required for the examples and more.

In general we recommend that you read the book at a computer with a mouse and keyboard so that you can follow along with the examples. Below we will walk you though a typical session of work with the book.1

33.1. Browser compatibility#

The author recommends using the Google Chrome browser but most of the content should work with most browsers. If you run into issues please open an issue and the try switching browsers to see if this solves your problem.

33.2. Opening an issue#

Towards the top at the top right hand side of the page you will see a few icons. Putting your mouse over the git icon will reveal a dropdown. Select “open issue” and follow the instructions. Be sure to state what browser you were using and what the problem was. If possible include a screenshot.

Thanks!

33.3. WARNING – DANGER#

The files you create within your Linux server are NOT PERMANENT! In other words you cannot rely on the files to be there if the server crashes for some reason, it gets shutdown due to inactivity, or you purposefully shut it down. Every time you make a change to your code you are expected to save your work to your github repo.

33.4. Step 0: Start your server#

If you are in a BU class that is using this book, follow this link:

33.4.1. BU Server startup#

Clicking on the above link should take you to the following page:

Clicking "Login with OpenShift". This will take you to the page displayed below.
Click "GoogleBU". This will take you to the following login page.
Enter your BU username and password and then click "Continue". This may then redirect you to BU's two factor authentication service as shown below
Select your choice of authentication mechanism. If you are not able to login try again using an "incognito" browser window". If you still cannot login and you are sure you are in a class that is using the book please contact the teaching staff and they will add your BU user to the service.

33.4.2. Booting your server#

After login you should be presented with the following panel. You will need to:

  1. Select the right “Notebook Image” (“UCSLS UNIX Environment” or “Under the Covers: The Secret Life of Software”),

  2. Select “Start server in current tab”, and then

  3. click on the “Start Server” button.

You then should observe the following sequence progress as your server starts up

At this point you may be presented again with the following login page on which you should again select “GoogleBU”.

33.5. UNIX Terminal Environment#

After the boot process you should be presented with the UNIX terminal environment that we will be using as illustrated below.

>

33.5.1. Creating Terminals#

Use the “File” menu to select “New” then “Terminal”. This should start a Terminal as shown below:

Using the “File->New->Terminal” menu option again lets you create more terminals. Each terminal will have its own tab as shown below.

You can create and organize as many terminals as you like. Dragging the “Terminal” tab title bar around will allow you to adjust the layout. For example, below we have started three terminals and organized them in two rows – two on the first row and one on the second.

33.5.2. Closing Terminals#

To close a terminal simply click the “x” in the terminal’s tab title bar.

33.6. UNIX Terminal Environment “Lifetime”#

Your UNIX terminal environment is temporary. It will automatically be destroyed. This will happen:

  1. After a period of inactivity

  2. 12 hours after you started it

Rather than letting the system destroy your environment arbitrarily it is best for you to shut it down yourself when you are done your work, see below.

33.6.1. WARNING#

Given the temporary nature of the environment you should be aware that ANY FILES YOU HAVE WITHIN IT WILL BE DESTROYED when it shuts down. When you start a new one it will reset to a fresh clean state.

This is intentional; you are expected to commit your work frequently back to github classroom along with a message explaining your commit. Your history of commits is something you are expected to be able to explain when reviewing your homework assignment.

33.7. Shutting Down Your Server#

When you have finished your session of working it is important that you shutdown your server. To shutdown the server select the “Hub Control” feature from the “File” menu as illustrated below

33.7.1. Hub Control Panel#

This will open a new tab or window with following page:

This may present you with a confirmation panel. Click “Stop server” to confirm.

33.7.2. Shutdown#

At this point the browser tab or window that you used for your work session will no longer be valid, see below, and you can safely close it.

1

This material comes from jonathan’s systems book here, but we expect minor tweaks to creep in as we gain experience with the OS class and eventually we will be pointing to different images, etc…