I’m sure someone has created a “dropboxfs” that provides an ext3/4 interface to your dropbox files so that you don’t have to use dropbox’s official clients. Just after gmail started up there was something like “gmailfs” that allowed you to abuse an email account by storing the contents of a filesystem in it. That is basically the same concept, but instead of a natural 1 to 1 mapping you would have a single 100MB file stored over 4 or 5 emails for example.
ext3/4 is a particular filesystem, not an interface. This is really about providing something that supports an endpoint that already exists in the kernel, which nfs and smb do (usually). gmailfs was built on fuse (there exists ssh, and s3 variations as well), which this article points out as an attempt and they decided it didn’t really work for them.
Reading this I got the idea to implement ab SMB or NFS gateway (run locally) that exposes Dropbox through. I wonder if that would work…
The reason I want it is because I wouldn’t be limited to whatever kernel’s the Dropbox team wants to support. All OS’s I use support NFS or Samba.
I’m sure someone has created a “dropboxfs” that provides an ext3/4 interface to your dropbox files so that you don’t have to use dropbox’s official clients. Just after gmail started up there was something like “gmailfs” that allowed you to abuse an email account by storing the contents of a filesystem in it. That is basically the same concept, but instead of a natural 1 to 1 mapping you would have a single 100MB file stored over 4 or 5 emails for example.
ext3/4 is a particular filesystem, not an interface. This is really about providing something that supports an endpoint that already exists in the kernel, which nfs and smb do (usually). gmailfs was built on fuse (there exists ssh, and s3 variations as well), which this article points out as an attempt and they decided it didn’t really work for them.
not a bad idea