Generated.

diff --git a/blog/Some_notes_on_fault_tolerant_storage_systems.html b/blog/Some_notes_on_fault_tolerant_storage_systems.html
index d36ac732d553634357711d6f960f91722b02e388..e3f12e2bc0ea20345b068e3757423b17b964199d 100644 (file)
--- a/blog/Some_notes_on_fault_tolerant_storage_systems.html
+++ b/blog/Some_notes_on_fault_tolerant_storage_systems.html
@@ -85,7 +85,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/archive/2017/11/11.rss b/blog/archive/2017/11/11.rss
index 42c73727fb17f666bc7b1120f557d6e2590cb228..ef197da51e08bddb9d99fe2555a41a626971ea5f 100644 (file)
--- a/blog/archive/2017/11/11.rss
+++ b/blog/archive/2017/11/11.rss
@@ -74,7 +74,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/archive/2017/11/index.html b/blog/archive/2017/11/index.html
index a388988270728ce5b2bb53127487d41a240ab62e..4a24d8a8295e19d6215edf179e6a1b8ae6db11d2 100644 (file)
--- a/blog/archive/2017/11/index.html
+++ b/blog/archive/2017/11/index.html
@@ -92,7 +92,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/draft/2013-helse.txt b/blog/draft/2013-helse.txt
index ddae0a8c6be01ecda125ca2dcc3e9a60b86a03b2..558010ed25dbea1adfa80db67267c6bc7ca2ac98 100644 (file)
--- a/blog/draft/2013-helse.txt
+++ b/blog/draft/2013-helse.txt
@@ -40,3 +40,5 @@ https://www.theguardian.com/technology/2016/jul/06/nhs-to-scrap-single-database-
 http://www.aftenposten.no/norge/Vil-lagre-blodprover-fra-nyfodte-for-evig-tid-619404b.html
 
 https://www.aftenposten.no/meninger/debatt/i/7eOvV/Skal-det-lages-en-biobank-med-DNA-fra-nesten-alle-nordmenn--Kristin-Halvorsen-og-Ole-Johan-Borge
+
+https://www.dagbladet.no/kultur/lar-verden-snoke-i-norske-pasientjournaler/68866104

diff --git a/blog/images/2017-11-18-verk-i-det-fri-filmer.png b/blog/images/2017-11-18-verk-i-det-fri-filmer.png
new file mode 100644 (file)
index 0000000..2cf063b
Binary files /dev/null and b/blog/images/2017-11-18-verk-i-det-fri-filmer.png differ

diff --git a/blog/index.html b/blog/index.html
index fd8545b70bb8fefc0db5d0d3aa9bad29baf2fa0c..5ee011c39b835942bc396e6d5a0437ae00cc8688 100644 (file)
--- a/blog/index.html
+++ b/blog/index.html
@@ -85,7 +85,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/index.rss b/blog/index.rss
index ec8decc975a01108d6927019d09b63de5d20e992..99315b792e0a23ec41bc7563bbd98ca1f63c1140 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -74,7 +74,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/sitemap.xml b/blog/sitemap.xml
index dfeb150a0d6e55c52e87a8835605ca4ee9130b39..0d1c5cccc3b71d6ea1bf436ce60110a57dc58ea7 100644 (file)
--- a/blog/sitemap.xml
+++ b/blog/sitemap.xml
@@ -1685,6 +1685,11 @@
   <priority>0.50</priority>
   <changefreq>weekly</changefreq>
  </url>
+ <url>
+  <loc>http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html</loc>
+  <priority>0.50</priority>
+  <changefreq>weekly</changefreq>
+ </url>
  <url>
   <loc>http://people.skolelinux.org/pere/blog/Lenker_for_2012_11_28.html</loc>
   <priority>0.50</priority>

diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index a6a5a45601597bdd6dafffc686d369833e69acd7..c88925f4187fea5fc5410b393114941e51318d9b 100644 (file)
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -74,7 +74,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index d03c913a90c41efc37bfdd01a811cb46075c79a7..51e0657fb0f83cea606170b8faa6976d64802b35 100644 (file)
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -91,7 +91,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/tags/raid/index.html b/blog/tags/raid/index.html
index f3c6c5b2649f970b82a529c6bc69a4c29dc9146b..69e6985656798478b6353a9395639dbf7e38a08e 100644 (file)
--- a/blog/tags/raid/index.html
+++ b/blog/tags/raid/index.html
@@ -91,7 +91,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/tags/raid/raid.rss b/blog/tags/raid/raid.rss
index 74aa6fcac2c9fd87eec37eaa61723030114eff18..a365db0e47045a8fd7ed91100329ccd5298fa510 100644 (file)
--- a/blog/tags/raid/raid.rss
+++ b/blog/tags/raid/raid.rss
@@ -74,7 +74,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/tags/sysadmin/index.html b/blog/tags/sysadmin/index.html
index fb0a3d80d8ca0b3e1475e76382492e3fb996c4c6..2bb99d181b577b7f81dc236462dbf75d6f432d3a 100644 (file)
--- a/blog/tags/sysadmin/index.html
+++ b/blog/tags/sysadmin/index.html
@@ -91,7 +91,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>
 

diff --git a/blog/tags/sysadmin/sysadmin.rss b/blog/tags/sysadmin/sysadmin.rss
index 1508371d7cb26ad707aa293ce918f4556e6b8666..898ebd230e64d88fb84b98635e2feafa4d1ea531 100644 (file)
--- a/blog/tags/sysadmin/sysadmin.rss
+++ b/blog/tags/sysadmin/sysadmin.rss
@@ -74,7 +74,7 @@ are few options on Linux addressing all the identified issues.  Both
 ZFS and Btrfs are doing a fairly good job, but have legal and
 practical issues on their own.  I wonder how cluster file systems like
 Ceph do in this regard.  After all, there is an old saying, you know
-you have a distributed system when the crash of a compyter you have
+you have a distributed system when the crash of a computer you have
 never heard of stops you from getting any work done.  The same holds
 true if fault tolerance do not work.</p>