Federico Bonelli 2 years ago
parent
commit
fbaabe6bb6
3 changed files with 101 additions and 8 deletions
  1. 4 2
      guide.md
  2. 89 0
      howtoburnSDcards.md
  3. 8 6
      readme.md

+ 4 - 2
guide.md

@@ -31,9 +31,11 @@
31 31
     - check wich partitions of the SD are munted and umount them
32 32
     - `sudo dd if=~/dowseimagefile.dmg of=/dev/sdb`
33 33
 ### clone on MAC
34
-- `diskutil list`
34
+- `diskutil list` and unmount the right device (the card you write upon)
35 35
 - `diskutil unmountDisk </dev/disk3>`
36
-- `sudo dd if=~/<dowseIMGname.img> of=</dev/disk3>`
36
+- from the folder with the images
37
+	- `xzcat /path/to/devuan_ascii_dowse_raspi2.img.xz | sudo dd of=</dev/disk3>` bs=4M`
38
+
37 39
 
38 40
 
39 41
 ## Deploy

+ 89 - 0
howtoburnSDcards.md

@@ -0,0 +1,89 @@
1
+Hey there.
2
+
3
+The image can be found here: https://pub.parazyd.cf/tmp/dowse-img/
4
+
5
+There's two files: .tar.gz and .img.xz. I will explain them below.
6
+If it's usable, try to include it in the Dowse documentation.
7
+
8
+.tar.gz)
9
+   This is a tarball of the root filesystem (watch out, tarbomb!) that
10
+   can be extracted on a previously partitioned SD card. Basic steps to
11
+   do this are:
12
+
13
+   $ cfdisk /dev/mmcblk0
14
+       * make a partition of 128M that will act as /boot
15
+       * make a partition of remaining free space that will act as /
16
+   $ mkfs.vfat -F32 /dev/mmcblk0p1
17
+   $ mkfs.ext4 /dev/mmcblk0p2
18
+   $ mkdir mnt
19
+   $ mount /dev/mmcblk0p2 mnt
20
+   $ mkdir mnt/boot
21
+   $ mount /dev/mmcblk0p1 mnt/boot
22
+   $ cd mnt
23
+   $ tar xvf /path/to/devuan_ascii_dowse_raspi2.tar.gz
24
+   $ cd ..
25
+   $ umount -R mnt && sync
26
+
27
+   This will result in a Dowse SD card which has all the free space
28
+   usable.
29
+
30
+.img.xz)
31
+   This is a premade .img that can be dd-d to a SD card. Basic steps to
32
+   do this are:
33
+
34
+   $ xzcat /path/to/devuan_ascii_dowse_raspi2.img.xz | sudo dd of=/dev/mmcblk0 bs=4M
35
+   $ sync
36
+
37
+   To enlarge the second partition to the whole sd card:
38
+
39
+   $ cfdisk /dev/mmcblk0
40
+       * delete the second (bigger) partition
41
+       * create a new partition using all the remaining free space
42
+   $ e2fsck -f /dev/mmcblk0p2
43
+   $ resize2fs /dev/mmcblk0p2
44
+   $ sync
45
+
46
+   This will also result in a Dowse SD card which has all the free
47
+   space usable.
48
+
49
+---
50
+
51
+The Router setup:
52
+
53
+Connect the WAN cable to the blue port on the TP-Link, and then plug it
54
+in and power it up. It will boot and get an IP on the WAN by requesting
55
+DHCP.
56
+
57
+The TP-Link will also start the wireless network called 'dowse', with
58
+the password 'dortmund'. The router serves no DHCP on its own. To
59
+connect to the router, you can either plug in a cable, or access it via
60
+WiFi. Its IP address is "10.0.1.1". You can set your ip using:
61
+
62
+   $ ifconfig eth0 10.0.1.2 (use eth0 or wlan0 depending on how you connected)
63
+
64
+Now you should be able to access the interface of the router using
65
+10.0.1.1 as the IP address in your browser (or SSH).
66
+
67
+Time to connect the Dowse box. Plug it in and wait a minute or two until
68
+it boots. The white box won't start Dowse automatically so you have to
69
+start it manually. If you're still connected to the TP-Link, you should
70
+be able to access the Dowse box at the "10.0.1.250" IP address, using
71
+either "root:toor" or "dowse:dowse" as the credentials. Then start dowse
72
+normally as we do.
73
+
74
+---
75
+
76
+That's all there is to it. I'll try to be on IRC during the time of the
77
+workshop. Tor will also be running on the box so I will be able to
78
+intervene.
79
+
80
+Let me know when the workshop is happening and if anything else's
81
+needed.
82
+
83
+Have a good one ;)
84
+
85
+
86
+-- 
87
+~ parazyd
88
+GnuPG: 03337671FDE75BB6A85EC91FB876CB44FA1B0274
89
+GnuPG: https://parazyd.cf/FA1B0274.asc

+ 8 - 6
readme.md

@@ -37,7 +37,7 @@ There are two users set up, root and dowse. The default password for root is too
37 37
 - find out its IP address. Your router might tell you if you log in to its web interface, or try an app like https://github.com/adafruit/Adafruit-Pi-Finder/releases/tag/3.0.0
38 38
 
39 39
 - Let's assume it's 10.0.1.10. Open a Terminal and type
40
-ping 10.0.1.10
40
+`ping 10.0.1.10`
41 41
 - or open http://dowse.it in your browser. You should see the captive portal. Enter yourself as the administrator.
42 42
 
43 43
 - another way to check that the captive portal works:
@@ -60,7 +60,7 @@ ssh into the dowse box (See 'Putty' further down if you are on Windows)
60 60
 
61 61
 then start:
62 62
 
63
-/usr/local/dowse/bin/dowse-to-osc osc.udp://ip-of-machine-to-send-to:port/path
63
+`/usr/local/dowse/bin/dowse-to-osc osc.udp://ip-of-machine-to-send-to:port/path`
64 64
 
