dunno much about (mac)fuse internals but maybe this general os-header can be of help:
/usr/include/sys/syslimits.h:83:#define NAME_MAX 255 /* max bytes in a file name */ /usr/include/sys/syslimits.h:91:#define PATH_MAX 1024 /* max bytes in pathname */ (there are other /usr/include/**limits.h as well) vike On Mon, Sep 20, 2010 at 9:17 PM, Jim <[email protected]> wrote: > At this location: > > http://code.google.com/p/macfuse/wiki/REFERENCE_FILE_SYSTEM > > appears the text: > > The subdir stacking module in conjunction with the subdir=/d module > option lets you limit loopback to a single directory. Normally, > loopback would actually remount the root file system. It's nicer and > cleaner to contain experimentation to one directory. Note that if you > conduct file system tests that involve long path names, the loopback > program will have to work with path names that are longer on the back- > end side: for example, if a call comes in to create a file /foo, > loopback will attempt to create /d/foo on the underlying file system. > Thus, the back-end will hit the path name length limit earlier than > the front-end. > > > From this I deduce that there is a max path length somewhere which may/ > will affect me, but searching for path length turns up very little. > What is this max path length, or where would I find any documentation > about it? > > > Thanks, > Jim > > -- > 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. > > -- 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.
