Welcome to Linux Screw! If you're new here, you may want to subscribe our RSS feed.
Flickr is an extremely popular image/video hosting website, web services suite and an online community platform. It was one of the earliest Web 2.0 applications. In addition to being a popular Web site for users to share personal photographs, the service is widely used by bloggers as a photo repository. It hosts more than two billion images.
Now it is possible to mount your Flickr account on Linux PC as a virtual filesystem, allowing you to browse through your photos as if they were on a locally connected drive. It can be now easily done with Flickrfs:
Once mounted, it retrieves information about your photos hosted on your flickr account, and shows them as files. You can now easily copy photos from your local machine to this mount, and it will automatically upload them to your flickr account. Similary, you can copy the files from your mount to your local machine, and it will download your images from flickr.
All the files in the mount have a meta file attached to them, which provides access to title, description, tags, and license information. Modifying any of these fields and saving the meta file, will update them on the server as well.
You are lucky if you chose Ubuntu as detailed step-by-step installation guide is available at author’s site for Ubuntu users. Of course you are welcome to use it under other Linux distributions e.g. Slackware ![]()

i get the following when trying to run the program:
david@holly:~$ python flickrfs-1.3.9/flickrfs.py
Traceback (most recent call last):
File “flickrfs-1.3.9/flickrfs.py”, line 1079, in
server = Flickrfs()
File “flickrfs-1.3.9/flickrfs.py”, line 157, in __init__
Fuse.__init__(self, *args, **kw)
File “/usr/lib/python2.5/site-packages/fuse.py”, line 652, in __init__
“”"
RuntimeError: fuse.fuse_python_api not defined.
! Please define fuse.fuse_python_api internally (eg.
!
! (1) fuse.fuse_python_api = (0, 2)
!
! ) or in the enviroment (eg.
!
! (2) FUSE_PYTHON_API=0.1
!
! ).
!
! If you are actually developing a filesystem, probably (1) is the way to go.
! If you are using a filesystem written before 2007 Q2, probably (2) is what
! you want.”
Any ideas on what to do from here?