WIP libusbhsfs - USB Mass Storage Class Host + Filesystem Mounter static library.

It's homebrew oriented. Dunno what made you think otherwise. The whole purpose of licensing it under ISC is to give developers full liberty to do whatever they please with the library, even if it's a private and/or closed-source project. This is also the license used by libnx itself, for example.

XorTroll and I agreed on it because we felt like it's something that deserves to be freely used without enforcing developers to comply with license-specific restrictions. It's just the right way to do it.

If you're referring to the fact that the library is now being used by blawar on his public projects, then I'm sorry to say he has the full right to do so. Look, I'm not gonna play devil's advocate here - I know how you people feel about him, but that doesn't give me (or anyone) the right to revoke him the liberty of using the library as well. The ISC License works that way.

The thing is, I'm one of the developers of this library and I'm not even mad at blawar for using it. Why should I? It was developed to be used *by* developers, regardless of the purpose they may give it. It's like saying libnx enables "mindless installers" just because it is used to build them, or that Atmosphère itself enables piracy just because it's possible to load sigpatches with it. Totally unintended features from their respective creators and contributors.

In the end, it all boils down to the purposes people give to things. Just wanted to make myself very clear about this.

And please, let's not get carried away - nothing wrong has really happened in this particular thread, and I'd very much prefer to keep it that way.

 

I'd say you'd have to try the latest example test app. Many bugs have been fixed in the meantime.

It does work, but we're still working on it (e.g. cleaning up the code). I'll merge it into main soon.

The error on exit was related to users not disconnecting their UMS devices after a previous libusbhsfs session. On exit, the same Allow Medium Removal + Stop Unit commands issued by the "Safely Remove" feature from Windows are used, which make UMS devices unusable unless a bus reset is performed on each one of them. It was already fixed, along with 4 other bugs in the BOT driver.

 

Almost nearing completion. We're only missing NTFS tests under actual applications.

 

@ShroomKing Please confirm if you can also reproduce any issues using the attached test application. If that's the case, please share the "libusbhsfs.log" file that should be located in your SD card root directory after running the application. Feel free to try connecting your USB drive both before and after launching the application.

 

libusbhsfs updated to v0.1.0. Many changes and bugfixes were introduced, but most importantly: NTFS support is now available.

Please check the full changelog at the release page: https://github.com/DarkMatterCore/libusbhsfs/releases/tag/v0.1.0.

I fixed this issue some hours ago. It was related to the fact that the NTFS implementation from the library was keeping references to the root directory inode from mounted NTFS volumes - not anymore, though.