On Tue, Nov 18, 2008 at 1:01 AM, iDeveloper <[EMAIL PROTECTED]> wrote: > > Hi Ted > > I added the ro option back. The ytfs example creates an empty > dictionary for nodes that exist in the videos_ dictionary. Shouldn't > we be returning attributes specified in the .h file (File type, size > etc) > Can you please point me to an example/documentation which explains the > methods and their implementation in detail. > The GMUserFIleSystem specifies pretty much all the documentation. But > an example implementing this might be helpful. I tried running the > LoopbackFS example. But as soon as I select a directory, it gives an > alert saying > > Internal fuse error (rc=1) while attempting to mount the file system. > For now, the best way to diagnose is to look for error messages using > Console. > mount_fusefs: failed to mount /Volumes/loop@/dev/fuse0: Socket is not > connected
I haven't had any problems with LoopbackFS not working and I haven't really seen anyone else report LoopbackFS issues, either. Are you using source from the head of the source tree or from the 1.7 tag (as I recommended earlier)? Also, LoopbackFS is Leopard-only; I don't think it'll even compile on Tiger, so I'm guessing that is not the issue. ted > > And thats where I'm stuck! > > On Nov 18, 1:12 pm, "ted bonkenburg" <[EMAIL PROTECTED]> wrote: >> On Mon, Nov 17, 2008 at 10:44 PM, iDeveloper <[EMAIL PROTECTED]> wrote: >> >> > Hi Ted >> >> > Thanks for the quick response. YTFS works fine. There is no problem >> > with running that example. I've just modified it at some places, like >> > removing the ro option, returning my icns file from iconDataAtPath and >> > returning an array with the folder names in my directory. I've not >> > made any other changes to the code. >> >> It is good to hear that ytfs is working for you. >> >> >> >> > Removed the ro option as I wanted it to be a read-write system. >> >> If you want to create a write-able file system then you really need to >> properly implement almost all of the GMUserFileSystemOperations >> informal protocol methods. In addition, you'll need to be thorough and >> make sure that your operations behave properly by returning proper >> errors, filling in a complete set of attributes in >> attributesOfItemAtPath:, etc. >> >> For this reason, I suggest you get your file system working well in >> read-only mode before you tackle write support. >> >> ted >> >> >> >> > Thanks again >> >> > On Nov 18, 9:12 am, "ted bonkenburg" <[EMAIL PROTECTED]> wrote: >> >> On Mon, Nov 17, 2008 at 8:13 AM, iDeveloper <[EMAIL PROTECTED]> wrote: >> >> >> > Hi >> >> >> > I'm trying to create a file system using the ytfs example as the base. >> >> > But nothing seems to be working with my code! The icns file doesn't >> >> >> Did you get ytfs working? If not, did you follow the tutorial exactly? >> >> Specifically, did you follow the part that recommended that you check >> >> out the 1.5 tag for the YTFS example? >> >> >> svn >> >> checkouthttp://macfuse.googlecode.com/svn/tags/macfuse-1.5/filesystems-objc/y... >> >> ytfs >> >> >> The head ytfs-tutorial is updated to reflect changes to the >> >> Objective-C API that may be in the next MacFUSE release. >> >> >> > show up, the file system doesn't dismount on stopping the project and >> >> > I can't see any of the files in my directory :( >> >> >> Ok, these are a lot of problems at once. I'll wait until I hear if you >> >> got ytfs working as it is supposed to work first. >> >> >> > I am getting files from a web-service, have removed the ro option and >> >> > returning attribute dictionary for both root dir and files. But I >> >> >> Removing the "ro" option is not a good idea until >> >> >> > still don;t see anything in the root dir! And if I try to import >> >> > MacFUSE.h instead of GMUserFileSystem.h, I get an error "No such file >> >> > or directory" >> >> > I am using MacFUSE 1.7. I've included the MacFUSE.framework file in >> >> > the project but I don't see a MacFUSE.h in the headers! >> >> >> MacFUSE.h is not present in 1.7. It is new and should be present in >> >> the next release of MacFUSE. >> >> >> It sounds to me like maybe you have checked out the current >> >> development tree rather than a 1.5 or 1.7 tag, which will work better >> >> when working off one of the example Objective-C file systems. >> >> >> If you want to be forward-thinking in your work, then you can develop >> >> against (and help test) the developer releases. If so, then please >> >> read: >> >> >>http://code.google.com/p/macfuse/wiki/AUTOINSTALL >> >> >> ted >> >> >> > Please help! > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
