> libtreefs was what I had in mind for the "fullsized" shm-translator.
> About libdiskfs, I'm not sure yet (read: I must read more sources yet).
> Basically, I don't need a filesystem-backend (say ext2, ufs, ...),
> just a tree (directory) structure to hold, say /servers/shm/0,
> /servers/shm/1, ... libdiskfs would be useful for a memory-based
> filesystem, which is not exactly what I have in mind. But again
> I'll have to read more about libdiskfs before.
I had the same thing in mind for each: libtreefs for the memory
based implementation and libdiskfs for your disk based implementation.
I do not think that libdiskfs would fit a memory based implementation at
all.
> Now I must first figure out how to use libtreefs/libdiskfs by
> writing a translator with dummy callbacks. If I get there, the
> rest will be much more easier.
It's always easier when you know how ;)
Best regards,
-Neal
--
Neal H Walfield
University of Massachusetts at Lowell
[EMAIL PROTECTED] or [EMAIL PROTECTED]
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd
