doc(temp/README):Initialize README for temperature logging

[EVA-2020-02.git] / doc / setup / README.org

diff --git a/doc/setup/README.org b/doc/setup/README.org
index 1a2f9fa103e293cbc34969fea146530927f04d8b..d4a63276639834208eb8570c9ed7759c3b75fa84 100644 (file)
--- a/doc/setup/README.org
+++ b/doc/setup/README.org
@@ -5,7 +5,7 @@
 ** About
 This document created by [[http://baltakatei.com][Steven Baltakatei Sandoval]] on
 ~2020-10-07T18:39Z~ under a [[http://creativecommons.org/licenses/by-sa/4.0/][CC BY-SA 4.0]] license and last updated on
 ** About
 This document created by [[http://baltakatei.com][Steven Baltakatei Sandoval]] on
 ~2020-10-07T18:39Z~ under a [[http://creativecommons.org/licenses/by-sa/4.0/][CC BY-SA 4.0]] license and last updated on

-~2020-10-16T22:26Z~.
+~2020-10-17T21:22Z~.

 
 This document contains information regarding setup of the
 ninfacyzga-01 hardware common to all operation modes. This includes:
 
 This document contains information regarding setup of the
 ninfacyzga-01 hardware common to all operation modes. This includes:


@@ -175,10 +175,35 @@ In summary, remote SSH access may be enabled upon initial startup of a
 freshly installed image of Raspberry Pi OS by making sure an empty
 file named ~ssh~ is present on the ~boot~ partition.
 
 freshly installed image of Raspberry Pi OS by making sure an empty
 file named ~ssh~ is present on the ~boot~ partition.
 

+***** Login via SSH
+Assuming your router supports finding your Raspberry Pi via its
+default hostname of `raspberypi`, log into the pi via Wi-Fi using the
+following command:
+
+: $ ssh pi@raspberrypi
+
+Otherwise, you may have to identify the raspbery pi's IP address via
+your network router's administration console and login via a command
+resembling this:
+
+: $ ssh pi@192.168.x.x
+
+If you had previously set up a different raspberry pi that also used
+the same hostname ~raspberrypi~ or the same IP address (ex:
+~192.168.123.123~), you may have to inform your computer that this is a
+different device. You may do so using these commands:
+
+: $ ssh-keygen -f ~/.ssh/known_hosts -R "raspberrypi"
+: $ ssh-keygen -R 192.168.123.123
+

 ***** Add SSH public key
 If the use has an SSH public key, it may be added as a line in
 ~~/.ssh/authorized_keys~.
 
 ***** Add SSH public key
 If the use has an SSH public key, it may be added as a line in
 ~~/.ssh/authorized_keys~.
 

+Add the ~~/.ssh~ directory if it doesn't already exist.
+
+: $ mkdir ~/.ssh
+

 Follow [[https://superuser.com/a/925859/][these]] directions to set permissions.
 
 : $ chmod 700 ~/.ssh
 Follow [[https://superuser.com/a/925859/][these]] directions to set permissions.
 
 : $ chmod 700 ~/.ssh


@@ -225,6 +250,8 @@ Make sure to install the ~unattended-upgrades~ package to make sure
 the latest security patches for packages are installed. See [[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][this page]]
 for a description of how ~unattended-upgrades~ works.
 
 the latest security patches for packages are installed. See [[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][this page]]
 for a description of how ~unattended-upgrades~ works.
 

+: $ sudo apt install unattended-upgrades
+

 The configuration file is located at:
 ~/etc/apt/apt.conf.d/50unattended-upgrades~ ([[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][ref]]). Make sure that the
 following lines are present and not commented out.
 The configuration file is located at:
 ~/etc/apt/apt.conf.d/50unattended-upgrades~ ([[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][ref]]). Make sure that the
 following lines are present and not commented out.