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

  • Thread starter Thread starter DarkMatterCore
  • Start date Start date
  • Views Views 46,585
  • Replies Replies 189
  • Likes Likes 61
I thought this would be homebrew oriented, but I see it leaned towards hacking, which contradicts OP.

Let's hope to see this great module in productive applications in the future and not in another mindless installer.
 
I thought this would be homebrew oriented, but I see it leaned towards hacking, which contradicts OP.

Let's hope to see this great module in productive applications in the future and not in another mindless installer.
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.
 
Last edited by DarkMatterCore,
or that Atmosphère itself enables piracy just because it's possible to load sigpatches with it.
Trying to explain this to some people is like hitting wall.
Atmosphere has clear purpose which some people think that can be strained to launch unsigned installed apps but SciresM doesn't want to.

The same is with this library. It has clear purpose and if you don't get it after reading license, then politely speaking fuck off and go elsewhere bitching about devs being villains.

To be safe: I'm not attacking you @Ghost92
 
Last edited by masagrator,
2020121002373800-F1C11A22FAEE3B82F21B330E1B786A39.mp4_snapshot_00.03.163.jpg
 

Does dev branch work? should I recompile / release tinleaf with this yet?

Also have you heard anything about crashing on exit with this library? not sure if its tinfleaf or this library, but there seems to be an error upon process exit. Ive been too busy to troubleshoot lately.
 
Last edited by blawar,
I have a 700GB GenDisk SCSI\DiskST3750640NS Drive in ExFat Format. When I use their .nro test it shows nothing or hangs

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

Does dev branch work? should I recompile / release tinleaf with this yet?

Also have you heard anything about crashing on exit with this library? not sure if its tinfleaf or this library, but there seems to be an error upon process exit. Ive been too busy to troubleshoot lately.

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.
 
Last edited by DarkMatterCore,
Untested. I just compiled your dev branch and linked it. Hopefully someone will test.
Pressing A on "Install over USB HDD" crashes when a NTFS drive is connected. Pressing A on "Exit" crashes too. ExFAT works.

I don't have SXOS not sure what else i can test.
 
  • Like
Reactions: blawar
Pressing A on "Install over USB HDD" crashes when a NTFS drive is connected. Pressing A on "Exit" crashes too. ExFAT works.

I don't have SXOS not sure what else i can test.

Can you post the atmosphere crashlog for the NTFS crash?

Also, did you run it in high memory mode when it crashed with NTFS?
 
Can you post the atmosphere crashlog for the NTFS crash?

Also, did you run it in high memory mode when it crashed with NTFS?
I don't get an atmosphere crash it's just the "Software closed because an error occurred" type of crash. And yes I'm running it in high memory mode.
Sorry I did some more testing and installing from NTFS actually does work but i have to start tinleaf first and then connect the drive. After exiting i also have to reboot my switch to get it to connect again. With ExFAT i can just leave the drive attached to one of the docks usb ports but with NTFS it will not work.

I only get an atmosphere crash when i try it in applet mode, if you want i can post that.

--------------------- MERGED ---------------------------

Can you post the atmosphere crashlog for the NTFS crash?
Oh i just realised atmosphere has crashlogs for more than just fatal errors, here's the log
 

Attachments

@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.
 

Attachments

Last edited by DarkMatterCore,
  • Like
Reactions: peteruk
@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.
I can't reproduce this, i get the same result don't matter if i'm connecting before or after launch(all tests succeed except for file copy like in the pic you posted yesterday).
I guess it's just tinleaf not initializing/unmounting properly or something
 
  • Like
Reactions: DarkMatterCore
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 can't reproduce this, i get the same result don't matter if i'm connecting before or after launch(all tests succeed except for file copy like in the pic you posted yesterday).
I guess it's just tinleaf not initializing/unmounting properly or something
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.
 

Site & Scene News

Popular threads in this forum