Skip to content
This repository has been archived by the owner on May 2, 2024. It is now read-only.

Outdated cask: osxfuse-beta #1615

Closed
vitorgalvao opened this issue Jan 29, 2016 · 1 comment
Closed

Outdated cask: osxfuse-beta #1615

vitorgalvao opened this issue Jan 29, 2016 · 1 comment

Comments

@vitorgalvao
Copy link
Member

Outdated cask: osxfuse-beta.

Info:

Full appcast:

<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xml:lang="en-US">
  <id>tag:github.com,2008:https://github.com/osxfuse/osxfuse/releases</id>
  <link type="text/html" rel="alternate" href="https://github.com/osxfuse/osxfuse/releases"/>
  <link type="application/atom+xml" rel="self" href="https://github.com/osxfuse/osxfuse/releases.atom"/>
  <title>Release notes from osxfuse</title>
  <updated>2016-01-18T19:08:34Z</updated>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-2.8.3</id>
<updated>2016-01-18T19:08:34Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-2.8.3"/>
<title>osxfuse-2.8.3</title>
<content type="html">&lt;p&gt;Bump version to 2.8.3&lt;/p&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-3.1.0</id>
<updated>2016-01-20T20:40:31Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-3.1.0"/>
<title>FUSE for OS X 3.1.0</title>
<content type="html">&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The kernel extension does no longer use the first free slot when registering osxfuse character devices. In practice there are kernel internal devices that use absolute index values, which will stomp on free-slot based assignments that happen before them. Slot 12 is considered a safe starting index for Mac OS X 10.5 to 10.7, 24 for OS X 10.8 and later. See bsd/kern/bsd_stubs.c for details.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Update pkg-config files&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Remove &lt;code&gt;-pthread&lt;/code&gt; option from &lt;code&gt;Libs&lt;/code&gt; line in &lt;code&gt;osxfuse.pc&lt;/code&gt; and &lt;code&gt;macfuse.pc&lt;/code&gt; as it is not required on OS X and causes issues when using clang. See &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/256&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/256&quot; data-id=&quot;124186876&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#256&lt;/a&gt; for details.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Remove &lt;code&gt;Libs.private&lt;/code&gt; line from &lt;code&gt;osxfuse.pc&lt;/code&gt;. libosxfuse does not support static linking.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Update MacFUSE compatibility layer from FUSE version 2.7.3 to 2.7.4.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add instructions for using Homebrew instead of MacPorts to install the required third-party build tools autoconf, automaker, libtool, and gettext.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Improve compatibility with Finder on OS X 10.11&lt;/p&gt;

&lt;p&gt;Unless &lt;code&gt;allow_root&lt;/code&gt; or &lt;code&gt;allow_other&lt;/code&gt; is set we limit vnode operations to the user that mounted the file system. Starting with OS X 10.11 &lt;code&gt;DesktopServicesHelper&lt;/code&gt;, which is running as root, calls &lt;code&gt;access(2)&lt;/code&gt; on behalf of Finder when trying to delete a directory. Blocking this request results in Finder aborting the delete process. Therefore we are no longer enforcing &lt;code&gt;allow_root&lt;/code&gt; or &lt;code&gt;allow_other&lt;/code&gt; for &lt;code&gt;vnop_access&lt;/code&gt;. &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Fix mount-init-unmount race condition&lt;/p&gt;

&lt;p&gt;The volume might be unmounted before we are able to complete the asynchronous &lt;code&gt;FUSE_INIT&lt;/code&gt; process. This could result in a &quot;trying to interlock destroyed mutex&quot; kernel panic.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Fix mount-init-abi race condition&lt;/p&gt;

&lt;p&gt;Wait until the FUSE session is initialized before generating user space requests. We do not know which ABI version to use until the initialization process is complete.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-3.0.9</id>
<updated>2016-01-03T01:29:19Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-3.0.9"/>
<title>FUSE for OS X 3.0.9</title>
<content type="html">&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;The FUSE kernel extension used to treat all signals, received while waiting for the user space file system daemon to respond to a file system request, as fatal. On OS X there is no public API to block signals in kernel mode or to determine which signal caused the current interrupt. This is why there have been only two options:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Treat all signals a fatal and return immediately.&lt;/li&gt;
&lt;li&gt;Ignore all signals, including fatal ones.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Before version 3.0.9 all signals were treated as fatal. Between those two options this one is the &quot;safer&quot; one, as we do not want file systems to hang the whole system. The problem is that it can become virtually impossible to complete any I/O operation under high signal pressure on a high latency (e.g. network) file system.&lt;/p&gt;

&lt;p&gt;In 3.0.9, if a process that is issuing a FUSE file system operation is interrupted, the following will happen:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;If the corresponding request is not yet sent to user space, then an &quot;interrupted&quot; flag is set for the request. When the request has been successfully transferred to user space and this flag is set, an &lt;code&gt;FUSE_INTERRUPT&lt;/code&gt; request is queued.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If the request is already sent to user space, then an &lt;code&gt;FUSE_INTERRUPT&lt;/code&gt; request is queued.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If a file system request is not yet sent to user space and the process issuing the request is aborted (&lt;code&gt;SIGKILL&lt;/code&gt; or unhandled fatal signal), then the request is marked as answered and returns immediately.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This fixes issue &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/213&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/213&quot; data-id=&quot;87764509&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#213&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Improve support for &lt;code&gt;sigaction(2)&lt;/code&gt; flag &lt;code&gt;SA_RESTART&lt;/code&gt;. This fixes issue &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/228&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/228&quot; data-id=&quot;100887528&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#228&lt;/a&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-3.0.8</id>
<updated>2016-01-01T19:07:57Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-3.0.8"/>
<title>FUSE for OS X 3.0.8</title>
<content type="html">&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Ignore &lt;code&gt;vfs_update_vfsstat()&lt;/code&gt; error on mount.&lt;/p&gt;

&lt;p&gt;Do not treat &lt;code&gt;vfs_update_vfsstat()&lt;/code&gt; failing when mounting a FUSE volume as a fatal error. The worst that can happen is &lt;code&gt;vfsstat&lt;/code&gt; being stale.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-3.0.7</id>
<updated>2016-01-03T01:29:53Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-3.0.7"/>
<title>FUSE for OS X 3.0.7</title>
<content type="html">&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Improve compatibility with Finder. Starting with OS X 10.9 &lt;code&gt;syspolicyd&lt;/code&gt; (which is running as root) calls &lt;code&gt;getxattr(2)&lt;/code&gt; when opening items in Finder. Blocking these calls results in Finder displaying an error message. Therefore we are no longer blocking &lt;code&gt;getxattr(2)&lt;/code&gt; calls by root even if &lt;code&gt;allow_root&lt;/code&gt; or &lt;code&gt;allow_other&lt;/code&gt; is not set.&lt;/p&gt;

&lt;p&gt;This fixes issue &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/162&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/162&quot; data-id=&quot;43221888&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#162&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Fix &lt;code&gt;select(2)&lt;/code&gt; for FUSE devices on OS X 10.11. The issue was caused by a kernel private struct that has changed between OS X 10.10 and 10.11.&lt;/p&gt;

&lt;p&gt;See &lt;a href=&quot;https://groups.google.com/d/msg/osxfuse-group/SaumUOcriPA/ujAbniiVCQAJ&quot;&gt;select(2) on channel fd hangs and makes system unstable on El Capitan&lt;/a&gt; for details.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Fix unified buffer cache invalidation error when expanding files. Unless the file did end on a page boundary we are now invalidating the last page of the file&#39;s unified buffer cache manually.&lt;/p&gt;

&lt;p&gt;This fixes issue &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/237&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/237&quot; data-id=&quot;109218160&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#237&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-2.8.2</id>
<updated>2015-10-25T18:04:47Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-2.8.2"/>
<title>osxfuse-2.8.2</title>
<content type="html">&lt;p&gt;Bump version to 2.8.2&lt;/p&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-2.8.1</id>
<updated>2015-09-24T22:27:36Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-2.8.1"/>
<title>osxfuse-2.8.1</title>
<content type="html">&lt;p&gt;Bump version to 2.8.1&lt;/p&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-3.0.6</id>
<updated>2016-01-17T21:51:12Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-3.0.6"/>
<title>FUSE for OS X 3.0.6</title>
<content type="html">&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Improve compatibility with Finder on OS X 10.11&lt;/p&gt;

&lt;p&gt;Unless &lt;code&gt;allow_root&lt;/code&gt; or &lt;code&gt;allow_other&lt;/code&gt; is set we limit vnode operations to the user that mounted the file system. Starting with OS X 10.11 &lt;code&gt;DesktopServicesHelper&lt;/code&gt;, which is running as root, calls &lt;code&gt;stat(2)&lt;/code&gt; on behalf of Finder when trying to delete a directory. Blocking this request results in Finder aborting the delete process. Therefore we are no longer enforcing &lt;code&gt;allow_root&lt;/code&gt; or &lt;code&gt;allow_other&lt;/code&gt; for &lt;code&gt;vnop_getattr&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Fix error handling for &lt;code&gt;FUSE_NOTIFY_INVAL_INODE&lt;/code&gt; notifications. See &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/233&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/233&quot; data-id=&quot;105659330&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#233&lt;/a&gt; for details.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Fix race condition in &lt;code&gt;vfsop_sync()&lt;/code&gt; that can trigger a &quot;Attempted to lock max-locked recursive lock&quot; kernel panic. See &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/232&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/232&quot; data-id=&quot;104982929&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#232&lt;/a&gt; for details.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Fetch new releases over HTTPS. See &lt;a href=&quot;https://github.com/osxfuse/prefpane/pull/2&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/prefpane/issues/2&quot; data-id=&quot;98700888&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/prefpane#2&lt;/a&gt; for details.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-3.0.5</id>
<updated>2016-01-03T01:31:33Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-3.0.5"/>
<title>FUSE for OS X 3.0.5</title>
<content type="html">&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Update libfuse to version 2.9.4&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Initilalize stat buffer passed to &lt;code&gt;getattr()&lt;/code&gt; and &lt;code&gt;fgetattr()&lt;/code&gt; to zero in all cases.&lt;/li&gt;
&lt;li&gt;Fix &lt;code&gt;fuse_remove_signal_handlers()&lt;/code&gt; to properly restore the default signal handler.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Refactor the non-portable libfuse function &lt;code&gt;fuse_purge_np()&lt;/code&gt; to use the the standard function &lt;code&gt;fuse_lowlevel_notify_inval_inode()&lt;/code&gt; instead of of the non-portable &lt;code&gt;FUSEDEVIOCALTERVNODEFORINODE&lt;/code&gt; ioctl.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The non-portable libfuse functions &lt;code&gt;fuse_purge_np()&lt;/code&gt; and &lt;code&gt;fuse_knote_np()&lt;/code&gt; are now obsolete and therefore deprecated.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Fix vnode invalidation notification handling in FUSE kernel extension by updating the vnode&#39;s attributes upon receiving a &lt;code&gt;FUSE_NOTIFY_INVAL_INODE&lt;/code&gt; notification to detect remote file size changes. See &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/229&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/229&quot; data-id=&quot;102029501&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#229&lt;/a&gt; for details.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Cache vnode attributes when creating vnodes. This guarantees that &lt;code&gt;va_iosize&lt;/code&gt; has been initialized before processing read or write requests. A &lt;code&gt;va_iosize&lt;/code&gt; of zero bytes will trigger an infinite number of zero byte reads or writes. See &lt;a href=&quot;https://github.com/osxfuse/osxfuse/issues/224&quot; class=&quot;issue-link js-issue-link&quot; data-url=&quot;https://github.com/osxfuse/osxfuse/issues/224&quot; data-id=&quot;100199944&quot; data-error-text=&quot;Failed to load issue title&quot; data-permission-text=&quot;Issue title is private&quot;&gt;osxfuse/osxfuse#224&lt;/a&gt; for details.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Invalidate directory attributes when creating file. When creating a file using &lt;code&gt;open(2)&lt;/code&gt; and &lt;code&gt;O_CREAT&lt;/code&gt;, POSIX requires that the parent directory&#39;s ctime and mtime be updated (if the file did not exist):&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;If O_CREAT is set and the file did not previously exist, upon
successful completion, open() shall mark for update the st_atime,
st_ctime, and st_mtimefields of the file and the st_ctime and
st_mtime fields of the parent directory.
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;For details see &lt;a href=&quot;https://groups.google.com/d/msg/osxfuse-group/bGY4ehPQdCM/pGg-Cm1BW0gJ&quot;&gt;Minor bug with directory mtimes and O_CREAT&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Hide &lt;code&gt;xcodebuild&lt;/code&gt; output when building osxfuse if verbose flag is not set.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
  <entry>
<id>tag:github.com,2008:Repository/1867347/osxfuse-3.0.4</id>
<updated>2016-01-02T19:56:15Z</updated>
<link rel="alternate" type="text/html" href="/osxfuse/osxfuse/releases/tag/osxfuse-3.0.4"/>
<title>FUSE for OS X 3.0.4</title>
<content type="html">&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Add experimental support for OS X 10.11.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add experimental support for Xcode 7.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Fix an incompatibility with Microsoft Office 2016 preventing Office from saving documents on FUSE volumes.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Fix an incompatibility with FUSE ABI versions below 7.12. In previous releases the file open mode in &lt;code&gt;FUSE_OPEN&lt;/code&gt; messages to the file system daemon has always been 0.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
<author>
  <name>bfleischer</name>
</author>
<media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/716336?v=3&amp;s=60"/>
  </entry>
</feed>
@vitorgalvao vitorgalvao mentioned this issue Jan 30, 2016
Closed
@vitorgalvao
Copy link
Member Author

Closing in favour of #1631.

@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vitorgalvao @miccal