Generated.

[homepage.git] / blog / Broken_hard_link_handling_with_sshfs.html

diff --git a/blog/Broken_hard_link_handling_with_sshfs.html b/blog/Broken_hard_link_handling_with_sshfs.html
index 384065a5690a2b84a2347ccdb6e784c716aec863..7862d24e9b1394b3435659f7c773c103c8300dc1 100644 (file)
--- a/blog/Broken_hard_link_handling_with_sshfs.html
+++ b/blog/Broken_hard_link_handling_with_sshfs.html
@@ -23,7 +23,7 @@
       <div class="title">Broken hard link handling with sshfs</div>
       <div class="date">30th August 2010</div>
       <div class="body"><p>Just got an email from Tobias Gruetzmacher as a followup on my
-<a href="http://people.skolelinux.org/pere/blog/Broken_umask_handling_with_sshfs.html">previous
+<a href="https://people.skolelinux.org/pere/blog/Broken_umask_handling_with_sshfs.html">previous
 post about sshfs</a>.  He reported another problem with sshfs.  It
 fail to handle hard links properly.  A simple way to spot this is to
 look at the . and .. entries in the directory tree.  These should have