search

mahinthjoe / macfuse

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

Internal NTFS Volumes are considered "ejectable". #63

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Using a "Eject all ejectable Volumes" Script will unmount the NTFS Volume
2. Eject icon appears in Sidebar for an internal volume.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Macfuse 0.1.7/  Mac OSX 10.4.8

Please provide any additional information below.

Original issue reported on code.google.com by chumsd...@gmail.com on 29 Jan 2007 at 3:03

GoogleCodeExporter commented 8 years ago 
All MacFUSE volumes are indeed considered ejectable. From the standpoint of 
MacFUSE, everything is 
"external" (as in -- user space -- quite analogous to a 
remote/across-the-network file system).

Original comment by si...@gmail.com on 29 Jan 2007 at 3:27

GoogleCodeExporter commented 8 years ago 
It's reasonable, I saw the location was actually file://localhost/Volume/blah
But I wonder if there can be some switch to handle, or maybe an hidden file 
called
".ntfs-internal" to avoild the Eject?

Original comment by chumsd...@gmail.com on 29 Jan 2007 at 8:04

GoogleCodeExporter commented 8 years ago 
MacFUSE volumes are not "network" volumes -- it's just that they are not local 
(disk-based) volumes. There is no 
block device involved, and the way the mount system call works on Mac OS X, if 
you specify that you're using a 
block device at mount time, the kernel will try to open it as such for  you 
(before the call even reaches MacFUSE). 
Therefore, it is not justifiable to jump through a million hoops just to 
convince the kernel otherwise.

Original comment by si...@gmail.com on 5 Feb 2007 at 1:11