fs-addon already works…
3dEyes wrote:
fs-addon already works...
Nice 8).
Now if only someone would port/write a non-read only NTFS driver…
skoe wrote:
3dEyes wrote:fs-addon already works...Nice 8).
Now if only someone would port/write a non-read only NTFS driver…
This driver does write as well as read NTFS, doesn’t it?
Dirty Harry wrote:
This driver does write as well as read NTFS, doesn't it?
Yes, I thought so too…no?
In any case, this is awesome 
- hopefully it will get added to the Haiku repo 
What license is this code under? I read somewhere (http://joomla.iscomputeron.com/index.php?option=com_content&task=view&id=893&Itemid=2) that it contained code based upon this (http://cia.navi.cx/stats/project/ntfs), which is GPL.
How does this affect it being a part of the Haiku repo?
<disclaimer>I’m not a GPL authority, and I’m more than happy for someone to clarify the situation. Last thing I want is some massive debate about the GPL.</disclaimer>
expensivelesbian wrote:
How does this affect it being a part of the Haiku repo?<disclaimer>I’m not a GPL authority, and I’m more than happy for someone to clarify the situation. Last thing I want is some massive debate about the GPL.</disclaimer>
There are already several GPL “add-ons” in the Haiku repo. As long as none of Haiku’s code links to the GPL code, there is no need to make any Haiku code also GPL.
I believe there is also a --disable-gpl-addons configure option to build the entire tree WITHOUT GPL-licensed add-ons (they’re placed in a separate sub-directory). Keep in mind that a large number of Haiku’s commandline apps are GPL’d including bash… BeOS used a lot of GPL code this way also.
This addon is based on libntfs-3g (linux-ntfs.org) and as investigation - GPL.
Now ntfs addon for haiku works in read-only mode.
Write functions are temporarily disabled now.
It is necessary to solve some problems for write support.
umccullough wrote:
expensivelesbian wrote:How does this affect it being a part of the Haiku repo?<disclaimer>I’m not a GPL authority, and I’m more than happy for someone to clarify the situation. Last thing I want is some massive debate about the GPL.</disclaimer>
There are already several GPL “add-ons” in the Haiku repo. As long as none of Haiku’s code links to the GPL code, there is no need to make any Haiku code also GPL.
I believe there is also a --disable-gpl-addons configure option to build the entire tree WITHOUT GPL-licensed add-ons (they’re placed in a separate sub-directory). Keep in mind that a large number of Haiku’s commandline apps are GPL’d including bash… BeOS used a lot of GPL code this way also.
That’s great. I was wondering a more out loud as I wasn’t sure how far such code could be easily kept apart from the Haiku code, especially something so intrinsic as FS addons. However, I’m sure the gatekeepers will do their bit.
Thanks for the response.