Move releases to macfuse GitHub organization

_layouts/base.html

@@ -18,7 +18,7 @@ <h1>
                 </h1>
             </a>
             <ul id="menu">
-                <li><a href="https://github.com/osxfuse">Project on GitHub</a></li><li><a href="https://github.com/osxfuse/osxfuse/releases">Downloads</a></li><li><a href="https://github.com/osxfuse/osxfuse/wiki">Wiki</a></li><li><a href="https://groups.google.com/forum/#!forum/osxfuse-group">Google Group</a></li><li><a href="https://github.com/osxfuse/osxfuse/issues">Issue Tracker</a></li>
+                <li><a href="https://github.com/osxfuse">Project on GitHub</a></li><li><a href="https://github.com/macfuse/macfuse/releases">Downloads</a></li><li><a href="https://github.com/macfuse/macfuse/wiki">Wiki</a></li><li><a href="https://groups.google.com/forum/#!forum/osxfuse-group">Google Group</a></li><li><a href="https://github.com/macfuse/macfuse/issues">Issue Tracker</a></li>
             </ul>
         </div>
         <div id="content">
@@ -35,7 +35,7 @@ <h2>Sponsors of the macFUSE project</h2>
         </div>
         <div id="legal" class="footer">
             <div>
-                <a href="https://raw.githubusercontent.com/osxfuse/osxfuse/releases/LICENSE.txt">macFUSE License</a>
+                <a href="https://raw.githubusercontent.com/macfuse/macfuse/release/macfuse/LICENSE.txt">macFUSE License</a>
                 <br>
                 &copy; 2011-2024 Benjamin Fleischer
                 <br>

_layouts/home.html

@@ -65,10 +65,10 @@
         addDownloadCounter("osxfuse-developer", response);
     }
 </script>
-<script type="text/javascript" src="https://api.github.com/repos/osxfuse/osxfuse/releases/assets/{{ page.osxfuse.gh_asset_id }}?callback=osxfuseDownloadCounter"></script>
+<script type="text/javascript" src="https://api.github.com/repos/macfuse/macfuse/releases/assets/{{ page.osxfuse.gh_asset_id }}?callback=osxfuseDownloadCounter"></script>
 <script type="text/javascript" src="https://api.github.com/repos/osxfuse/sshfs/releases/assets/{{ page.sshfs.gh_asset_id }}?callback=sshfsDownloadCounter"></script>
 {% if page.osxfuse-developer %}
-<script type="text/javascript" src="https://api.github.com/repos/osxfuse/osxfuse/releases/assets/{{ page.osxfuse-developer.gh_asset_id }}?callback=osxfuseDeveloperDownloadCounter"></script>
+<script type="text/javascript" src="https://api.github.com/repos/macfuse/macfuse/releases/assets/{{ page.osxfuse-developer.gh_asset_id }}?callback=osxfuseDeveloperDownloadCounter"></script>
 {% endif %}
 <div>
     {{ content }}

_posts/2011-07-25-OSXFUSE-2.3.0.html

@@ -8,7 +8,7 @@
         - macOS 10.6 or 10.7
         - Intel
         - "SHA1: 17794d5a961b3676fe3ae8f5b900d384a031f808"
-    url: "https://github.com/osxfuse/osxfuse.github.com/raw/0408ac797f07ca1ae1908e02a7cd215d4480c644/releases/OSXFUSE-2.3.dmg"
+    url: "https://github.com/macfuse/macfuse.github.com/raw/0408ac797f07ca1ae1908e02a7cd215d4480c644/releases/OSXFUSE-2.3.dmg"
 ---
 <p class="note">
     This is the first public release of OSXFUSE, a successor to MacFUSE. OSXFUSE 2.3.0 is a beta release and may contain bugs.

_posts/2011-08-01-OSXFUSE-2.3.1.html

@@ -8,7 +8,7 @@
         - macOS 10.6 to 10.7
         - Intel
         - "SHA1: 0076e8cefb5ec71cd0134b17d4b38a7021e4b749"
-    url: "https://github.com/osxfuse/osxfuse.github.com/raw/831c5c557993bfc15db59d0fc3bc5d07417214a7/releases/OSXFUSE-2.3.dmg"
+    url: "https://github.com/macfuse/macfuse.github.com/raw/831c5c557993bfc15db59d0fc3bc5d07417214a7/releases/OSXFUSE-2.3.dmg"
 ---
 <h3>New Features</h3>
 <ul>
@@ -17,7 +17,7 @@ <h3>New Features</h3>
 <h3>Fixes</h3>
 <ul>
     <li>Fixed a bug in build script target <code>reload</code>.</li>
-    <li>Fixed a bug in <code>OSXFUSE.framework</code> that may have resulted in the selector <code>removeExtendedAttribute:ofItemAtPath:error:</code> never being called. Tracked as issue #2: <a href="https://github.com/osxfuse/osxfuse/issues/2">"removeExtendedAttribute never called"</a>. Reported and fixed by Dan Cooper.</li>
+    <li>Fixed a bug in <code>OSXFUSE.framework</code> that may have resulted in the selector <code>removeExtendedAttribute:ofItemAtPath:error:</code> never being called. Tracked as issue #2: <a href="https://github.com/macfuse/macfuse/issues/2">"removeExtendedAttribute never called"</a>. Reported and fixed by Dan Cooper.</li>
     <li>Fixed bundle identifier of the OSXFUSE kernel extension.</li>
 </ul>
 <h3>Known Issues</h3>

_posts/2011-08-28-OSXFUSE-2.3.2.html

@@ -8,12 +8,12 @@
         - macOS 10.6 to 10.7
         - Intel
         - "SHA1: f85936ab47e076e7bb49317c9edac6bd5ee3ea30"
-    url: "https://github.com/osxfuse/osxfuse.github.com/raw/1c68f1e9c7b78433d9c84686d5a109b3537ea724/releases/OSXFUSE-2.3.dmg"
+    url: "https://github.com/macfuse/macfuse.github.com/raw/1c68f1e9c7b78433d9c84686d5a109b3537ea724/releases/OSXFUSE-2.3.dmg"
 ---
 <h3>Fixes</h3>
 <ul>
-    <li>Fixed a permission issue regarding Finder in macOS 10.7. Creating files on a OSXFUSE volume, that had not been mounted with option <code>allow_other</code>, failed due to a change in Finder. Tracked as issue #5: <a href="https://github.com/osxfuse/osxfuse/issues/5">"Finder permission problem"</a>. Fix suggested by Peter Stegemann</li>
-    <li>Fixed a bug in the OSXFUSE kernel extension, that could render a file system unresponsive and therefore being ejected after a timeout. This bug affected solely Macs running a 64 bit kernel and was triggered through many simultaneous file system operations. Tracked as issue #7: <a href="https://github.com/osxfuse/osxfuse/issues/7">"Deadlock in filesystem"</a>. Fix based on Anatol Pomozov's findings.</li>
+    <li>Fixed a permission issue regarding Finder in macOS 10.7. Creating files on a OSXFUSE volume, that had not been mounted with option <code>allow_other</code>, failed due to a change in Finder. Tracked as issue #5: <a href="https://github.com/macfuse/macfuse/issues/5">"Finder permission problem"</a>. Fix suggested by Peter Stegemann</li>
+    <li>Fixed a bug in the OSXFUSE kernel extension, that could render a file system unresponsive and therefore being ejected after a timeout. This bug affected solely Macs running a 64 bit kernel and was triggered through many simultaneous file system operations. Tracked as issue #7: <a href="https://github.com/macfuse/macfuse/issues/7">"Deadlock in filesystem"</a>. Fix based on Anatol Pomozov's findings.</li>
 </ul>
 <h3>Changes</h3>
 <ul>

_posts/2011-09-04-OSXFUSE-2.3.3.html

@@ -8,7 +8,7 @@
         - macOS 10.5 to 10.7
         - Intel or PowerPC
         - "SHA1: 2e6fc52ac28d66b8f3ce381f6a97b4114ebf1284"
-    url: "https://github.com/osxfuse/osxfuse.github.com/raw/83da89ad3e4b1d3f3b328636879490eeab20143a/releases/OSXFUSE-2.3.dmg"
+    url: "https://github.com/macfuse/macfuse.github.com/raw/83da89ad3e4b1d3f3b328636879490eeab20143a/releases/OSXFUSE-2.3.dmg"
 ---
 <h3>New Features</h3>
 <ul>

_posts/2011-09-08-OSXFUSE-2.3.4.html

@@ -12,8 +12,8 @@
 ---
 <h3>Fixes</h3>
 <ul>
-    <li>Fixed a bug that triggered a system-wide deadlock, if multiple MacFUSE volumes are mounted. This issue had been introduced in OSXFUSE 2.3.1 and affected solely MacFUSE file systems based on one of the user space C libraries, <code>libfuse</code> or <code>libfuse_ino64</code>. Objective-C file systems based on <code>MacFUSE.framework</code> did not trigger the deadlock. Tracked as issue #10: <a href="https://github.com/osxfuse/osxfuse/issues/10">"Deadlock when multiple MacFUSE file systems are mounted"</a>.</li>
-    <li>Fixed an issue that prevented the kernel extension from loading on macOS 10.5 (PowerPC). This was caused by a bug in <code>llvm-gcc-4.2</code>. Tracked as issue #9: <a href="https://github.com/osxfuse/osxfuse/issues/9">"osxfusefs.kext does not load on OS X 10.5/ppc"</a>.</li>
+    <li>Fixed a bug that triggered a system-wide deadlock, if multiple MacFUSE volumes are mounted. This issue had been introduced in OSXFUSE 2.3.1 and affected solely MacFUSE file systems based on one of the user space C libraries, <code>libfuse</code> or <code>libfuse_ino64</code>. Objective-C file systems based on <code>MacFUSE.framework</code> did not trigger the deadlock. Tracked as issue #10: <a href="https://github.com/macfuse/macfuse/issues/10">"Deadlock when multiple MacFUSE file systems are mounted"</a>.</li>
+    <li>Fixed an issue that prevented the kernel extension from loading on macOS 10.5 (PowerPC). This was caused by a bug in <code>llvm-gcc-4.2</code>. Tracked as issue #9: <a href="https://github.com/macfuse/macfuse/issues/9">"osxfusefs.kext does not load on OS X 10.5/ppc"</a>.</li>
     <li>Fixed an issue that caused 64 bit PowerPC file systems to crash. This was caused by <code>llvm-gcc-4.2</code>.</li>
 </ul>
 <h3>Changes</h3>

_posts/2012-02-19-OSXFUSE-2.3.9.html

@@ -12,14 +12,14 @@
 ---
 <h3>New Features</h3>
 <ul>
-    <li>Added support for building PowerPC file systems on macOS 10.6 and 10.7, if an appropriate version of Xcode is installed (e.g. Xcode 3.2.6). Tracked as issue #12: <a href="https://github.com/osxfuse/osxfuse/issues/12">"OSXFUSE 2.3.4 has no ppc compiled in"</a>.</li>
+    <li>Added support for building PowerPC file systems on macOS 10.6 and 10.7, if an appropriate version of Xcode is installed (e.g. Xcode 3.2.6). Tracked as issue #12: <a href="https://github.com/macfuse/macfuse/issues/12">"OSXFUSE 2.3.4 has no ppc compiled in"</a>.</li>
 </ul>
 <h3>Fixes</h3>
 <ul>
     <li>Fixed a race condition, that would lead to a file system deadlock. The deadlock could be triggered by a read/write operation in <code>fuse_internal_strategy</code> on a file, that another thread had just created (but not opened, yet).</li>
     <li>Fixed a deadlock in <code>fuse_vnop_mmap</code> that affected certain file systems (i. e. MooseFS). It could by triggered by the file operation <code>VNOP_MMAP</code> which tries to authorize the action on the vnode corresponding to the file. In case the authorization is not already cached <code>VNOP_GETATTR</code> is called which caused the deadlock.</li>
     <li>Fixed an issue that could trigger a <code>vnode reclaim in
-        progress</code> kernel panic on 32-bit kernels of macOS 10.6 and later. Tracked as issue #16: <a href="https://github.com/osxfuse/osxfuse/issues/16">"vnode reclaim in progress - NTFS"</a>.</li>
+        progress</code> kernel panic on 32-bit kernels of macOS 10.6 and later. Tracked as issue #16: <a href="https://github.com/macfuse/macfuse/issues/16">"vnode reclaim in progress - NTFS"</a>.</li>
     <li>Fixed an issue where Finder would report a wrong file size for files on sparse FUSE file systems.</li>
     <li>Fixed an issue that caused Finder on macOS 10.6 and later to not display updated free/used space values for FUSE volumes. This is done by enabling capability <code>VOL_CAP_FMT_FAST_STATFS</code> by default and implementing the mount-time option <code>slow_statfs</code>. This option is interesting for network file systems where calls to <code>statfs</code> are expensive.</li>
 </ul>

_posts/2012-05-28-OSXFUSE-2.4.0.html

@@ -16,22 +16,22 @@
 <h3>New Features</h3>
 <ul>
     <li>Added experimental support for OS X 10.8.</li> 
-    <li>Added support for Xcode 4.3. The following additional packages need to be installed in order to build OSXUFSE using Xcode 4.3: Command Line Tools for Xcode, Auxiliary Tools for Xcode, Autotools, and Libtool. See <a href="https://github.com/osxfuse/osxfuse/blob/osxfuse-2/README.md">README.md</a> for more information.</li>
+    <li>Added support for Xcode 4.3. The following additional packages need to be installed in order to build OSXUFSE using Xcode 4.3: Command Line Tools for Xcode, Auxiliary Tools for Xcode, Autotools, and Libtool. See <a href="https://github.com/macfuse/macfuse/blob/osxfuse-2/README.md">README.md</a> for more information.</li>
 </ul>
 <h3>Fixes</h3>
 <ul>
-    <li>Resolved an issue, that could trigger a <code>vnode reclaim in progress</code> kernel panic on macOS 10.5. Tracked as issue #16: <a href="https://github.com/osxfuse/osxfuse/issues/16">"vnode reclaim in progress - NTFS"</a>.
+    <li>Resolved an issue, that could trigger a <code>vnode reclaim in progress</code> kernel panic on macOS 10.5. Tracked as issue #16: <a href="https://github.com/macfuse/macfuse/issues/16">"vnode reclaim in progress - NTFS"</a>.
     <li>Fixed a bug in the implementation of the <code>exchange</code> file  system operation, that could cause data loss or corruption on macOS 10.7 or later.</li>
-    <li>Resolved several issues, that were caused by using the build-time macro <code>__FreeBSD__</code> when building <code>libosxfuse</code> bindings for various languages. Tracked as issues #17: <a href="https://github.com/osxfuse/osxfuse/issues/17">"osxfuse.pc contains -D__FreeBSD__=10"</a> and #25: <a href="https://github.com/osxfuse/osxfuse/issues/25">"sys/statfs.h included but unnecessary"</a>.</li>
+    <li>Resolved several issues, that were caused by using the build-time macro <code>__FreeBSD__</code> when building <code>libosxfuse</code> bindings for various languages. Tracked as issues #17: <a href="https://github.com/macfuse/macfuse/issues/17">"osxfuse.pc contains -D__FreeBSD__=10"</a> and #25: <a href="https://github.com/macfuse/macfuse/issues/25">"sys/statfs.h included but unnecessary"</a>.</li>
     <li>Fixed an issue, that could result in FUSE command line options being ignored or overwritten when mounting a FUSE volume on 64-bit Macs.</li>
     <li>Fixed an issue, that could cause OS X to run out of I/O buffer space and become unresponsive in rare cases.
     <li>Fixed several issues, that could trigger a kernel panic when interrupting file system operations on a FUSE volume.</li>
-    <li>Fixed a bug, that was responsible for crashing the Plan 9 FUSE file system (9pfuse) when writing on the mounted FUSE volume. Tracked as issue #28: <a href="https://github.com/osxfuse/osxfuse/issues/28">"Bad length passed to client process in write operation"</a>.</li>
+    <li>Fixed a bug, that was responsible for crashing the Plan 9 FUSE file system (9pfuse) when writing on the mounted FUSE volume. Tracked as issue #28: <a href="https://github.com/macfuse/macfuse/issues/28">"Bad length passed to client process in write operation"</a>.</li>
     <li>Fixed a bug in the updater tool, that caused developer releases not appearing as an update option.</li>
 </ul>
 <h3>Changes</h3>
 <ul>
-    <li>Use the FUSE for OS X logo as fallback volume icon, in case a file system linked against <code>OSXFUSE.framework</code> does not supply a custom volume icon (option <code>volicon</code>). Tracked as issue #27: <a href="https://github.com/osxfuse/osxfuse/issues/27">"Include default volume icon as framework resource"</a>.</li>
+    <li>Use the FUSE for OS X logo as fallback volume icon, in case a file system linked against <code>OSXFUSE.framework</code> does not supply a custom volume icon (option <code>volicon</code>). Tracked as issue #27: <a href="https://github.com/macfuse/macfuse/issues/27">"Include default volume icon as framework resource"</a>.</li>
     <li>Include DWARF version 2 debug information for <code>libosxfuse</code> and <code>libmacfuse</code> to make debugging FUSE file systems easier. The debug symbol bundles are stored in <code>OSXFUSE.framework/Resources/Debug</code>.</li>
     <li>Various under-the-hood improvements like enabling support for hidden files on FUSE volumes and case-sensitive file systems.</li>
 </ul>

_posts/2012-08-01-OSXFUSE-2.5.0.html

@@ -16,18 +16,18 @@
 <h3>New Features</h3>
 <ul>
     <li>Full support for OS X 10.8.</li>
