blog/archive/2018/10/10.rss

   1 <?xml version="1.0" encoding="ISO-8859-1"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
   3         <channel>
   4                 <title>Petter Reinholdtsen - Entries from October 2018</title>
   5                 <description>Entries from October 2018</description>
   6                 <link>http://www.hungry.com/~pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>Measuring the speaker frequency response using the AUDMES free software GUI - nice free software</title>
  11                 <link>http://www.hungry.com/~pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html</link>
  12                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html</guid>
  13                 <pubDate>Mon, 22 Oct 2018 08:40:00 +0200</pubDate>
  14                 <description>&lt;p&gt;&lt;img src=&quot;https://people.skolelinux.org/pere/blog/images/2018-10-22-audmes-measure-speakers.png&quot; align=&quot;right&quot; width=&quot;40%&quot;/&gt;&lt;/p&gt;
  15
  16 &lt;p&gt;My current home stereo is a patchwork of various pieces I got on
  17 flee markeds over the years.  It is amazing what kind of equipment
  18 show up there.  I&#39;ve been wondering for a while if it was possible to
  19 measure how well this equipment is working together, and decided to
  20 see how far I could get using free software.  After trawling the web I
  21 came across an article from DIY Audio and Video on
  22 &lt;a href=&quot;https://www.diyaudioandvideo.com/Tutorial/SpeakerResponseTesting/&quot;&gt;Speaker
  23 Testing and Analysis&lt;/a&gt; describing how to test speakers, and it listing
  24 several software options, among them
  25 &lt;a href=&quot;https://sourceforge.net/projects/audmes/&quot;&gt;AUDio MEasurement
  26 System (AUDMES)&lt;/a&gt;.  It is the only free software system I could find
  27 focusing on measuring speakers and audio frequency response.  In the
  28 process I also found an interesting article from NOVO on
  29 &lt;a href=&quot;http://novo.press/understanding-speaker-specifications-and-frequency-response/&quot;&gt;Understanding
  30 Speaker Specifications and Frequency Response&lt;/a&gt; and an article from
  31 ecoustics on
  32 &lt;a href=&quot;https://www.ecoustics.com/articles/understanding-speaker-frequency-response/&quot;&gt;Understanding
  33 Speaker Frequency Response&lt;/a&gt;, with a lot of information on what to
  34 look for and how to interpret the graphs.  Armed with this knowledge,
  35 I set out to measure the state of my speakers.&lt;/p&gt;
  36
  37 &lt;p&gt;The first hurdle was that AUDMES hadn&#39;t seen a commit for 10 years
  38 and did not build with current compilers and libraries.  I got in
  39 touch with its author, who no longer was spending time on the program
  40 but gave me write access to the subversion repository on Sourceforge.
  41 The end result is that now the code build on Linux and is capable of
  42 saving and loading the collected frequency response data in CSV
  43 format.  The application is quite nice and flexible, and I was able to
  44 select the input and output audio interfaces independently.  This made
  45 it possible to use a USB mixer as the input source, while sending
  46 output via my laptop headphone connection.  I lacked the hardware and
  47 cabling to figure out a different way to get independent cabling to
  48 speakers and microphone.&lt;/p&gt;
  49
  50 &lt;p&gt;Using this setup I could see how a large range of high frequencies
  51 apparently were not making it out of my speakers.  The picture show
  52 the frequency response measurement of one of the speakers.  Note the
  53 frequency lines seem to be slightly misaligned, compared to the CSV
  54 output from the program.  I can not hear several of these are high
  55 frequencies, according to measurement from
  56 &lt;a href=&quot;http://freehearingtestsoftware.com&quot;&gt;Free Hearing Test
  57 Software&lt;/a&gt;, an freeware system to measure your hearing (still
  58 looking for a free software alternative), so I do not know if they are
  59 coming out out the speakers.  I thus do not quite know how to figure
  60 out if the missing frequencies is a problem with the microphone, the
  61 amplifier or the speakers, but I managed to rule out the audio card in my
  62 PC by measuring my Bose noise canceling headset using its own
  63 microphone.  This setup was able to see the high frequency tones, so
  64 the problem with my stereo had to be in the amplifier or speakers.&lt;/p&gt;
  65
  66 &lt;p&gt;Anyway, to try to role out one factor I ended up picking up a new
  67 set of speakers at a flee marked, and these work a lot better than the
  68 old speakers, so I guess the microphone and amplifier is OK.  If you
  69 need to measure your own speakers, check out AUDMES.  If more people
  70 get involved, perhaps the project could become good enough to
  71 &lt;a href=&quot;https://bugs.debian.org/910876&quot;&gt;include in Debian&lt;/a&gt;?  And if
  72 you know of some other free software to measure speakers and amplifier
  73 performance, please let me know.  I am aware of the freeware option
  74 &lt;a href=&quot;https://www.roomeqwizard.com/&quot;&gt;REW&lt;/a&gt;, but I want something
  75 that can be developed also when the vendor looses interest.&lt;/p&gt;
  76
  77 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
  78 activities, please send Bitcoin donations to my address
  79 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
  80 </description>
  81         </item>
  82
  83         <item>
  84                 <title>Web browser integration of VLC with Bittorrent support</title>
  85                 <link>http://www.hungry.com/~pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</link>
  86                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</guid>
  87                 <pubDate>Sun, 21 Oct 2018 09:50:00 +0200</pubDate>
  88                 <description>&lt;p&gt;Bittorrent is as far as I know, currently the most efficient way to
  89 distribute content on the Internet.  It is used all by all sorts of
  90 content providers, from national TV stations like
  91 &lt;a href=&quot;https://www.nrk.no/&quot;&gt;NRK&lt;/a&gt;, Linux distributors like
  92 &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; and
  93 &lt;a href=&quot;https://www.ubuntu.com/&quot;&gt;Ubuntu&lt;/a&gt;, and of course the
  94 &lt;a href=&quot;https://archive.org/&quot;&gt;Internet archive&lt;/A&gt;.
  95
  96 &lt;p&gt;Almost a month ago
  97 &lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;a new
  98 package adding Bittorrent support to VLC&lt;/a&gt; became available in
  99 Debian testing and unstable.  To test it, simply install it like
 100 this:&lt;/p&gt;
 101
 102 &lt;p&gt;&lt;pre&gt;
 103 apt install vlc-plugin-bittorrent
 104 &lt;/pre&gt;&lt;/p&gt;
 105
 106 &lt;p&gt;Since the plugin was made available for the first time in Debian,
 107 several improvements have been made to it.  In version 2.2-4, now
 108 available in both testing and unstable, a desktop file is provided to
 109 teach browsers to start VLC when the user click on torrent files or
 110 magnet links.  The last part is thanks to me finally understanding
 111 what the strange x-scheme-handler style MIME types in desktop files
 112 are used for.  By adding x-scheme-handler/magnet to the MimeType entry
 113 in the desktop file, at least the browsers Firefox and Chromium will
 114 suggest to start VLC when selecting a magnet URI on a web page.  The
 115 end result is that now, with the plugin installed in Buster and Sid,
 116 one can visit any
 117 &lt;a href=&quot;https://archive.org/details/CopyingIsNotTheft1080p&quot;&gt;Internet
 118 Archive page with movies&lt;/a&gt; using a web browser and click on the
 119 torrent link to start streaming the movie.&lt;/p&gt;
 120
 121 &lt;p&gt;Note, there is still some misfeatures in the plugin.  One is the
 122 fact that it will hang and
 123 &lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/13&quot;&gt;block VLC
 124 from exiting until the torrent streaming starts&lt;/a&gt;.  Another is the
 125 fact that it
 126 &lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/9&quot;&gt;will pick
 127 and play a random file in a multi file torrent&lt;/a&gt;.  This is not
 128 always the video file you want.  Combined with the first it can be a
 129 bit hard to get the video streaming going.  But when it work, it seem
 130 to do a good job.&lt;/p&gt;
 131
 132 &lt;p&gt;For the Debian packaging, I would love to find a good way to test
 133 if the plugin work with VLC using autopkgtest.  I tried, but do not
 134 know enough of the inner workings of VLC to get it working.  For now
 135 the autopkgtest script is only checking if the .so file was
 136 successfully loaded by VLC.  If you have any suggestions, please
 137 submit a patch to the Debian bug tracking system.&lt;/p&gt;
 138
 139 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 140 activities, please send Bitcoin donations to my address
 141 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 142 </description>
 143         </item>
 144
 145         <item>
 146                 <title>Release 0.2 of free software archive system Nikita announced</title>
 147                 <link>http://www.hungry.com/~pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</link>
 148                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</guid>
 149                 <pubDate>Thu, 18 Oct 2018 14:40:00 +0200</pubDate>
 150                 <description>&lt;p&gt;This morning, the new release of the
 151 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
 152 Noark 5 core project&lt;/a&gt; was
 153 &lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2018-October/000406.html&quot;&gt;announced
 154 on the project mailing list&lt;/a&gt;.  The free software solution is an
 155 implementation of the Norwegian archive standard Noark 5 used by
 156 government offices in Norway.  These were the changes in version 0.2
 157 since version 0.1.1 (from NEWS.md):
 158
 159 &lt;ul&gt;
 160   &lt;li&gt;Fix typos in REL names&lt;/li&gt;
 161   &lt;li&gt;Tidy up error message reporting&lt;/li&gt;
 162   &lt;li&gt;Fix issue where we used Integer.valueOf(), not Integer.getInteger()&lt;/li&gt;
 163   &lt;li&gt;Change some String handling to StringBuffer&lt;/li&gt;
 164   &lt;li&gt;Fix error reporting&lt;/li&gt;
 165   &lt;li&gt;Code tidy-up&lt;/li&gt;
 166   &lt;li&gt;Fix issue using static non-synchronized SimpleDateFormat to avoid
 167       race conditions&lt;/li&gt;
 168   &lt;li&gt;Fix problem where deserialisers were treating integers as strings&lt;/li&gt;
 169   &lt;li&gt;Update methods to make them null-safe&lt;/li&gt;
 170   &lt;li&gt;Fix many issues reported by coverity&lt;/li&gt;
 171   &lt;li&gt;Improve equals(), compareTo() and hash() in domain model&lt;/li&gt;
 172   &lt;li&gt;Improvements to the domain model for metadata classes&lt;/li&gt;
 173   &lt;li&gt;Fix CORS issues when downloading document&lt;/li&gt;
 174   &lt;li&gt;Implementation of case-handling with registryEntry and document upload&lt;/li&gt;
 175   &lt;li&gt;Better support in Javascript for OPTIONS&lt;/li&gt;
 176   &lt;li&gt;Adding concept description of mail integration&lt;/li&gt;
 177   &lt;li&gt;Improve setting of default values for GET on ny-journalpost&lt;/li&gt;
 178   &lt;li&gt;Better handling of required values during deserialisation &lt;/li&gt;
 179   &lt;li&gt;Changed tilknyttetDato (M620) from date to dateTime&lt;/li&gt;
 180   &lt;li&gt;Corrected some opprettetDato (M600) (de)serialisation errors.&lt;/li&gt;
 181   &lt;li&gt;Improve parse error reporting.&lt;/li&gt;
 182   &lt;li&gt;Started on OData search and filtering.&lt;/li&gt;
 183   &lt;li&gt;Added Contributor Covenant Code of Conduct to project.&lt;/li&gt;
 184   &lt;li&gt;Moved repository and project from Github to Gitlab.&lt;/li&gt;
 185   &lt;li&gt;Restructured repository, moved code into src/ and web/.&lt;/li&gt;
 186   &lt;li&gt;Updated code to use Spring Boot version 2.&lt;/li&gt;
 187   &lt;li&gt;Added support for OAuth2 authentication.&lt;/li&gt;
 188   &lt;li&gt;Fixed several bugs discovered by Coverity.&lt;/li&gt;
 189   &lt;li&gt;Corrected handling of date/datetime fields.&lt;/li&gt;
 190   &lt;li&gt;Improved error reporting when rejecting during deserializatoin.&lt;/li&gt;
 191   &lt;li&gt;Adjusted default values provided for ny-arkivdel, ny-mappe,
 192    ny-saksmappe, ny-journalpost and ny-dokumentbeskrivelse.&lt;/li&gt;
 193   &lt;li&gt;Several fixes for korrespondansepart*.&lt;/li&gt;
 194   &lt;li&gt;Updated web GUI:
 195      &lt;ul&gt;
 196        &lt;li&gt;Now handle both file upload and download.&lt;/li&gt;
 197        &lt;li&gt;Uses new OAuth2 authentication for login.&lt;/li&gt;
 198        &lt;li&gt;Forms now fetches default values from API using GET.&lt;/li&gt;
 199        &lt;li&gt;Added RFC 822 (email), TIFF and JPEG to list of possible file formats.&lt;/li&gt;
 200      &lt;/ul&gt;&lt;/li&gt;
 201 &lt;/ul&gt;
 202
 203 &lt;p&gt;The changes and improvements are extensive.  Running diffstat on
 204 the changes between git tab 0.1.1 and 0.2 show 1098 files changed,
 205 108666 insertions(+), 54066 deletions(-).&lt;/p&gt;
 206
 207 &lt;p&gt;If free and open standardized archiving API sound interesting to
 208 you, please contact us on IRC
 209 (&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&gt;#nikita on
 210 irc.freenode.net&lt;/a&gt;) or email
 211 (&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
 212 mailing list&lt;/a&gt;).&lt;/p&gt;
 213
 214 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 215 activities, please send Bitcoin donations to my address
 216 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 217 </description>
 218         </item>
 219
 220         <item>
 221                 <title>Fetching trusted timestamps using the rfc3161ng python module</title>
 222                 <link>http://www.hungry.com/~pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</link>
 223                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</guid>
 224                 <pubDate>Mon, 8 Oct 2018 12:30:00 +0200</pubDate>
 225                 <description>&lt;p&gt;I have  earlier covered the basics of trusted timestamping using the
 226 &#39;openssl ts&#39; client.  See blog post for
 227 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/Public_Trusted_Timestamping_services_for_everyone.html&quot;&gt;2014&lt;/a&gt;,
 228 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/syslog_trusted_timestamp___chain_of_trusted_timestamps_for_your_syslog.html&quot;&gt;2016&lt;/a&gt;
 229 and
 230 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html&quot;&gt;2017&lt;/a&gt;
 231 for those stories.  But some times I want to integrate the timestamping
 232 in other code, and recently I needed to integrate it into Python.
 233 After searching a bit, I found
 234 &lt;a href=&quot;https://dev.entrouvert.org/projects/python-rfc3161&quot;&gt;the
 235 rfc3161 library&lt;/a&gt; which seemed like a good fit, but I soon
 236 discovered it only worked for python version 2, and I needed something
 237 that work with python version 3.  Luckily I next came across
 238 &lt;a href=&quot;https://github.com/trbs/rfc3161ng/&quot;&gt;the rfc3161ng library&lt;/a&gt;,
 239 a fork of the original rfc3161 library.  Not only is it working with
 240 python 3, it have fixed a few of the bugs in the original library, and
 241 it has an active maintainer.  I decided to wrap it up and make it
 242 &lt;a href=&quot;https://tracker.debian.org/pkg/python-rfc3161ng&quot;&gt;available in
 243 Debian&lt;/a&gt;, and a few days ago it entered Debian unstable and testing.&lt;/p&gt;
 244
 245 &lt;p&gt;Using the library is fairly straight forward.  The only slightly
 246 problematic step is to fetch the required certificates to verify the
 247 timestamp.  For some services it is straight forward, while for others
 248 I have not yet figured out how to do it.  Here is a small standalone
 249 code example based on of the integration tests in the library code:&lt;/p&gt;
 250
 251 &lt;pre&gt;
 252 #!/usr/bin/python3
 253
 254 &quot;&quot;&quot;
 255
 256 Python 3 script demonstrating how to use the rfc3161ng module to
 257 get trusted timestamps.
 258
 259 The license of this code is the same as the license of the rfc3161ng
 260 library, ie MIT/BSD.
 261
 262 &quot;&quot;&quot;
 263
 264 import os
 265 import pyasn1.codec.der
 266 import rfc3161ng
 267 import subprocess
 268 import tempfile
 269 import urllib.request
 270
 271 def store(f, data):
 272     f.write(data)
 273     f.flush()
 274     f.seek(0)
 275
 276 def fetch(url, f=None):
 277     response = urllib.request.urlopen(url)
 278     data = response.read()
 279     if f:
 280         store(f, data)
 281     return data
 282
 283 def main():
 284     with tempfile.NamedTemporaryFile() as cert_f,\
 285          tempfile.NamedTemporaryFile() as ca_f,\
 286          tempfile.NamedTemporaryFile() as msg_f,\
 287          tempfile.NamedTemporaryFile() as tsr_f:
 288
 289         # First fetch certificates used by service
 290         certificate_data = fetch(&#39;https://freetsa.org/files/tsa.crt&#39;, cert_f)
 291         ca_data_data = fetch(&#39;https://freetsa.org/files/cacert.pem&#39;, ca_f)
 292
 293         # Then timestamp the message
 294         timestamper = \
 295             rfc3161ng.RemoteTimestamper(&#39;http://freetsa.org/tsr&#39;,
 296                                         certificate=certificate_data)
 297         data = b&quot;Python forever!\n&quot;
 298         tsr = timestamper(data=data, return_tsr=True)
 299
 300         # Finally, convert message and response to something &#39;openssl ts&#39; can verify
 301         store(msg_f, data)
 302         store(tsr_f, pyasn1.codec.der.encoder.encode(tsr))
 303         args = [&quot;openssl&quot;, &quot;ts&quot;, &quot;-verify&quot;,
 304                 &quot;-data&quot;, msg_f.name,
 305                 &quot;-in&quot;, tsr_f.name,
 306                 &quot;-CAfile&quot;, ca_f.name,
 307                 &quot;-untrusted&quot;, cert_f.name]
 308         subprocess.check_call(args)
 309
 310 if &#39;__main__&#39; == __name__:
 311    main()
 312 &lt;/pre&gt;
 313
 314 &lt;p&gt;The code fetches the required certificates, store them as temporary
 315 files, timestamp a simple message, store the message and timestamp to
 316 disk and ask &#39;openssl ts&#39; to verify the timestamp.  A timestamp is
 317 around 1.5 kiB in size, and should be fairly easy to store for future
 318 use.&lt;/p&gt;
 319
 320 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 321 activities, please send Bitcoin donations to my address
 322 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 323 </description>
 324         </item>
 325
 326         <item>
 327                 <title>Automatic Google Drive sync using grive in Debian</title>
 328                 <link>http://www.hungry.com/~pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
 329                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
 330                 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
 331                 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian.  To try to
 332 rescue the remains, I helped set up automatic sync with Google Drive.
 333 I did not find any sensible Debian package handling this
 334 automatically, so I rebuild the grive2 source from
 335 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
 336 task and added a autostart desktop entry and a small shell script to
 337 run in the background while the user is logged in to do the sync.
 338 Here is a sketch of the setup for future reference.&lt;/p&gt;
 339
 340 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
 341 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user.  Next, I
 342 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
 343 to start the sync when the user log in:&lt;/p&gt;
 344
 345 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 346 [Desktop Entry]
 347 Name=Google drive autosync
 348 Type=Application
 349 Exec=/home/user/bin/grive-sync
 350 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 351
 352 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
 353 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
 354
 355 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 356 #!/bin/sh
 357 set -e
 358 cd ~/
 359 cleanup() {
 360     if [ &quot;$syncpid&quot; ] ; then
 361         kill $syncpid
 362     fi
 363 }
 364 trap cleanup EXIT INT QUIT
 365 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
 366 syncpdi=$!
 367 while true; do
 368     if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
 369         echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
 370         exit 1
 371     fi
 372     if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
 373         /usr/lib/grive/grive-sync.sh sync googledrive
 374     fi
 375     sleep 300
 376 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
 377 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 378
 379 &lt;p&gt;Feel free to use the setup if you want.  It can be assumed to be
 380 GNU GPL v2 licensed (or any later version, at your leisure), but I
 381 doubt this code is possible to claim copyright on.&lt;/p&gt;
 382
 383 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 384 activities, please send Bitcoin donations to my address
 385 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 386 </description>
 387         </item>
 388
 389         </channel>
 390 </rss>