From b5f1dca291e477818f097d8c4ab341f30ea5b31e Mon Sep 17 00:00:00 2001 From: merlllle Date: Mon, 21 Feb 2022 15:01:40 +0000 Subject: [PATCH 1/2] Add remote access tips --- docs/labs/LAB5.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/labs/LAB5.md b/docs/labs/LAB5.md index 5fb0553..ed8decd 100644 --- a/docs/labs/LAB5.md +++ b/docs/labs/LAB5.md @@ -32,6 +32,8 @@ endeavor to fix any issue quickly. Finally, make sure you do the **exercises** properly. +If you are doing the lab remotely, read the [remote access tips](#remote-access) first is recommanded. + ## Tools You are second year computer science students and we expect some autonomy @@ -517,3 +519,27 @@ We hope you enjoyed this short introduction to Linux. This lab was developed thanks to material available at [Harvard 0S/161](http://os161.eecs.harvard.edu/), [ops-class](https://ops-class.org/) and [OS/161 at UBC](https://sites.google.com/site/os161ubc/home). + +## Remote access + +If you are doing this lab remotely, you can use the `ssh` command from [lab 3](https://github.com/cs-uob/COMS20012/blob/master/docs/labs/LAB3.md): + +```sh +# Please change ab12345 to your username +ssh -J ab12345@seis.bris.ac.uk ab12345@rd-mvb-linuxlab.bristol.ac.uk +``` + +But since vagrant will write files to tmp directory, which is not shared between different lab machines, vagrant will redownload and reinstall everything which will take ~5 min every time you are on a new machine, so it might save some time if you stick on one lab machine. Here is how to do it: + +1. When you use the above command to `ssh` into the lab, you will be rondamly allocated a machine. + +2. To find out which machine you are on, look at the prompt after you log in. It will be something like this: +```sh +[ab12345@it075733 ~]$ +``` +`ab12345` is your username and `it075733` is the machine id. + +3. Write down the machine id so that next time you can directly `ssh` into that machine by +```sh +.\ssh -J ab12345@seis.bris.ac.uk ab12345@it075733.wks.bris.ac.uk +``` From 71285a7a8db9ef295ab4046c09938b3c58a9944f Mon Sep 17 00:00:00 2001 From: merlllle Date: Mon, 21 Feb 2022 15:28:46 +0000 Subject: [PATCH 2/2] Add COMS10012 link --- docs/labs/LAB5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/labs/LAB5.md b/docs/labs/LAB5.md index ed8decd..32d6435 100644 --- a/docs/labs/LAB5.md +++ b/docs/labs/LAB5.md @@ -529,7 +529,7 @@ If you are doing this lab remotely, you can use the `ssh` command from [lab 3](h ssh -J ab12345@seis.bris.ac.uk ab12345@rd-mvb-linuxlab.bristol.ac.uk ``` -But since vagrant will write files to tmp directory, which is not shared between different lab machines, vagrant will redownload and reinstall everything which will take ~5 min every time you are on a new machine, so it might save some time if you stick on one lab machine. Here is how to do it: +But since IT has configured vagrant on the lab machines to store VMs in the `/tmp` directory (according to [COMS10012](https://cs-uob.github.io/COMS10012/exercises/part1/posix1/install.html#warning-about-lab-machines---read-carefully)), which is not shared between different lab machines, vagrant will redownload and reinstall everything which will take ~5 min every time you are on a new machine, so it might save some time if you stick on one lab machine. Here is how to do it: 1. When you use the above command to `ssh` into the lab, you will be rondamly allocated a machine.