bispawel / macfuse

Automatically exported from code.google.com/p/macfuse
Other
0 stars 0 forks source link

Filesystem installed into /System/Library - why not /Library? #78

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Just as the extension is now installed in /Library/Extensions, why can't 
fusefs.fs be installed into /
Library/Filesystems?

Original issue reported on code.google.com by kball...@gmail.com on 30 Jan 2007 at 9:19

GoogleCodeExporter commented 8 years ago
See issue #1, the same question appears there. This blog post seems to cover 
the answer: http://
daringfireball.net/2003/08/the_one_and_only_mac_os_x_extensions_folder

Original comment by eddie.va...@gmail.com on 2 Feb 2007 at 2:29

GoogleCodeExporter commented 8 years ago
eddie, go back and read my post. MacFUSE 0.1.9 does in fact already use 
/Library/Extensions. The question was 
about the Filesystems folder, and the post you referenced does not talk about 
Filesystems at all. Also, the stated 
reasons for restricting autoload of Extensions to /System/Library/Extensions 
does not apply to Filesystems - 
there's no equivalent to the kextcache for them, and BootX doesn't need to care 
about them.

Original comment by kball...@gmail.com on 2 Feb 2007 at 7:08

GoogleCodeExporter commented 8 years ago
Amit can say for certain, but I remember him saying that the system 
(unfortunately)
only looks in /System/Library/Filesystems for filesystem bundles.

Original comment by motown...@gmail.com on 4 Feb 2007 at 6:35

GoogleCodeExporter commented 8 years ago
For what it's worth, I build MacFUSE and SSHFS from the source provided here, 
patching ever so slightly to put 
the fusefs.fs filesystem stuff under /LibraryFilesystems.

Seems to work just fine.

This is with macfuse 0.1.8 on OSX 10.4.8.

Original comment by jdput...@gmail.com on 13 Feb 2007 at 5:52

GoogleCodeExporter commented 8 years ago
When you do a cmd-i (get info) on an sshfs volume icon, what do you see in the 
"Format:" field?

Original comment by si...@gmail.com on 14 Feb 2007 at 9:50

GoogleCodeExporter commented 8 years ago
Format: Unknown (fusefs)

Original comment by jdput...@gmail.com on 16 Feb 2007 at 10:20

GoogleCodeExporter commented 8 years ago
Right. So the Finder (technically, things underneath the Finder) cannot find 
"fusefs.fs". You should be seeing "SSH 
File System (MacFUSE)".

Depends on one's definition of "works just fine".

The bundle is a *passive* entity. It's not like by putting it in 
/System/Library/Filesystems, you would cause bad 
things to happen. In the case of file systems like ntfs-3g, where you want such 
bundles to specify more things 
beyond just file system type strings, it wouldn't even "work fine" if the 
bundle can't be "found".

Original comment by si...@gmail.com on 17 Feb 2007 at 12:32

GoogleCodeExporter commented 8 years ago
Since I do very little with the finder for SSHFS file systems, I guess my 
definition of "just fine" is OK, but clearly 
wrong.

Thank you for pointing out the error of my ways. I'll update my personal builds 
to put the fusefs.fs  bundle under 
/System/Library/Filesystems where it clearly belongs.

Jeff.

Original comment by jdput...@gmail.com on 20 Feb 2007 at 11:03

GoogleCodeExporter commented 8 years ago

Original comment by si...@gmail.com on 22 Feb 2007 at 9:29