The list has been quiet recently. My main activity has been with NFS code.
The file handle <-> "parsed name" (the internal representation of a 1-wire path name) is done. The rare exception of very long paths with branching of the DS2409 is handled by a small lookup table. Long bus paths will have to be handled the same way. Most of the functions are implemented: NULL, SETATTR, ACCESS, READLINK, CREATE, MKDIR, SYMLINK, MKNOD, REMOVE, RMDIR, RENAME, LINK COMMIT are essentially null ops. READ, WRITE are implemented. READDIR and READDIRPLUS are in progress. They are a little difficult because the 1-wire bus is dynamic, and possibly long. All the other wrappers send back the entire directory, either one element at a time or as one long string. NFS polls for groups of entries. My solution is to fill the requesting buffer (which I suspect will normally be enough), and behave differently depending on the type of directory requested. property directories are unchanging in-memory (eg: 21.xxxx/log/temperature.nnnn) and will return the same each time. Device directories will have to be stored in RAM. I'll store just one. My hope is that this will bring fuse-like function to BSD, Mac OSX and Windows. Paul ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
