fs bundles are ignored from /Library

Originator:jorgen.lundman
Number:rdar://15217592 Date Originated:
Status:open Resolved:
Product:Mavericks Product Version:
Classification: Reproducible:
 
Apple is moving developers out of /System, for example with (signed) kexts to go in /Library.
However, /System/Library/Filesystems/fs.bundle/ is currently only only place processed, /Library/Filesystems/ is ignored. As can be seen in line 59 in loadable_fs.h

Apple support indicates that internally <rdar://problem/15217592> exists.

Comments

Reply from Apple, Radar closed

Apple Developer Relations 21-Nov-2014 04:46 PM

Engineering has determined that there are no plans to address this issue.

We are now closing this bug report.

If you have questions regarding the resolution of this issue, please update your bug report with that information.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.

By d235j.1 at Nov. 21, 2014, 11:31 p.m. (reply...)

Initial Radar report

This was my bug report. Originator: d235j.1 Date: 13-Oct-2013 04:36 PM Summary: Within the WWDC 2013 KEXT session, we were asked to let Apple know if there is any need to write to /System, as /System would be locked down in the future. I have run into such a need just now: a filesystem bundle must be in /System/Library/Filesystems for automounting to work. Simply placing it in /Library/Filesystems is not good enough. This path seems to be hardcoded in /usr/include/sys/loadable_fs.h .

Other than this major issue, I can't easily think of a reason for a developer to need to write to /System, but if there are any, I will open another report.

Steps to Reproduce: 1. Place a custom filesystem in /Library/Filesystems. 2. Attempt to mount a volume that requires it.

Expected Results: The volume should mount with the specified filesystem.

Actual Results: The volume does not mount with the specified filesystem. If there is a filesystem in /System/Library/Filesystems it mounts with that one; otherwise it does not mount at all.

Version: OS X 10.8+ and 10.9+

Notes: The filesystem API isn't documented other than in the header; some documentation and sample code would be nice, but I understand that other things have a higher priority. The ability to add filesystem modules is very nice to have.

Also, it would be nice if the API for stacking file systems was more accessible, now that Core Storage does this.

Configuration: All configurations

Attachments:

In addition, diskarbitrationd should use the value of the FSMountExecutable and the FSMountArguments keys in the filesystem bundle's Info.plist when mounting a filesystem, rather than hardcoding /sbin/mount_. This would make filesystem bundles much more portable, as writing to /sbin should also be discouraged.

By d235j.1 at Nov. 21, 2014, 11:30 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!