-    <li>Full support for Xcode 4.4 on OS X 10.7 and 10.8. See <a href="https://github.com/osxfuse/osxfuse/blob/osxfuse-2/README.md">README.md</a> for more information on building OSXFUSE.</li>
+    <li>Full support for Xcode 4.4 on OS X 10.7 and 10.8. See <a href="https://github.com/macfuse/macfuse/blob/osxfuse-2/README.md">README.md</a> for more information on building OSXFUSE.</li>
     <li>Implemented FUSE device operation <code>select</code>. Using system call <code>select</code> allows waiting for FUSE requests sent from the kernel extension to a user space FUSE daemon in a very efficient manner while handling other events in the same thread. Patch by Thomas Nordin.</li>
 </ul>
 <h3>Fixes</h3>
 <ul>
     <li>Fixed a bug, that can trigger a kernel panic when performing file system operations on a dying FUSE volume. Reported by Andreas Guðmundsson: <a href="https://groups.google.com/d/topic/osxfuse-group/zwpaEy6aGZ4/discussion">"panic in fuse_vnop_mmap"</a>.</li>
     <li>Fixed an issue where user space FUSE file systems, that are being unmounted, do not receive reclaim messages before receiving message <code>FUSE_DESTROY</code>. Patch by Anatol Pomozov.</li>
-    <li>Fixed a bug, that can trigger a kernel panic when reading or writing files on a FUSE volume. Tracked as issue #35: <a href="https://github.com/osxfuse/osxfuse/issues/35">"Kernel panic on osx 10.7"</a>.</li>
+    <li>Fixed a bug, that can trigger a kernel panic when reading or writing files on a FUSE volume. Tracked as issue #35: <a href="https://github.com/macfuse/macfuse/issues/35">"Kernel panic on osx 10.7"</a>.</li>
     <li>Fixed an issue that can prevent a multi-threaded FUSE file systems from terminating when receiving singal <code>SIGINT</code> (Ctrl+C). Based on a patch by Anatol Pomozov.</li>
-    <li>Addressed an issue, that can result in unexpected behavior of Objective-C FUSE file systems using <code>OSXFUSE.framework</code>. This issue was caused by using a non thread safe file manager instance. Tracked as issue #37: <a href="https://github.com/osxfuse/osxfuse/issues/37">"ObjC framework should avoid [NSFileManager defaultManager]"</a></li>
+    <li>Addressed an issue, that can result in unexpected behavior of Objective-C FUSE file systems using <code>OSXFUSE.framework</code>. This issue was caused by using a non thread safe file manager instance. Tracked as issue #37: <a href="https://github.com/macfuse/macfuse/issues/37">"ObjC framework should avoid [NSFileManager defaultManager]"</a></li>
     <li>Fixed a bug, that prevents user root from accessing files on a FUSE volume despite mount-time option <code>allow_root</code> being set. The issue is caused by an inconsistent permission check in file system operation <code>access</code>. Patch by Anatol Pomozov.</li>
-    <li>Fixed an issue, that triggers a kernel panic on OS X 10.8 in case of a failed mount attempt of a FUSE volume. Tracked as issue #38: <a href="https://github.com/osxfuse/osxfuse/issues/38">"sshfs-2.4.1 / osxfuse-2.4.2 kernel panic when a remote directory is mounted twice"</a>, issue #43: <a href="https://github.com/osxfuse/osxfuse/issues/43">Mountain Lion kernal panic</a> and issue #44: <a href="https://github.com/osxfuse/osxfuse/issues/44">"Mountain Lion kernel panics"</a>.</li>
+    <li>Fixed an issue, that triggers a kernel panic on OS X 10.8 in case of a failed mount attempt of a FUSE volume. Tracked as issue #38: <a href="https://github.com/macfuse/macfuse/issues/38">"sshfs-2.4.1 / osxfuse-2.4.2 kernel panic when a remote directory is mounted twice"</a>, issue #43: <a href="https://github.com/macfuse/macfuse/issues/43">Mountain Lion kernal panic</a> and issue #44: <a href="https://github.com/macfuse/macfuse/issues/44">"Mountain Lion kernel panics"</a>.</li>
     <li>Addressed an issue, that can trigger a kernel panic in tight mount/umount cycles on macOS 10.5 and later. Bug reported by Zach Marquez: <a href="https://groups.google.com/d/topic/osxfuse-group/Pou_FM8uSYw/discussion">"Kernel panic in tight mount/unmount loop"</a></li>
 </ul>
 <h3>Changes</h3>