Fix out-of-date “play.sh” and “cd” commands

README.md

@@ -86,7 +86,7 @@ these machines are several hops away — hops that can be inspected by
 normal networking tools like `traceroute`:
 
 ```
-$ ./play.sh h1
+$ ssh h1
 
 # traceroute www.example.com
 traceroute to www.example.com (10.130.1.4), 30 hops max, 60 byte packets

playground/README.md

@@ -157,9 +157,10 @@ pre-packaged virtual machine image:
         $ ./launch.sh
 
 Once the above steps are completed, you should be able to get a root
-prompt on any of the machines by using the `play.sh` script.
+prompt on any of the machines by making an SSH connection to any of the
+machines `h1`, `h2`, `h3`, or `h4`:
 
-    $ ./play.sh h1
+    $ ssh h1
 
     root@h1:/# pwd
     /

playground/launch.sh

@@ -212,3 +212,11 @@ sudo ip netns exec www ip addr add 10.130.1.4/24 dev eth0
 for name in ftp mail www
 do sudo ip netns exec $name ip route add default via 10.130.1.1
 done
+
+cat <<'EOT'
+
+Playground set up successfully! To enter, now run the command:
+
+    ssh h1
+
+EOT

py3/chapter07/README.md

@@ -61,14 +61,14 @@ on the `ftp.example.com` host, where `inetd` happens to already be
 running to provide a Telnet service for the scripts in Chapter 16.  Once
 you have the playground running, create a client host like `h1`:
 
-    $ ./play.sh h1
+    $ ssh h1
 
 Because each client host auto-mounts the `py3` directory, you will have
 access to the scripts and configuration file that need to be copied over
 to `ftp.example.com` for the two services to run.  You can perform the
 copy using the following commands on host `h1`:
 
-    # cd /py3/chapter07
+    # cd /fopnp/py3/chapter07
     # scp in_zen1.py in_zen2.py zen_utils.py ftp.example.com:/
     # scp inetd.conf ftp.example.com:
     # ssh ftp.example.com

py3/chapter13/README.md

@@ -25,9 +25,9 @@ already set up and configured to receive incoming email.  Once the
 playground is running, ask for a prompt on the `h1` host and visit the
 `chapter13` directory:
 
-    $ ./play.sh h1
+    $ ssh h1
 
-    # cd py3/chapter13
+    # cd /fopnp/py3/chapter13
 
 At the `h1` machine’s prompt you can then experiment with sending
 messages across the network.  The `simple.py` script and the slightly

py3/chapter14/README.md

@@ -28,9 +28,9 @@ The scripts in this chapter are best exercised inside the network
 already set up and configured for POP.  Once the playground is running,
 ask for a prompt on the `h1` host and visit this chapter’s directory:
 
-    $ ./play.sh h1
+    $ ssh h1
 
-    # cd py3/chapter14
+    # cd /fopnp/py3/chapter14
 
 All of the scripts in this chapter are careful to use the `POP3_SSL`
 class and therefore guarantee the use of TLS to protect the user’s

py3/chapter15/README.md

@@ -24,9 +24,9 @@ The scripts in this chapter are best exercised inside the network
 already set up and configured for POP.  Once the playground is running,
 ask for a prompt on the `h1` host and visit this chapter’s directory:
 
-    $ ./play.sh h1
+    $ ssh h1
 
-    # cd py3/chapter14
+    # cd /fopnp/py3/chapter14
 
 The scripts will all need the password of the `brandon` user, which is
 `abc123` and in the following examples will be piped in with the `echo`

py3/chapter16/README.md

@@ -65,7 +65,7 @@ Docker does not launch your initial shell on a host with everything set
 up as though you had logged in, this will only work if you `su` to the
 `root` user first:
 
-    $ ./play.sh h1
+    $ ssh h1
 
     # su root
 

py3/chapter17/README.md

@@ -102,7 +102,7 @@ directory:
 
     $ ./play h1
 
-    # cd py3/chapter17
+    # cd /fopnp/py3/chapter17
 
 The username `brandon` and the password `abc123` should let you upload
 binary files to the user’s home directory: