Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NTFS-3G support #7

Closed
GoogleCodeExporter opened this issue Jun 4, 2015 · 3 comments
Closed

NTFS-3G support #7

GoogleCodeExporter opened this issue Jun 4, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Perhaps one of the most ambitious file system implementations on top of FUSE is 
NTFS-3G 
<http://www.ntfs-3g.org/>. However, it currently has its ./configure script 
hardcoded to disallow non-
Linux building. This is likely due to their understandable unwillingness to 
support a setup they cannot 
maintain themselves:
<http://www.ntfs-3g.org/support.html#endian64>
"The code is 64-bit clean, endian safe and it's reported to work on these 
systems. ///However 
unfortunately we are unable to validate the functionality and keep ensuring 
correctness and reliability 
due to lack of dedicated such hardwares for development///."
<http://forum.ntfs-3g.org/viewtopic.php?p=449#449>
"Mac may work but ///we can't officially support hardwares we don't 
have permanent physical access because we think that would be highly 
irresponsible regards to users data integration///."

Now, naturally the developers of MacFUSE *do* presumably have "permanent 
physical access" to Mac 
hardware (and, certainly, others interested in this do). Would it therefore be 
possible to work on a patch 
to their tarball?

Original issue reported on code.google.com by chucker...@gmail.com on 11 Jan 2007 at 10:22

@GoogleCodeExporter
Copy link
Author

Never mind. #6 beat me to it by mere minutes.

Original comment by chucker...@gmail.com on 11 Jan 2007 at 10:22

@GoogleCodeExporter
Copy link
Author

Removing the restriction is easy; we're not going to patch their tarball.

Original comment by motown...@gmail.com on 12 Jan 2007 at 2:51

  • Changed state: WontFix

@GoogleCodeExporter
Copy link
Author

There's no need to patch the tarball.  If you want to override that check, you 
can look for the line that starts with:

case "$target_os"

in the configure script. It switches on "linux*". You can, for experimental 
purposes, change "linux*" to just "*".

Original comment by si...@gmail.com on 12 Jan 2007 at 2:54

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant