| |||||||||||||
Samsung's F2FS filesystemSamsung's F2FS filesystemPosted Oct 6, 2012 0:43 UTC (Sat) by geofft (subscriber, #59789)In reply to: Samsung's F2FS filesystem by drag Parent article: Samsung's F2FS filesystem
I also can't believe that faking up a FAT filesystem in memory and exposing that to the host would be terribly hard. (qemu has the read-only version of that with -hda fat:/path/to/something, and honestly saying that you get read-only support unless you install the right filesystem driver seems just fine to me.)
(Log in to post comments)
Samsung's F2FS filesystem Posted Oct 8, 2012 9:51 UTC (Mon) by moltonel (guest, #45207) [Link]
The problem with that is that USB mass storage works (by specs) by giving direct access to the hardware. So direct that the device's OS (Android for example) needs to stop pretty much all activity to be sure to not touch the hardware at the same time as the computer's OS. That's why you can't do anything else (listen to music, etc) while your phone/player/etc is connected as a usb key.
If you want to fake a filesystem, you'll have to fake the USB hardware controlers below it first. And that's certainly trickyer.
MTP and iTunes allow concurrent access by the host and the guest, and that's arguably the only good thing about these protocols.
Samsung's F2FS filesystem Posted Oct 8, 2012 13:11 UTC (Mon) by drag (subscriber, #31333) [Link]
Well you'd have to fake it with a emulated block device hosting fat32. It's sounds plausable, but a pain in the rear to do well.
MTD seems cleaner and if Linux support for MTD as a client didn't suck then I would be happy about it.
Samsung's F2FS filesystem Posted Oct 12, 2012 0:42 UTC (Fri) by Comet (subscriber, #11646) [Link]
Calibre as a client has MTD support, for managing books on such devices; it's all GPL'd Python and runs on Linux.
|
|||||||||||||