65 65
 to make it start at every boot, put this line inside the file /etc/rc.local (edit as root)
66 66
 
@@ -81,7 +81,7 @@ after installing node red you can follow a great tutorial :
81 81
 ### Installation Linux
82 82
 - install node.js
83 83
 - in terminal
84
-sudo npm install -g --unsafe-perm node-red
84
+`sudo npm install -g --unsafe-perm node-red`
85 85
 
86 86
 ### Installation Mac
87 87
 - install via homebrew https://brew.sh/
@@ -96,7 +96,7 @@ go to node.js website and install node.js
96 96
 https://nodejs.org/en/
97 97
 
98 98
 open node terminal
99
-type: sudo npm install -g --unsafe-perm node-red
99
+type: `sudo npm install -g --unsafe-perm node-red`
100 100
 
101 101
 
102 102
 ## Gource
@@ -108,7 +108,7 @@ Gource allows to visualize the data using a colorful, dynamic and animated graph
108 108
 - After installing, there is a ssh console client called plink.exe. It might not be in your 'PATH'. To run it from windows commandline, you need to specify the whole path. E.g. "c:\Program Files\Putty\plink.exe …"
109 109
 - When piping the output to gource, Windows does not show the interactive prompot for the password. But you can specify the password via the commandline switch -pw
110 110
 
111
-<full_path_to_putty>\plink.exe -pw dowse -l dowse dowse.it /usr/local/dowse/bin/dowse-to-gource | <full_path_to_gource>\gource.exe --log-format custom -
111
+`<full_path_to_putty>\plink.exe -pw dowse -l dowse dowse.it /usr/local/dowse/bin/dowse-to-gource | <full_path_to_gource>\gource.exe --log-format custom -`
112 112
 
113 113
 Alternative:
114 114
 - Instead of cmd/powershell, use a shell that knows SSH and such tools like 'https://babun.github.io/'
@@ -118,7 +118,9 @@ Alternative:
118 118
 install via homebrew https://brew.sh/
119 119
 First install brew if it isn't already, then just do brew install gource
120 120
 Once installed, start gource on your own laptop with
121
-ssh -l dowse dowse.it /usr/local/dowse/bin/dowse-to-gource | gource --log-format custom -
121
+`ssh -l dowse dowse.it /usr/local/dowse/bin/dowse-to-gource | gource --log-format custom -`
122
+my favourite gource command:
123
+`ssh -l dowse dowse.it /usr/local/dowse/bin/dowse-to-gource | gource --log-format custom -e 0.5 --bloom-multiplier 2.0 --bloom-intensity 0.1 --background F7EFDB --font-size 18 --font-colour 000000 --logo ~/devel/dowse-workshops/logo_small.png -`
122 124
 
123 125
 password is dowse
124 126