From: Petter Reinholdtsen Date: Wed, 9 Apr 2014 09:34:53 +0000 (+0000) Subject: Generated. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/2b90197f037d6c4372fd9df9b61c8f8e74630cea?ds=sidebyside Generated. --- diff --git a/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html b/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html index 12d588eeee..4a9d5fafff 100644 --- a/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html +++ b/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html @@ -26,8 +26,8 @@ solution for use at home. My requirements are simple, it must be cheap and locally encrypted (in other words, I keep the encryption keys, the storage provider do not have access to my private files). -One idea me and my friends have had many years ago, before the cloud -storage providers showed up, have been to use Google mail as storage, +One idea me and my friends had many years ago, before the cloud +storage providers showed up, was to use Google mail as storage, writing a Linux block device storing blocks as emails in the mail service provided by Google, and thus get heaps of free space. On top of this one can add encryption, RAID and volume management to have @@ -56,7 +56,7 @@ package is included already. So to get started, run apt-get install s3ql. Next, pick a storage provider. I ended up picking Greenqloud, after reading their nice recipe on how -to use s3ql with their Amazon S3 service, because I trust the laws +to use S3QL with their Amazon S3 service, because I trust the laws in Iceland more than those in USA when it come to keeping my personal data safe and private, and thus would rather spend money on a company in Iceland. Another nice recipe is available from the article @@ -226,7 +226,7 @@ Backend reports that fs is still mounted elsewhere, aborting.

The file content is uploaded when the cache is full, while the metadata is uploaded once every 24 hour by default. To ensure the file system content is flushed to the cloud, one can either umount the -file system, or ask s3ql to flush the cache and metadata using +file system, or ask S3QL to flush the cache and metadata using s3qlctrl: 

@@ -281,7 +281,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.

 
diff --git a/blog/archive/2014/04/04.rss b/blog/archive/2014/04/04.rss
index 2bace76284..7bc91647dc 100644
--- a/blog/archive/2014/04/04.rss
+++ b/blog/archive/2014/04/04.rss
@@ -15,8 +15,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -45,7 +45,7 @@ package is included already.  So to get started, run <tt>apt-get
 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
-to use s3ql with their Amazon S3 service</a>, because I trust the laws
+to use S3QL with their Amazon S3 service</a>, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -215,7 +215,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 <p>The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 <p><blockquote><pre>
@@ -270,7 +270,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics</a>, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.</p>
 
diff --git a/blog/archive/2014/04/index.html b/blog/archive/2014/04/index.html
index d8ffbdc142..77cc69bf0f 100644
--- a/blog/archive/2014/04/index.html
+++ b/blog/archive/2014/04/index.html
@@ -33,8 +33,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -63,7 +63,7 @@ package is included already.  So to get started, run apt-get
 install s3ql.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 how
-to use s3ql with their Amazon S3 service, because I trust the laws
+to use S3QL with their Amazon S3 service, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -233,7 +233,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 
The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 
@@ -288,7 +288,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.

 
diff --git a/blog/index.html b/blog/index.html
index 6d449f60ff..6ef5883eb7 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -26,8 +26,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -56,7 +56,7 @@ package is included already.  So to get started, run apt-get
 install s3ql.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 how
-to use s3ql with their Amazon S3 service, because I trust the laws
+to use S3QL with their Amazon S3 service, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -226,7 +226,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 
The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 
@@ -281,7 +281,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.

 
diff --git a/blog/index.rss b/blog/index.rss
index cf27c633b6..37dfb4e431 100644
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -15,8 +15,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -45,7 +45,7 @@ package is included already.  So to get started, run <tt>apt-get
 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
-to use s3ql with their Amazon S3 service</a>, because I trust the laws
+to use S3QL with their Amazon S3 service</a>, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -215,7 +215,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 <p>The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 <p><blockquote><pre>
@@ -270,7 +270,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics</a>, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.</p>
 
diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss
index a7191e0be8..973546461a 100644
--- a/blog/tags/debian/debian.rss
+++ b/blog/tags/debian/debian.rss
@@ -15,8 +15,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -45,7 +45,7 @@ package is included already.  So to get started, run <tt>apt-get
 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
