Tidying
This commit is contained in:
Bob Mottram
parent
c71a6d6dc1
commit
0dd80dae27
|
|
@ -23,8 +23,7 @@ As part of the Freedombone installation the GPG key used to encrypt backups will
|
|||
|
||||
#+BEGIN_SRC bash
|
||||
ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
#+END_SRC
|
||||
|
||||
Select /Backup and Restore/ then /Backup GPG key to USB drive (master keydrive)/.
|
||||
|
|
@ -41,8 +40,7 @@ Log into the system and become the root user, then run the /backup/ command.
|
|||
|
||||
#+BEGIN_SRC bash
|
||||
ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
#+END_SRC
|
||||
|
||||
Select /Backup and Restore/ and then /Backup data to USB drive/.
|
||||
|
|
@ -55,8 +53,7 @@ Log into the system and become the root user:
|
|||
|
||||
#+BEGIN_SRC bash
|
||||
ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
#+END_SRC
|
||||
|
||||
If this is a new Freedombone installation then you will first need to restore your backup keys. That can be done by selecting /Backup and Restore/ then /Restore GPG key from USB keydrive/. When that's done remove the keydrive and plug in the backup drive.
|
||||
|
|
@ -71,8 +68,7 @@ Firstly you will need to have a user account on one or more of your friends serv
|
|||
|
||||
#+BEGIN_SRC bash
|
||||
ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
#+END_SRC
|
||||
|
||||
Select /Backup and Restore/ then /Configure remote backups/.
|
||||
|
|
@ -86,8 +82,7 @@ First log in and if you don't already have one then create a new friends list:
|
|||
|
||||
#+BEGIN_SRC bash
|
||||
ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
#+END_SRC
|
||||
|
||||
Select /Backup and Restore/ then /Restore GPG key from USB (master keydrive)/. Select the username then plug in your keydrive and restore the key.
|
||||
|
|
@ -102,8 +97,7 @@ Log in as root:
|
|||
|
||||
#+BEGIN_SRC bash
|
||||
ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
#+END_SRC
|
||||
|
||||
Select /Backup and Restore/ then /Restore from remote backup/ and enter the domain name of the remote server that you wish to restore from.
|
||||
|
|
|
|||
|
|
@ -28,8 +28,6 @@
|
|||
| [[Why does my email keep getting rejected as spam by Gmail/etc?]] |
|
||||
#+END_CENTER
|
||||
|
||||
* Why not supply a disk image download?
|
||||
Shipping a Freedombone disk image ready to install on a flash disk would be easy, but disk images are relatively opaque. It would be quite easy to hide something nasty within a disk image and the user might never know. To guard against that possibility installing via the *freedombone* command is a lot more transparent, since it's really just a bash script. You can check the script code to see exactly what it's doing, and the packages are all downloaded from standard Debian repos (you can even choose which one you trust) or git repos. Doing it this way the system is fully auditable, whereas when shipping a disk image it's harder to be confident that no nefarious extras have been added.
|
||||
* I don't have a static IP address. Can I still install this system?
|
||||
Yes. The minimum requirements are to have some hardware that you can install Debian onto and also that you have administrator access to your internet router so that you can forward ports to the system which has Freedombone installed.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title></title>
|
||||
<!-- 2015-11-03 Tue 19:49 -->
|
||||
<!-- 2015-12-13 Sun 17:25 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="generator" content="Org-mode" />
|
||||
<meta name="author" content="Bob Mottram" />
|
||||
|
|
@ -207,8 +207,7 @@ As part of the Freedombone installation the GPG key used to encrypt backups will
|
|||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -243,8 +242,7 @@ Log into the system and become the root user, then run the <i>backup</i> command
|
|||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -271,8 +269,7 @@ Log into the system and become the root user:
|
|||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -303,8 +300,7 @@ Firstly you will need to have a user account on one or more of your friends serv
|
|||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -334,8 +330,7 @@ First log in and if you don't already have one then create a new friends list:
|
|||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -366,8 +361,7 @@ Log in as root:
|
|||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">ssh username@domainname -p 2222
|
||||
su
|
||||
control
|
||||
sudo control
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -3,15 +3,15 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2015-12-03 Thu 14:12 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title></title>
|
||||
<!-- 2015-12-13 Sun 17:26 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="generator" content="Org-mode" />
|
||||
<meta name="author" content="Bob Mottram" />
|
||||
<meta name="description" content="Turn the Beaglebone Black into a personal communications server"
|
||||
/>
|
||||
<meta name="keywords" content="freedombox, debian, beaglebone, hubzilla, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<style type="text/css">
|
||||
<!--/*--><![CDATA[/*><!--*/
|
||||
.title { text-align: center;
|
||||
|
|
@ -237,14 +237,6 @@ for the JavaScript code in this tag.
|
|||
</table>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgheadline16" class="outline-2">
|
||||
<h2 id="orgheadline16">Why not supply a disk image download?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline16">
|
||||
<p>
|
||||
Shipping a Freedombone disk image ready to install on a flash disk would be easy, but disk images are relatively opaque. It would be quite easy to hide something nasty within a disk image and the user might never know. To guard against that possibility installing via the <b>freedombone</b> command is a lot more transparent, since it's really just a bash script. You can check the script code to see exactly what it's doing, and the packages are all downloaded from standard Debian repos (you can even choose which one you trust) or git repos. Doing it this way the system is fully auditable, whereas when shipping a disk image it's harder to be confident that no nefarious extras have been added.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline1" class="outline-2">
|
||||
<h2 id="orgheadline1">I don't have a static IP address. Can I still install this system?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline1">
|
||||
|
|
|
|||
Loading…
Reference in New Issue