[mela@neudarkover ~/bin/flickrfs]$ python flickrfs/flickrfs.py
Traceback (most recent call last):
File "flickrfs/flickrfs.py", line 1083, in ?
server = Flickrfs()
File "flickrfs/flickrfs.py", line 159, in __init__
log.info("flickrfs.py:Flickrfs:mountpoint: %s" % repr(self.mountpoint))
File "/usr/local/lib/python2.4/site-packages/fuse.py", line 711, in __getattr__
raise AttributeError, "Fuse instance has no attribute '%s'" % meth
AttributeError: Fuse instance has no attribute 'mountpoint'
[mela@neudarkover ~/bin/flickrfs]$ uname -a
FreeBSD neudarkover.home 6.2-STABLE FreeBSD 6.2-STABLE #9: Tue May 22 20:54:52 CEST 2007 root@neudarkover.home:/usr/obj/usr/src/sys/DARKOVER i386
[mela@neudarkover ~/bin/flickrfs]$ python -V
Python 2.4.4
Logged In: YES
user_id=1342181
Originator: NO
The problem seems to be exactly what the stack trace is pointing at. You need to provide a mount point, a directory where flickrfs would populate the photos.
$ python flickrfs/flickrfs.py ~/mnt/flickrfs
Logged In: YES
user_id=84642
Originator: YES
I'm sorry, messed up my posting.
[mela@neudarkover ~/bin/flickrfs]$ sudo python flickrfs/flickrfs.py /flickr
Password:
Traceback (most recent call last):
File "flickrfs/flickrfs.py", line 1083, in ?
server = Flickrfs()
File "flickrfs/flickrfs.py", line 159, in __init__
log.info("flickrfs.py:Flickrfs:mountpoint: %s" % repr(self.mountpoint))
File "/usr/local/lib/python2.4/site-packages/fuse.py", line 711, in __getattr__
raise AttributeError, "Fuse instance has no attribute '%s'" % meth
AttributeError: Fuse instance has no attribute 'mountpoint'
[mela@neudarkover ~/bin/flickrfs]$ ls -ld /flickr
drwxr-xr-x 2 root wheel 512 Jun 21 03:30 /flickr
Logged In: YES
user_id=287697
Originator: NO
But they did provide a mount point: "/flickr"
Anyway, they're not the only one with this problem. This is a duplicate of 1504522 and 1508208, with 1508208 holding a pseudo-patch that should fix this.
Logged In: YES
user_id=287697
Originator: NO
I was a wee bit too quick there. This is indeed a duplicate report of 1504522, but 1508208 is something else entirely. Sorry about that. The problem does seem to have been located in 1504522 though, including a work around.
Logged In: YES
user_id=1445114
Originator: NO
This bug is fixed in CVS as of 1/27/2008 and will be in the next release. In the meantime you may be able to get it to work by downgrading your fuse-python to 0.1.