From: Petter Reinholdtsen Date: Sat, 18 Nov 2017 20:13:25 +0000 (+0100) Subject: Generated. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/ea70595b420dc8bda793ba9a383df1085a9e7c8e?hp=834625244e97305bc552eaeb5fed85aac172a8fe Generated. --- diff --git a/blog/Some_notes_on_fault_tolerant_storage_systems.html b/blog/Some_notes_on_fault_tolerant_storage_systems.html index d36ac732d5..e3f12e2bc0 100644 --- 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.

diff --git a/blog/archive/2017/11/11.rss b/blog/archive/2017/11/11.rss index 42c73727fb..ef197da51e 100644 --- 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 a388988270..4a24d8a829 100644 --- 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.

diff --git a/blog/draft/2013-helse.txt b/blog/draft/2013-helse.txt index ddae0a8c6b..558010ed25 100644 --- 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 index 0000000000..2cf063bc41 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 fd8545b70b..5ee011c39b 100644 --- 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.

diff --git a/blog/index.rss b/blog/index.rss index ec8decc975..99315b792e 100644 --- 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 dfeb150a0d..0d1c5cccc3 100644 --- a/blog/sitemap.xml +++ b/blog/sitemap.xml @@ -1685,6 +1685,11 @@ 0.50 weekly + + http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html + 0.50 + weekly + http://people.skolelinux.org/pere/blog/Lenker_for_2012_11_28.html 0.50 diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index a6a5a45601..c88925f418 100644 --- 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 d03c913a90..51e0657fb0 100644 --- 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.

diff --git a/blog/tags/raid/index.html b/blog/tags/raid/index.html index f3c6c5b264..69e6985656 100644 --- 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.

diff --git a/blog/tags/raid/raid.rss b/blog/tags/raid/raid.rss index 74aa6fcac2..a365db0e47 100644 --- 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 fb0a3d80d8..2bb99d181b 100644 --- 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.

diff --git a/blog/tags/sysadmin/sysadmin.rss b/blog/tags/sysadmin/sysadmin.rss index 1508371d7c..898ebd230e 100644 --- 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>