-to use s3ql with their Amazon S3 service</a>, because I trust the laws
+to use S3QL with their Amazon S3 service</a>, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -215,7 +215,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 <p>The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 <p><blockquote><pre>
@@ -270,7 +270,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics</a>, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.</p>
 
diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html
index d633a3a436..0dab6fefb1 100644
--- a/blog/tags/debian/index.html
+++ b/blog/tags/debian/index.html
@@ -32,8 +32,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -62,7 +62,7 @@ package is included already.  So to get started, run apt-get
 install s3ql.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 how
-to use s3ql with their Amazon S3 service, because I trust the laws
+to use S3QL with their Amazon S3 service, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -232,7 +232,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 
The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 
@@ -287,7 +287,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.

 
diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index 8d56f12404..38d92bc66d 100644
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -15,8 +15,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -45,7 +45,7 @@ package is included already.  So to get started, run <tt>apt-get
 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
-to use s3ql with their Amazon S3 service</a>, because I trust the laws
+to use S3QL with their Amazon S3 service</a>, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -215,7 +215,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 <p>The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 <p><blockquote><pre>
@@ -270,7 +270,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics</a>, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.</p>
 
diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index fed66e2d06..86c9aa7de7 100644
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -32,8 +32,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -62,7 +62,7 @@ package is included already.  So to get started, run apt-get
 install s3ql.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 how
-to use s3ql with their Amazon S3 service, because I trust the laws
+to use S3QL with their Amazon S3 service, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -232,7 +232,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 
The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 
@@ -287,7 +287,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.

 
diff --git a/blog/tags/personvern/index.html b/blog/tags/personvern/index.html
index 847ca973a8..996af832e7 100644
--- a/blog/tags/personvern/index.html
+++ b/blog/tags/personvern/index.html
@@ -32,8 +32,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -62,7 +62,7 @@ package is included already.  So to get started, run apt-get
 install s3ql.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 how
-to use s3ql with their Amazon S3 service, because I trust the laws
+to use S3QL with their Amazon S3 service, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -232,7 +232,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 
The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 
@@ -287,7 +287,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.

 
diff --git a/blog/tags/personvern/personvern.rss b/blog/tags/personvern/personvern.rss
index 7829150a4c..d05036382c 100644
--- a/blog/tags/personvern/personvern.rss
+++ b/blog/tags/personvern/personvern.rss
@@ -15,8 +15,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -45,7 +45,7 @@ package is included already.  So to get started, run <tt>apt-get
 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
-to use s3ql with their Amazon S3 service</a>, because I trust the laws
+to use S3QL with their Amazon S3 service</a>, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -215,7 +215,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 <p>The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 <p><blockquote><pre>
@@ -270,7 +270,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics</a>, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.</p>
 
diff --git a/blog/tags/sikkerhet/index.html b/blog/tags/sikkerhet/index.html
index 115f3f6e94..cdad7b07be 100644
--- a/blog/tags/sikkerhet/index.html
+++ b/blog/tags/sikkerhet/index.html
@@ -32,8 +32,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -62,7 +62,7 @@ package is included already.  So to get started, run apt-get
 install s3ql.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 how
-to use s3ql with their Amazon S3 service, because I trust the laws
+to use S3QL with their Amazon S3 service, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -232,7 +232,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 
The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 
@@ -287,7 +287,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.

 
diff --git a/blog/tags/sikkerhet/sikkerhet.rss b/blog/tags/sikkerhet/sikkerhet.rss
index cf34758a8e..98e3442752 100644
--- a/blog/tags/sikkerhet/sikkerhet.rss
+++ b/blog/tags/sikkerhet/sikkerhet.rss
@@ -15,8 +15,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -45,7 +45,7 @@ package is included already.  So to get started, run <tt>apt-get
 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
-to use s3ql with their Amazon S3 service</a>, because I trust the laws
+to use S3QL with their Amazon S3 service</a>, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -215,7 +215,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 <p>The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 <p><blockquote><pre>
@@ -270,7 +270,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics</a>, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.</p>