I'm going to set this up today and see if this item on my "to-do" list works:
Alas, it didn't work. I didn't use davfs2, but actually that's what encouraged me to try this today! After tinkering around the Lucid Lynx Ubuntu system I recently setup on my Lenovo G555 I noticed something that sounded familiar but hadn't actually seen before: .gvfs.
GVFS is the successor to the Gnome virtual file system. Thankfully, it doesn't need the usual hardware abstraction layer (HAL) and is apparently very modular, kind of like PAM. I happened upon the hidden .gvfs folder in my home directory while trying to clean it up, with a goal of putting all my settings in $XDGCONFIGHOME (aka ~/.config). Would I want to delete .gvfs? Turns out I definitely want to keep it -- in my humble opinion it is a very very cool little folder! Not so much for what it as a folder does, but for what it alerted me to - the brand new world of GVFS at large.
On my Lucid Lynx install, I have these gvfs related packages installed:
lash@lenovo-g555-2:~$ dpkg -l | grep gvfs ii gvfs 1.6.1-0ubuntu1build1 userspace virtual filesystem - server ii gvfs-backends 1.6.1-0ubuntu1build1 userspace virtual filesystem - backends ii gvfs-bin 1.6.1-0ubuntu1build1 userspace virtual filesystem - binaries ii gvfs-fuse 1.6.1-0ubuntu1build1 userspace virtual filesystem - fuse server ii libgvfscommon0
Get the idea? Good! I'll elaborate anyway! Docunext readers may be familiar with FUSE, I know I am - I've been using SSHFS to mount filesystems over the SSH protocol for years, though I've been using NFS more often these days. I still use FUSE all the time for Encfs, too.
Anyway, from what I've learned so far, gvfs is a set of tools, abstraction layers, and programming interfaces to provide tighter integration of FUSE, as well as other filesystem backends, with Gnome. While reading up on gvfs, I discovered that Thibault Saunier is working on a Google Docs interface to gvfs! Believe in the gDrive! The gPhone came true!!
This got me thinking and reminded me that I wanted to try connecting S3 to DAV with Apache2::S3. But as my test confirmed, that won't work at all:
[Sun Aug 22 18:07:02 2010] [error] [client 192.168.1.215] <?xml version="1.0" encoding="UTF-8"?>\n<Error><Code>MethodNotAllowed</Code><Message>The specified method is not allowed against this resource.</Message><ResourceType>BUCKET</ResourceType><Method>PROPFIND</Method><RequestId>B0DA9D7EE6DE73AD</RequestId><AllowedMethod>PUT</AllowedMethod><HostId>tIbZEhZarXoApiO9wzD23fLIrGiYqZ+DKhUxiFYXmG5frXO6faXdpOLgGEAx2Fwc</HostId></Error> at /usr/local/share/perl/5.10.1/Apache2/S3.pm line 153.\n
So, it looks like S3FS it the best bet, though that one definitely needs some more work, too.