flickrfs-users Mailing List for Flickr Filesystem (Page 5)
Brought to you by:
manishrjain
Menu
▾
▴
flickrfs-users — Any questions, commends and suggestions regarding usage/development of flickrfs.
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(28) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(5) |
Feb
(22) |
Mar
|
Apr
(7) |
May
(11) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2007 |
Jan
(5) |
Feb
(8) |
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(4) |
Dec
|
| 2008 |
Jan
(21) |
Feb
(3) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
| 2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Manish R. J. <man...@gm...> - 2006-02-10 00:58:38
|
The way I do this is I have a test suite. I only check in code when the > test suite passes. Can you please upload the test suite to CVS. Manish |
|
From: Manish R. J. <man...@gm...> - 2006-02-10 00:55:56
|
On 2/9/06, rdm...@bi... <rdm...@bi...> wrote: > > On Thu, 9 Feb 2006 at 10:03, Manish Rai Jain wrote: > > On 2/9/06, rdm...@bi... <rdm...@bi...> wrote: > > Gr8 that you finished off the ctime/mtime functionality. And I think it > wd > > be more useful if ctime is 'time photo is taken' extracted from photos > Exif > > data. While utime wd be the time when photo is uploaded. > > If by 'utime' you mean what is in the code self.atime, then yes I > agree that makes maximum use of the available data. So > date_taken=3Dctime, last_update=3Dmtime, and date_uploaded=3Datime. > > >> If it's OK with you, Manish, I'd next like to do something that I > >> actually enjoy, though many programmers don't: refactoring. I can see > >> several places where the code could be tightened up and simplified, > >> now that you've roughed out how it all works. It will mean some fairl= y > >> radical changes to the code, but in the end I think it will be easier > >> to maintain and enhance (or I wouldn't suggest I do it!). > > > > Ok David. No probs with me, but I got some concerns. Lot of changes may > tend > > to break the code. To make sure that the changes can be tracked, and th= e > > code is still working, it wd be better to do all the changes followed b= y > > thorough testing locally, and then put it upstream in 1 go, instead of > doing > > cvs update after each small change. > > The way I do this is I have a test suite. I only check in code when the > test suite passes. The only problem is that my test suite doesn't > test 100% of the functionality. In particular I'm not currently testing > upload. So I guess I'd better figure out a way to do that. Come to > think of it I had ideas about that when I first started writing the tests > but had to give up because of some of the bugs I've now fixed, which > means I should be able to resurrect that test code... > > Anyway, the way I'd like to do this is to make incremental changes, > checking in as often as I can, where "I can" is defined as the full > test suite runs without error. Does that address your concerns? > (That methodology, by the way, is what I followed in doing the bug fixes, > although in that case I was making more and more of the tests pass with > each commit. But I always made sure nothing new broke before I did > a check-in.) Ok gr8. Go ahead. > Also, there are some functionalities and testing I wanted to complete: > > How about if I throw this list into a 'TODO' file in CVS? Presently > I'll take a look at tackling them. Thanks David. Fabio, I'd like you to take up one of the functionalities, an= d complete that. For now, photo resizing is the topmost priority. --David > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
|
From: <rdm...@bi...> - 2006-02-09 02:55:56
|
On Thu, 9 Feb 2006 at 10:03, Manish Rai Jain wrote: > On 2/9/06, rdm...@bi... <rdm...@bi...> wrote: > Gr8 that you finished off the ctime/mtime functionality. And I think it wd > be more useful if ctime is 'time photo is taken' extracted from photos Exif > data. While utime wd be the time when photo is uploaded. If by 'utime' you mean what is in the code self.atime, then yes I agree that makes maximum use of the available data. So date_taken=ctime, last_update=mtime, and date_uploaded=atime. >> If it's OK with you, Manish, I'd next like to do something that I >> actually enjoy, though many programmers don't: refactoring. I can see >> several places where the code could be tightened up and simplified, >> now that you've roughed out how it all works. It will mean some fairly >> radical changes to the code, but in the end I think it will be easier >> to maintain and enhance (or I wouldn't suggest I do it!). > > Ok David. No probs with me, but I got some concerns. Lot of changes may tend > to break the code. To make sure that the changes can be tracked, and the > code is still working, it wd be better to do all the changes followed by > thorough testing locally, and then put it upstream in 1 go, instead of doing > cvs update after each small change. The way I do this is I have a test suite. I only check in code when the test suite passes. The only problem is that my test suite doesn't test 100% of the functionality. In particular I'm not currently testing upload. So I guess I'd better figure out a way to do that. Come to think of it I had ideas about that when I first started writing the tests but had to give up because of some of the bugs I've now fixed, which means I should be able to resurrect that test code... Anyway, the way I'd like to do this is to make incremental changes, checking in as often as I can, where "I can" is defined as the full test suite runs without error. Does that address your concerns? (That methodology, by the way, is what I followed in doing the bug fixes, although in that case I was making more and more of the tests pass with each commit. But I always made sure nothing new broke before I did a check-in.) > Also, there are some functionalities and testing I wanted to complete: How about if I throw this list into a 'TODO' file in CVS? Presently I'll take a look at tackling them. --David |
|
From: Manish R. J. <man...@gm...> - 2006-02-09 02:03:11
|
On 2/9/06, rdm...@bi... <rdm...@bi...> wrote:
>
> I've checked in the bug fixes that have been talked about here, as well
> as my ctime/mtime enhancement. I've put comments in the README for
> each bugfix/enhancement. I'm not sure if the REAME is supposed to be
> the changelog or if I should create a changelog?
Gr8 that you finished off the ctime/mtime functionality. And I think it wd
be more useful if ctime is 'time photo is taken' extracted from photos Exif
data. While utime wd be the time when photo is uploaded.
If it's OK with you, Manish, I'd next like to do something that I
> actually enjoy, though many programmers don't: refactoring. I can see
> several places where the code could be tightened up and simplified,
> now that you've roughed out how it all works. It will mean some fairly
> radical changes to the code, but in the end I think it will be easier
> to maintain and enhance (or I wouldn't suggest I do it!).
Ok David. No probs with me, but I got some concerns. Lot of changes may ten=
d
to break the code. To make sure that the changes can be tracked, and the
code is still working, it wd be better to do all the changes followed by
thorough testing locally, and then put it upstream in 1 go, instead of doin=
g
cvs update after each small change.
Also, there are some functionalities and testing I wanted to complete:
1. Automatically resizing the photos to 800x600, 1024x728 etc. while
uploading. The user will specify which resolution the photos shd be
converted to through a 'settings.properties' file located in flickrfs Home
directory.
2. Meta data - I have tested the editing of metadata files through sed, vim=
,
and gedit. But more tests need to be done on other editors, for e.g. nano,
xemacs
3. Sync any changes done directly to flickr with flickrfs (while its still
mounted obv). This will mean flickrfs can automatically detect any new
photos uploaded to flickr (directly), and show them. Also means, that any
change in meta-data will be reflected as well. Though search results i.e.
tags/public or tags/personal need not be affected (or even synced).
It wd be best to do this using a command rather than a time bound
recurring thread. This wd prevent any inconsistencies.
I'd like someone to take these up, and remove the final obstacles to 'using
flickrfs'.
Manish
--
http://tuxmann.blogspot.com
"If I have seen further it is by standing on the shoulders of Giants"
"Software is like sex: it's better when it's free."
"An infinite number of monkeys typing into GNU emacs would never make a goo=
d
program."
|
|
From: <rdm...@bi...> - 2006-02-08 19:27:49
|
I've checked in the bug fixes that have been talked about here, as well as my ctime/mtime enhancement. I've put comments in the README for each bugfix/enhancement. I'm not sure if the REAME is supposed to be the changelog or if I should create a changelog? If it's OK with you, Manish, I'd next like to do something that I actually enjoy, though many programmers don't: refactoring. I can see several places where the code could be tightened up and simplified, now that you've roughed out how it all works. It will mean some fairly radical changes to the code, but in the end I think it will be easier to maintain and enhance (or I wouldn't suggest I do it!). --David |
|
From: <rdm...@bi...> - 2006-02-07 19:28:32
|
On Tue, 7 Feb 2006 at 10:31, Fabio Spelta wrote:
> Meanwhile, I'd like to ask about search for multiple tags in the "tags" folder.
> If I create a directory with a single tag, i.e. with
>
> /mount/point$ cd tags/personal
> /mount/point$ mkdir francesca
>
> that works fine, but if I try multiple tags with ":", I cant get any
> result neither with
>
> /mount/point$ mkdir francesca:io
> nor with
> /mount/point$ mkdir francesca\:io
>
> is that a bug or it's me that I'm missing something?
I'm not sure. I haven't gotten anything to work in 'personal' so far.
But I don't have any published photos. On the other hand, my test
program does:
mkdir('tags/public/radio:station:college')
which works fine and fetches three images.
--David
|
|
From: Manish R. J. <man...@gm...> - 2006-02-07 13:43:15
|
On 2/7/06, Fabio Spelta <sp...@gm...> wrote: > > > You're added. :) > > Lame, I discovered that... I don't use sourceforge from too much time, > and I'm not able to recover my pass in any way (lost my old email, > too). I opened a support request. > > Meanwhile, I'd like to ask about search for multiple tags in the "tags" > folder. > If I create a directory with a single tag, i.e. with > > /mount/point$ cd tags/personal > /mount/point$ mkdir francesca > > that works fine, but if I try multiple tags with ":", I cant get any > result neither with > > /mount/point$ mkdir francesca:io > nor with > /mount/point$ mkdir francesca\:io > > is that a bug or it's me that I'm missing something? My tests work fine with multiple tags. Btw, flickrfs won't allow to create directories anywhere. So, can only create directory in tags/personal or tags/public. Just to check if you did that while trying multiple tags. If you still can't find the prob, check the log. Everytime a new directory is created in 'tags/p*/', a new thread is started. log shd reveal that. Thank you very much, ciao > -- > Fabio > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
|
From: Fabio S. <sp...@gm...> - 2006-02-07 09:31:13
|
> You're added. :) Lame, I discovered that... I don't use sourceforge from too much time, and I'm not able to recover my pass in any way (lost my old email, too). I opened a support request. Meanwhile, I'd like to ask about search for multiple tags in the "tags" fol= der. If I create a directory with a single tag, i.e. with /mount/point$ cd tags/personal /mount/point$ mkdir francesca that works fine, but if I try multiple tags with ":", I cant get any result neither with /mount/point$ mkdir francesca:io nor with /mount/point$ mkdir francesca\:io is that a bug or it's me that I'm missing something? Thank you very much, ciao -- Fabio |
|
From: Fabio S. <sp...@gm...> - 2006-02-07 08:09:10
|
> > Please send me ur sourceforge usernames, if you wish to contribute to t= he > > code, and I will add you as developers. Thank you, my sourceforge username is 'febs'. I hope to contribute with more fixes than the previous one, although after that I can't see what else can be added. :-) Ciao -- Fabio |
|
From: <rdm...@bi...> - 2006-02-07 03:32:07
|
On Tue, 7 Feb 2006 at 11:09, Manish Rai Jain wrote: > Please send me ur sourceforge usernames, if you wish to contribute to the > code, and I will add you as developers. I'm 'bitdance'. Thanks! --David |
|
From: Manish R. J. <man...@gm...> - 2006-02-07 03:09:46
|
I have set up the CVS, and it shd be accessible within couple of hours for anonymous users. Please send me ur sourceforge usernames, if you wish to contribute to the code, and I will add you as developers. Regards Manish On 2/7/06, Manish Rai Jain <man...@gm...> wrote: > > Gr8 job! > I will set up a CVS now, and give you access to that. > > Manish > > > On 2/7/06, rdm...@bi... <rdm...@bi...> wrote: > > > > On Mon, 6 Feb 2006 at 17:03, Fabio Spelta wrote: > > > Well done! Me I've fixed a bug that makes flickrfs unusable for > > > international users. > > > > Any chance we could set up CVS and get multiple people with > > commit privs? > > > > --David > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > > _______________________________________________ > > Flickrfs-users mailing list > > Fli...@li... > > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > > > > > > -- > http://tuxmann.blogspot.com > > "If I have seen further it is by standing on the shoulders of Giants" > "Software is like sex: it's better when it's free." > "An infinite number of monkeys typing into GNU emacs would never make a > good program." -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
|
From: Manish R. J. <man...@gm...> - 2006-02-07 00:22:54
|
Gr8 job! I will set up a CVS now, and give you access to that. Manish On 2/7/06, rdm...@bi... <rdm...@bi...> wrote: > > On Mon, 6 Feb 2006 at 17:03, Fabio Spelta wrote: > > Well done! Me I've fixed a bug that makes flickrfs unusable for > > international users. > > Any chance we could set up CVS and get multiple people with > commit privs? > > --David > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
|
From: <rdm...@bi...> - 2006-02-06 16:46:19
|
On Mon, 6 Feb 2006 at 17:03, Fabio Spelta wrote: > Well done! Me I've fixed a bug that makes flickrfs unusable for > international users. Any chance we could set up CVS and get multiple people with commit privs? --David |
|
From: Fabio S. <sp...@gm...> - 2006-02-06 16:03:45
|
Well done! Me I've fixed a bug that makes flickrfs unusable for
international users.
Add this line:
import codecs
...after the other "imports".
Then change line 393 (which will become line 394 after that insertion!) fro=
m
f =3D open(os.path.join(flickrfsHome, '.'+id), 'w')
to
f =3D codecs.open(os.path.join(flickrfsHome, '.'+id), 'w', 'latin-1')
also, please insert just after line 564 (definition of the
"_mkfileOrDir" function) this one:
pth =3D pth.encode('latin-1')
Once these changes are apported, flickrfs will not break anymore when
it finds characters like these: =E0=E8=EC=F2=F9, often found in tags, names=
,
descriptions etc. of users of non-english languages, like me.
Time for a bugfix release? :-D
--
Fabio
|
|
From: <rdm...@bi...> - 2006-02-06 12:46:14
|
Found the fix for the exception-at-startup bug that is in
the bug tracker. Change line 446 from
retinfo = fapi.returntestFailure(rsp)
to
retinfo = fapi.returntestFailure(photos)
This led me to figuring out why I wasn't seeing the contents
of my set. The fix for _that_ is to change line 441 from
photos = fapi.photosets_getPhotos(api_key=flickrAPIKey, photoset_id=set_id)
to
photos = fapi.photosets_getPhotos(api_key=flickrAPIKey, photoset_id=set_id, auth_token=token)
--David
|
|
From: <rdm...@bi...> - 2006-02-06 02:26:43
|
Well, I finally got some time to play with the code enough to figure out may way around at least parts of it. I've got my first small enhancement to contribute. The included diff uses the photo upload time as the 'ctime' and the photo last update time as the 'mtime'. That way you can sort a directory listing by time the way you'd see it on the flickr web page. I've only applied this to the public tags directory at this point, but that's the place it's most likely to be useful. What's the best way to submit contributions? --David |
|
From: <rdm...@bi...> - 2006-01-30 14:48:47
|
On Mon, 30 Jan 2006 at 12:44, Manish Rai Jain wrote: > Do let me know if you get into any probs. Well, I have some questions. I created a flickr account to run these tests with, and uploaded a some photos. Now, I understand that these won't show up when I do a public tag search, but I thought they'd show up when I did it in personal (mkdir tags/personal/mytesttag). But nothing showed up. When I do the search on the flickr web interface they show up when I search from within my personal pictures but not when I do it from the public tags search, which is what I expected. Am I doing something wrong, or misunderstanding what the 'personal' subfolder of tags is for? In a similar fashion, once I unmounted and remounted my flickrfs, I no longer see the contents of my picture set (thought the set name itself is still there), nor do I see any photos in my 'stream' directory, even though I can see them in the flickr interface. All the photos are marked private at the moment, in case that matters. If I create a directory in tags/public for some preexisting tag, I get the photos for that tag, so I know it's not that my installation of flickrfs is borked. If these are bugs I'll work on tracking them down, but I thought I ought to check to make sure this isn't expected behavior or something I'm doing wrong... --David |
|
From: Manish R. J. <man...@gm...> - 2006-01-30 04:44:09
|
k great :). Do let me know if you get into any probs. Manish On 1/30/06, rdm...@bi... <rdm...@bi...> wrote: > On Mon, 30 Jan 2006 at 08:26, Manish Rai Jain wrote: > > Am currently busy with lot of projects going on in my university. If so= meone > > wd like to contribute to flickrfs code, it wd be great. > > Actually, I'm interested in doing that :) > > I've been playing with it, and getting a feel for how flickr works (I'd > never used flickr before encountering flickrfs). I'm currently writing > a little test program that exercises it, so that when I start making > changes to the code I'll have something to test against. > > --David (aka bitdancer) > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a good program." |
|
From: <rdm...@bi...> - 2006-01-30 00:59:04
|
On Mon, 30 Jan 2006 at 08:26, Manish Rai Jain wrote: > Am currently busy with lot of projects going on in my university. If someone > wd like to contribute to flickrfs code, it wd be great. Actually, I'm interested in doing that :) I've been playing with it, and getting a feel for how flickr works (I'd never used flickr before encountering flickrfs). I'm currently writing a little test program that exercises it, so that when I start making changes to the code I'll have something to test against. --David (aka bitdancer) |
|
From: Manish R. J. <man...@gm...> - 2006-01-30 00:26:22
|
Hi Fabio and all Am currently busy with lot of projects going on in my university. If someon= e wd like to contribute to flickrfs code, it wd be great. Regards Manish On 1/30/06, Fabio Spelta <sp...@gm...> wrote: > > Hello, how are things going with flickrfs? > Waiting for bugfixes and more feats! :-) > -- > Fabio > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
|
From: Fabio S. <sp...@gm...> - 2006-01-29 21:44:34
|
Hello, how are things going with flickrfs? Waiting for bugfixes and more feats! :-) -- Fabio |
|
From: Manish R. J. <man...@gm...> - 2005-11-30 08:37:48
|
And this step? [Also, copy over libfuse.so.2 (from /usr/local/lib) to /usr/lib. In case yo= u can't find it at /usr/local/lib, then can do an 'slocate libfuse.so.2'.] Actually, the problem lies with fuse configuration, so probably if even thi= s step is fine, then you may want to post to fuse-mailing list regarding this issue. Manish On 11/30/05, Geoffrey <geo...@le...> wrote: > > Yes - > > [root@Arial fuse-2.4.1]# ls -al /dev/fuse > crw-rw-rw- 1 root root 10, 229 Nov 8 13:00 /dev/fuse > > No joy. > > Manish Rai Jain wrote: > > Did you try out checking if normal user has enuf write permissions on > /dev/fuse, also if that is a character device. > $ ls -l /dev/fuse > crw-rw-rw- 1 root root 10, 229 Nov 16 04:21 /dev/fuse > > Manish > > > On 11/29/05, Geoffrey <geo...@le...> wrote: > > > > I'm still getting the "fuse: reading device: Bad file descriptor" > > error. I have su'd, done a make install, and checked /dev/fuse as per > > the install instructions & FAQ, but still get reams of 'bad file > > descriptor' errors. Session transcript (Fedora Core 2, Fuse v 2.4.1, > > Flickrfs v1.1.9) below. > > > > [geoffrey@Arial flickrfs-1.1.9]$ su - > > Password: > > [root@Arial root]# cd /home/geoffrey/fuse-2.4.1 > > [root@Arial fuse-2.4.1]# make install > > Making install in kernel > > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/kernel' > > make -C /lib/modules/2.6.10-1.12_FC2smp/build > > SUBDIRS=3D/home/geoffrey/fuse-2.4.1/kernel modules > > make[2]: Entering directory `/lib/modules/2.6.10-1.12_FC2smp/build' > > Building modules, stage 2. > > MODPOST > > make[2]: Leaving directory `/lib/modules/2.6.10-1.12_FC2smp/build' > > mkdir -p /lib/modules/2.6.10-1.12_FC2smp/kernel/fs/fuse > > /usr/bin/install -c -m 644 fuse.ko > > /lib/modules/2.6.10-1.12_FC2smp/kernel/fs/fuse/fuse.ko > > /sbin/depmod -a > > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/kernel' > > Making install in include > > make[1]: Entering directory `/home/geoffrey/fuse- 2.4.1/include' > > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/include' > > make[2]: Nothing to be done for `install-exec-am'. > > test -z "/usr/local/include/fuse" || mkdir -p -- > > "/usr/local/include/fuse" > > /usr/bin/install -c -m 644 'fuse.h' '/usr/local/include/fuse/fuse.h' > > /usr/bin/install -c -m 644 'fuse_compat.h' > > '/usr/local/include/fuse/fuse_compat.h' > > /usr/bin/install -c -m 644 'fuse_common.h' > > '/usr/local/include/fuse/fuse_common.h' > > /usr/bin/install -c -m 644 'fuse_lowlevel.h' > > '/usr/local/include/fuse/fuse_lowlevel.h' > > test -z "/usr/local/include" || mkdir -p -- "/usr/local/include" > > /usr/bin/install -c -m 644 'old/fuse.h' '/usr/local/include/fuse.h' > > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/include' > > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/include' > > Making install in lib > > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/lib' > > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/lib' > > test -z "/usr/local/lib" || mkdir -p -- "/usr/local/lib" > > /bin/sh ../libtool --mode=3Dinstall /usr/bin/install -c ' libfuse.la' > > '/usr/local/lib/libfuse.la' > > /usr/bin/install -c .libs/libfuse.so.2.4.1 > > /usr/local/lib/libfuse.so.2.4.1 > > (cd /usr/local/lib && rm -f libfuse.so.2 && ln -s libfuse.so.2.4.1 > > libfuse.so.2 ) > > (cd /usr/local/lib && rm -f libfuse.so && ln -s libfuse.so.2.4.1 > > libfuse.so) > > /usr/bin/install -c .libs/libfuse.lai /usr/local/lib/libfuse.la > > /usr/bin/install -c .libs/libfuse.a /usr/local/lib/libfuse.a > > ranlib /usr/local/lib/libfuse.a > > chmod 644 /usr/local/lib/libfuse.a > > PATH=3D"$PATH:/sbin" ldconfig -n /usr/local/lib > > ---------------------------------------------------------------------- > > Libraries have been installed in: > > /usr/local/lib > > > > If you ever happen to want to link against installed libraries > > in a given directory, LIBDIR, you must either use libtool, and > > specify the full pathname of the library, or use the `-LLIBDIR' > > flag during linking and do at least one of the following: > > - add LIBDIR to the `LD_LIBRARY_PATH' environment variable > > during execution > > - add LIBDIR to the `LD_RUN_PATH' environment variable > > during linking > > - use the `-Wl,--rpath -Wl,LIBDIR' linker flag > > - have your system administrator add LIBDIR to `/etc/ld.so.conf' > > > > See any operating system documentation about shared libraries for > > more information, such as the ld(1) and ld.so(8) manual pages. > > ---------------------------------------------------------------------- > > make[2]: Nothing to be done for `install-data-am'. > > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/lib' > > make[1]: Leaving directory `/home/geoffrey/fuse- 2.4.1/lib' > > Making install in util > > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/util' > > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/util' > > test -z "/usr/local/bin" || mkdir -p -- "/usr/local/bin" > > /bin/sh ../libtool --mode=3Dinstall /usr/bin/install -c 'fusermount' > > '/usr/local/bin/fusermount' > > /usr/bin/install -c fusermount /usr/local/bin/fusermount > > mkdir -p -- /sbin > > /usr/bin/install -c ./mount.fuse /sbin/mount.fuse > > make install-exec-hook > > make[3]: Entering directory `/home/geoffrey/fuse-2.4.1/util' > > chown root /usr/local/bin/fusermount > > chmod u+s /usr/local/bin/fusermount > > make[3]: Leaving directory `/home/geoffrey/fuse- 2.4.1/util' > > mkdir -p -- /etc/udev/rules.d > > /usr/bin/install -c -m 644 ./udev.rules /etc/udev/rules.d/40-fuse.rules > > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/util' > > make[1]: Leaving directory `/home/geoffrey/fuse- 2.4.1/util' > > Making install in example > > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/example' > > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/example' > > make[2]: Nothing to be done for `install-exec-am'. > > make[2]: Nothing to be done for `install-data-am'. > > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/example' > > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/example' > > make[1]: Entering directory `/home/geoffrey/fuse- 2.4.1' > > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1' > > make[2]: Nothing to be done for `install-exec-am'. > > test -z "/usr/local/lib/pkgconfig" || mkdir -p -- > > "/usr/local/lib/pkgconfig" > > /usr/bin/install -c -m 644 'fuse.pc' '/usr/local/lib/pkgconfig/fuse.pc' > > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1' > > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1' > > [root@Arial fuse-2.4.1]# ls -al /dev/fuse > > crw-rw-rw- 1 root root 10, 229 Nov 8 13:00 /dev/fuse > > [root@Arial fuse-2.4.1]# cd ../flickrfs-1.1.9 > > [root@Arial flickrfs-1.1.9]# ./flickrfs.py /mnt/flickrfs > > fuse: reading device: Bad file descriptor > > fuse: reading device: Bad file descriptor > > <and so on until KILLed> > > [root@Arial flickrfs-1.1.9]# logout > > [geoffrey@Arial flickrfs-1.1.9]$ ./flickrfs.py /mnt/flickrfs > > fuse: reading device: Bad file descriptor > > <snip - lots> > > fuse: reading device: Bad file descriptor > > fuse: reading device: BKilled > > [geoffrey@Arial flickrfs-1.1.9]$ tail ~/.flickrfs/log > > 11/29/05 19:00:16 DEBUG Got cached inode: /tags > > 11/29/05 19:00:16 INFO sets_thread: started > > 11/29/05 19:00:16 DEBUG parentDir:/: > > 11/29/05 19:00:16 DEBUG Creating directory:/sets > > 11/29/05 19:00:16 DEBUG Got cached inode: / > > 11/29/05 19:00:17 DEBUG parentDir:/sets: > > 11/29/05 19:00:17 DEBUG Creating directory:/sets/Family > > 11/29/05 19:00:17 DEBUG Got cached inode: /sets > > 11/29/05 19:00:22 DEBUG parentDir:/sets/Family: > > 11/29/05 19:00:22 DEBUG Creating file:/sets/Family/Wanggoolba Cree= k > > 05.jpg:with id:68237338 > > [geoffrey@Arial flickrfs-1.1.9]$ > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > > _______________________________________________ > > Flickrfs-users mailing list > > Fli...@li... > > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > > > > > > -- > http://tuxmann.blogspot.com > > "If I have seen further it is by standing on the shoulders of Giants" > "Software is like sex: it's better when it's free." > "An infinite number of monkeys typing into GNU emacs would never make a > good program." > > > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
|
From: Geoffrey <geo...@le...> - 2005-11-29 23:09:20
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Yes - <br>
<br>
[root@Arial fuse-2.4.1]# ls -al /dev/fuse
<br>
crw-rw-rw- 1 root root 10, 229 Nov 8 13:00 /dev/fuse<br>
<br>
No joy.<br>
<br>
Manish Rai Jain wrote:
<blockquote
cite="mid...@ma..."
type="cite">Did you try out checking if normal user has enuf write
permissions on /dev/fuse, also if that is a character device. <br>
$ ls -l /dev/fuse<br>
crw-rw-rw- 1 root root 10, 229 Nov 16 04:21 /dev/fuse<br>
<br>
Manish<br>
<br>
<br>
<div><span class="gmail_quote">On 11/29/05, <b
class="gmail_sendername">Geoffrey</b> <<a
href="mailto:geo...@le...">geo...@le...</a>>
wrote:</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm
still getting the "fuse: reading device: Bad file descriptor"<br>
error. I have su'd, done a make install, and checked /dev/fuse as per<br>
the install instructions & FAQ, but still get reams of 'bad file
<br>
descriptor' errors. Session transcript (Fedora Core 2, Fuse v 2.4.1,<br>
Flickrfs v1.1.9) below.<br>
<br>
[geoffrey@Arial flickrfs-1.1.9]$ su -<br>
Password:<br>
[root@Arial root]# cd /home/geoffrey/fuse-2.4.1<br>
[root@Arial fuse-2.4.1]# make install<br>
Making install in kernel<br>
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/kernel'<br>
make -C /lib/modules/2.6.10-1.12_FC2smp/build<br>
SUBDIRS=/home/geoffrey/fuse-2.4.1/kernel modules
<br>
make[2]: Entering directory `/lib/modules/2.6.10-1.12_FC2smp/build'<br>
Building modules, stage 2.<br>
MODPOST<br>
make[2]: Leaving directory `/lib/modules/2.6.10-1.12_FC2smp/build'<br>
mkdir -p /lib/modules/2.6.10-1.12_FC2smp/kernel/fs/fuse
<br>
/usr/bin/install -c -m 644 fuse.ko<br>
/lib/modules/2.6.10-1.12_FC2smp/kernel/fs/fuse/fuse.ko<br>
/sbin/depmod -a<br>
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/kernel'<br>
Making install in include<br>
make[1]: Entering directory `/home/geoffrey/fuse-
2.4.1/include'<br>
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/include'<br>
make[2]: Nothing to be done for `install-exec-am'.<br>
test -z "/usr/local/include/fuse" || mkdir -p --
"/usr/local/include/fuse"
<br>
/usr/bin/install -c -m 644 'fuse.h' '/usr/local/include/fuse/fuse.h'<br>
/usr/bin/install -c -m 644 'fuse_compat.h'<br>
'/usr/local/include/fuse/fuse_compat.h'<br>
/usr/bin/install -c -m 644 'fuse_common.h'<br>
'/usr/local/include/fuse/fuse_common.h'
<br>
/usr/bin/install -c -m 644 'fuse_lowlevel.h'<br>
'/usr/local/include/fuse/fuse_lowlevel.h'<br>
test -z "/usr/local/include" || mkdir -p -- "/usr/local/include"<br>
/usr/bin/install -c -m 644 'old/fuse.h' '/usr/local/include/fuse.h'
<br>
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/include'<br>
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/include'<br>
Making install in lib<br>
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/lib'<br>
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/lib'<br>
test -z "/usr/local/lib" || mkdir -p -- "/usr/local/lib"<br>
/bin/sh ../libtool --mode=install /usr/bin/install -c '<a
href="http://libfuse.la">
libfuse.la</a>'<br>
'/usr/local/lib/libfuse.la'<br>
/usr/bin/install -c .libs/libfuse.so.2.4.1
/usr/local/lib/libfuse.so.2.4.1<br>
(cd /usr/local/lib && rm -f libfuse.so.2 && ln -s
libfuse.so.2.4.1<br>
libfuse.so.2
)<br>
(cd /usr/local/lib && rm -f libfuse.so && ln -s
libfuse.so.2.4.1 libfuse.so)<br>
/usr/bin/install -c .libs/libfuse.lai /usr/local/lib/libfuse.la<br>
/usr/bin/install -c .libs/libfuse.a /usr/local/lib/libfuse.a
<br>
ranlib /usr/local/lib/libfuse.a<br>
chmod 644 /usr/local/lib/libfuse.a<br>
PATH="$PATH:/sbin" ldconfig -n /usr/local/lib<br>
----------------------------------------------------------------------<br>
Libraries have been installed in:
<br>
/usr/local/lib<br>
<br>
If you ever happen to want to link against installed libraries<br>
in a given directory, LIBDIR, you must either use libtool, and<br>
specify the full pathname of the library, or use the `-LLIBDIR'
<br>
flag during linking and do at least one of the following:<br>
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable<br>
during execution<br>
- add LIBDIR to the `LD_RUN_PATH' environment variable<br>
during linking
<br>
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag<br>
- have your system administrator add LIBDIR to `/etc/ld.so.conf'<br>
<br>
See any operating system documentation about shared libraries for<br>
more information, such as the ld(1) and ld.so(8) manual pages.<br>
----------------------------------------------------------------------<br>
make[2]: Nothing to be done for `install-data-am'.<br>
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/lib'<br>
make[1]: Leaving directory `/home/geoffrey/fuse-
2.4.1/lib'<br>
Making install in util<br>
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/util'<br>
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/util'<br>
test -z "/usr/local/bin" || mkdir -p -- "/usr/local/bin"
<br>
/bin/sh ../libtool --mode=install /usr/bin/install -c 'fusermount'<br>
'/usr/local/bin/fusermount'<br>
/usr/bin/install -c fusermount /usr/local/bin/fusermount<br>
mkdir -p -- /sbin<br>
/usr/bin/install -c ./mount.fuse /sbin/mount.fuse
<br>
make install-exec-hook<br>
make[3]: Entering directory `/home/geoffrey/fuse-2.4.1/util'<br>
chown root /usr/local/bin/fusermount<br>
chmod u+s /usr/local/bin/fusermount<br>
make[3]: Leaving directory `/home/geoffrey/fuse-
2.4.1/util'<br>
mkdir -p -- /etc/udev/rules.d<br>
/usr/bin/install -c -m 644 ./udev.rules /etc/udev/rules.d/40-fuse.rules<br>
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/util'<br>
make[1]: Leaving directory `/home/geoffrey/fuse-
2.4.1/util'<br>
Making install in example<br>
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/example'<br>
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/example'<br>
make[2]: Nothing to be done for `install-exec-am'.
<br>
make[2]: Nothing to be done for `install-data-am'.<br>
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/example'<br>
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/example'<br>
make[1]: Entering directory `/home/geoffrey/fuse-
2.4.1'<br>
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1'<br>
make[2]: Nothing to be done for `install-exec-am'.<br>
test -z "/usr/local/lib/pkgconfig" || mkdir -p --
"/usr/local/lib/pkgconfig"<br>
/usr/bin/install -c -m 644 'fuse.pc' '/usr/local/lib/pkgconfig/fuse.pc'<br>
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1'<br>
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1'<br>
[root@Arial fuse-2.4.1]# ls -al /dev/fuse
<br>
crw-rw-rw- 1 root root 10, 229 Nov 8 13:00 /dev/fuse<br>
[root@Arial fuse-2.4.1]# cd ../flickrfs-1.1.9<br>
[root@Arial flickrfs-1.1.9]# ./flickrfs.py /mnt/flickrfs<br>
fuse: reading device: Bad file descriptor<br>
fuse: reading device: Bad file descriptor
<br>
<and so on until KILLed><br>
[root@Arial flickrfs-1.1.9]# logout<br>
[geoffrey@Arial flickrfs-1.1.9]$ ./flickrfs.py /mnt/flickrfs<br>
fuse: reading device: Bad file descriptor<br>
<snip - lots><br>
fuse: reading device: Bad file descriptor
<br>
fuse: reading device: BKilled<br>
[geoffrey@Arial flickrfs-1.1.9]$ tail ~/.flickrfs/log<br>
11/29/05 19:00:16 DEBUG Got cached inode: /tags<br>
11/29/05 19:00:16 INFO sets_thread: started<br>
11/29/05 19:00:16 DEBUG parentDir:/:
<br>
11/29/05 19:00:16 DEBUG Creating directory:/sets<br>
11/29/05 19:00:16 DEBUG Got cached inode: /<br>
11/29/05 19:00:17 DEBUG parentDir:/sets:<br>
11/29/05 19:00:17 DEBUG Creating directory:/sets/Family
<br>
11/29/05 19:00:17 DEBUG Got cached inode: /sets<br>
11/29/05 19:00:22 DEBUG parentDir:/sets/Family:<br>
11/29/05 19:00:22 DEBUG Creating <a class="moz-txt-link-freetext" href="file:/sets/Family/Wanggoolba">file:/sets/Family/Wanggoolba</a> Creek<br>
05.jpg:with id:68237338<br>
[geoffrey@Arial flickrfs-1.1.9]$<br>
<br>
<br>
-------------------------------------------------------<br>
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files<br>
for problems? Stop! Download the new AJAX search engine that makes
<br>
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!<br>
<a href="http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click">http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click</a><br>
_______________________________________________<br>
Flickrfs-users mailing list<br>
<a href="mailto:Fli...@li...">Fli...@li...</a><br>
<a
href="https://lists.sourceforge.net/lists/listinfo/flickrfs-users">https://lists.sourceforge.net/lists/listinfo/flickrfs-users</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<a href="http://tuxmann.blogspot.com">http://tuxmann.blogspot.com</a><br>
<br>
"If I have seen further it is by standing on the shoulders of Giants"
<br>
"Software is like sex: it's better when it's free."<br>
"An infinite number of monkeys typing into GNU emacs would never make a
good program."
</blockquote>
<br>
</body>
</html>
|
|
From: Manish R. J. <man...@gm...> - 2005-11-29 12:56:53
|
Did you try out checking if normal user has enuf write permissions on /dev/fuse, also if that is a character device. $ ls -l /dev/fuse crw-rw-rw- 1 root root 10, 229 Nov 16 04:21 /dev/fuse Manish On 11/29/05, Geoffrey <geo...@le...> wrote: > > I'm still getting the "fuse: reading device: Bad file descriptor" > error. I have su'd, done a make install, and checked /dev/fuse as per > the install instructions & FAQ, but still get reams of 'bad file > descriptor' errors. Session transcript (Fedora Core 2, Fuse v 2.4.1, > Flickrfs v1.1.9) below. > > [geoffrey@Arial flickrfs-1.1.9]$ su - > Password: > [root@Arial root]# cd /home/geoffrey/fuse-2.4.1 > [root@Arial fuse-2.4.1]# make install > Making install in kernel > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/kernel' > make -C /lib/modules/2.6.10-1.12_FC2smp/build > SUBDIRS=3D/home/geoffrey/fuse-2.4.1/kernel modules > make[2]: Entering directory `/lib/modules/2.6.10-1.12_FC2smp/build' > Building modules, stage 2. > MODPOST > make[2]: Leaving directory `/lib/modules/2.6.10-1.12_FC2smp/build' > mkdir -p /lib/modules/2.6.10-1.12_FC2smp/kernel/fs/fuse > /usr/bin/install -c -m 644 fuse.ko > /lib/modules/2.6.10-1.12_FC2smp/kernel/fs/fuse/fuse.ko > /sbin/depmod -a > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/kernel' > Making install in include > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/include' > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/include' > make[2]: Nothing to be done for `install-exec-am'. > test -z "/usr/local/include/fuse" || mkdir -p -- "/usr/local/include/fuse= " > /usr/bin/install -c -m 644 'fuse.h' '/usr/local/include/fuse/fuse.h' > /usr/bin/install -c -m 644 'fuse_compat.h' > '/usr/local/include/fuse/fuse_compat.h' > /usr/bin/install -c -m 644 'fuse_common.h' > '/usr/local/include/fuse/fuse_common.h' > /usr/bin/install -c -m 644 'fuse_lowlevel.h' > '/usr/local/include/fuse/fuse_lowlevel.h' > test -z "/usr/local/include" || mkdir -p -- "/usr/local/include" > /usr/bin/install -c -m 644 'old/fuse.h' '/usr/local/include/fuse.h' > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/include' > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/include' > Making install in lib > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/lib' > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/lib' > test -z "/usr/local/lib" || mkdir -p -- "/usr/local/lib" > /bin/sh ../libtool --mode=3Dinstall /usr/bin/install -c 'libfuse.la' > '/usr/local/lib/libfuse.la' > /usr/bin/install -c .libs/libfuse.so.2.4.1 /usr/local/lib/libfuse.so.2.4.= 1 > (cd /usr/local/lib && rm -f libfuse.so.2 && ln -s libfuse.so.2.4.1 > libfuse.so.2) > (cd /usr/local/lib && rm -f libfuse.so && ln -s libfuse.so.2.4.1 > libfuse.so) > /usr/bin/install -c .libs/libfuse.lai /usr/local/lib/libfuse.la > /usr/bin/install -c .libs/libfuse.a /usr/local/lib/libfuse.a > ranlib /usr/local/lib/libfuse.a > chmod 644 /usr/local/lib/libfuse.a > PATH=3D"$PATH:/sbin" ldconfig -n /usr/local/lib > ---------------------------------------------------------------------- > Libraries have been installed in: > /usr/local/lib > > If you ever happen to want to link against installed libraries > in a given directory, LIBDIR, you must either use libtool, and > specify the full pathname of the library, or use the `-LLIBDIR' > flag during linking and do at least one of the following: > - add LIBDIR to the `LD_LIBRARY_PATH' environment variable > during execution > - add LIBDIR to the `LD_RUN_PATH' environment variable > during linking > - use the `-Wl,--rpath -Wl,LIBDIR' linker flag > - have your system administrator add LIBDIR to `/etc/ld.so.conf' > > See any operating system documentation about shared libraries for > more information, such as the ld(1) and ld.so(8) manual pages. > ---------------------------------------------------------------------- > make[2]: Nothing to be done for `install-data-am'. > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/lib' > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/lib' > Making install in util > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/util' > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/util' > test -z "/usr/local/bin" || mkdir -p -- "/usr/local/bin" > /bin/sh ../libtool --mode=3Dinstall /usr/bin/install -c 'fusermount' > '/usr/local/bin/fusermount' > /usr/bin/install -c fusermount /usr/local/bin/fusermount > mkdir -p -- /sbin > /usr/bin/install -c ./mount.fuse /sbin/mount.fuse > make install-exec-hook > make[3]: Entering directory `/home/geoffrey/fuse-2.4.1/util' > chown root /usr/local/bin/fusermount > chmod u+s /usr/local/bin/fusermount > make[3]: Leaving directory `/home/geoffrey/fuse-2.4.1/util' > mkdir -p -- /etc/udev/rules.d > /usr/bin/install -c -m 644 ./udev.rules /etc/udev/rules.d/40-fuse.rules > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/util' > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/util' > Making install in example > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/example' > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/example' > make[2]: Nothing to be done for `install-exec-am'. > make[2]: Nothing to be done for `install-data-am'. > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/example' > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/example' > make[1]: Entering directory `/home/geoffrey/fuse-2.4.1' > make[2]: Entering directory `/home/geoffrey/fuse-2.4.1' > make[2]: Nothing to be done for `install-exec-am'. > test -z "/usr/local/lib/pkgconfig" || mkdir -p -- > "/usr/local/lib/pkgconfig" > /usr/bin/install -c -m 644 'fuse.pc' '/usr/local/lib/pkgconfig/fuse.pc' > make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1' > make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1' > [root@Arial fuse-2.4.1]# ls -al /dev/fuse > crw-rw-rw- 1 root root 10, 229 Nov 8 13:00 /dev/fuse > [root@Arial fuse-2.4.1]# cd ../flickrfs-1.1.9 > [root@Arial flickrfs-1.1.9]# ./flickrfs.py /mnt/flickrfs > fuse: reading device: Bad file descriptor > fuse: reading device: Bad file descriptor > <and so on until KILLed> > [root@Arial flickrfs-1.1.9]# logout > [geoffrey@Arial flickrfs-1.1.9]$ ./flickrfs.py /mnt/flickrfs > fuse: reading device: Bad file descriptor > <snip - lots> > fuse: reading device: Bad file descriptor > fuse: reading device: BKilled > [geoffrey@Arial flickrfs-1.1.9]$ tail ~/.flickrfs/log > 11/29/05 19:00:16 DEBUG Got cached inode: /tags > 11/29/05 19:00:16 INFO sets_thread: started > 11/29/05 19:00:16 DEBUG parentDir:/: > 11/29/05 19:00:16 DEBUG Creating directory:/sets > 11/29/05 19:00:16 DEBUG Got cached inode: / > 11/29/05 19:00:17 DEBUG parentDir:/sets: > 11/29/05 19:00:17 DEBUG Creating directory:/sets/Family > 11/29/05 19:00:17 DEBUG Got cached inode: /sets > 11/29/05 19:00:22 DEBUG parentDir:/sets/Family: > 11/29/05 19:00:22 DEBUG Creating file:/sets/Family/Wanggoolba Creek > 05.jpg:with id:68237338 > [geoffrey@Arial flickrfs-1.1.9]$ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
|
From: Geoffrey <geo...@le...> - 2005-11-29 11:08:26
|
I'm still getting the "fuse: reading device: Bad file descriptor"
error. I have su'd, done a make install, and checked /dev/fuse as per
the install instructions & FAQ, but still get reams of 'bad file
descriptor' errors. Session transcript (Fedora Core 2, Fuse v 2.4.1,
Flickrfs v1.1.9) below.
[geoffrey@Arial flickrfs-1.1.9]$ su -
Password:
[root@Arial root]# cd /home/geoffrey/fuse-2.4.1
[root@Arial fuse-2.4.1]# make install
Making install in kernel
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/kernel'
make -C /lib/modules/2.6.10-1.12_FC2smp/build
SUBDIRS=/home/geoffrey/fuse-2.4.1/kernel modules
make[2]: Entering directory `/lib/modules/2.6.10-1.12_FC2smp/build'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/lib/modules/2.6.10-1.12_FC2smp/build'
mkdir -p /lib/modules/2.6.10-1.12_FC2smp/kernel/fs/fuse
/usr/bin/install -c -m 644 fuse.ko
/lib/modules/2.6.10-1.12_FC2smp/kernel/fs/fuse/fuse.ko
/sbin/depmod -a
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/kernel'
Making install in include
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/include'
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/include'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/include/fuse" || mkdir -p -- "/usr/local/include/fuse"
/usr/bin/install -c -m 644 'fuse.h' '/usr/local/include/fuse/fuse.h'
/usr/bin/install -c -m 644 'fuse_compat.h'
'/usr/local/include/fuse/fuse_compat.h'
/usr/bin/install -c -m 644 'fuse_common.h'
'/usr/local/include/fuse/fuse_common.h'
/usr/bin/install -c -m 644 'fuse_lowlevel.h'
'/usr/local/include/fuse/fuse_lowlevel.h'
test -z "/usr/local/include" || mkdir -p -- "/usr/local/include"
/usr/bin/install -c -m 644 'old/fuse.h' '/usr/local/include/fuse.h'
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/include'
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/include'
Making install in lib
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/lib'
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/lib'
test -z "/usr/local/lib" || mkdir -p -- "/usr/local/lib"
/bin/sh ../libtool --mode=install /usr/bin/install -c 'libfuse.la'
'/usr/local/lib/libfuse.la'
/usr/bin/install -c .libs/libfuse.so.2.4.1 /usr/local/lib/libfuse.so.2.4.1
(cd /usr/local/lib && rm -f libfuse.so.2 && ln -s libfuse.so.2.4.1
libfuse.so.2)
(cd /usr/local/lib && rm -f libfuse.so && ln -s libfuse.so.2.4.1 libfuse.so)
/usr/bin/install -c .libs/libfuse.lai /usr/local/lib/libfuse.la
/usr/bin/install -c .libs/libfuse.a /usr/local/lib/libfuse.a
ranlib /usr/local/lib/libfuse.a
chmod 644 /usr/local/lib/libfuse.a
PATH="$PATH:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/lib'
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/lib'
Making install in util
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/util'
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/util'
test -z "/usr/local/bin" || mkdir -p -- "/usr/local/bin"
/bin/sh ../libtool --mode=install /usr/bin/install -c 'fusermount'
'/usr/local/bin/fusermount'
/usr/bin/install -c fusermount /usr/local/bin/fusermount
mkdir -p -- /sbin
/usr/bin/install -c ./mount.fuse /sbin/mount.fuse
make install-exec-hook
make[3]: Entering directory `/home/geoffrey/fuse-2.4.1/util'
chown root /usr/local/bin/fusermount
chmod u+s /usr/local/bin/fusermount
make[3]: Leaving directory `/home/geoffrey/fuse-2.4.1/util'
mkdir -p -- /etc/udev/rules.d
/usr/bin/install -c -m 644 ./udev.rules /etc/udev/rules.d/40-fuse.rules
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/util'
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/util'
Making install in example
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1/example'
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1/example'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1/example'
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1/example'
make[1]: Entering directory `/home/geoffrey/fuse-2.4.1'
make[2]: Entering directory `/home/geoffrey/fuse-2.4.1'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/lib/pkgconfig" || mkdir -p -- "/usr/local/lib/pkgconfig"
/usr/bin/install -c -m 644 'fuse.pc' '/usr/local/lib/pkgconfig/fuse.pc'
make[2]: Leaving directory `/home/geoffrey/fuse-2.4.1'
make[1]: Leaving directory `/home/geoffrey/fuse-2.4.1'
[root@Arial fuse-2.4.1]# ls -al /dev/fuse
crw-rw-rw- 1 root root 10, 229 Nov 8 13:00 /dev/fuse
[root@Arial fuse-2.4.1]# cd ../flickrfs-1.1.9
[root@Arial flickrfs-1.1.9]# ./flickrfs.py /mnt/flickrfs
fuse: reading device: Bad file descriptor
fuse: reading device: Bad file descriptor
<and so on until KILLed>
[root@Arial flickrfs-1.1.9]# logout
[geoffrey@Arial flickrfs-1.1.9]$ ./flickrfs.py /mnt/flickrfs
fuse: reading device: Bad file descriptor
<snip - lots>
fuse: reading device: Bad file descriptor
fuse: reading device: BKilled
[geoffrey@Arial flickrfs-1.1.9]$ tail ~/.flickrfs/log
11/29/05 19:00:16 DEBUG Got cached inode: /tags
11/29/05 19:00:16 INFO sets_thread: started
11/29/05 19:00:16 DEBUG parentDir:/:
11/29/05 19:00:16 DEBUG Creating directory:/sets
11/29/05 19:00:16 DEBUG Got cached inode: /
11/29/05 19:00:17 DEBUG parentDir:/sets:
11/29/05 19:00:17 DEBUG Creating directory:/sets/Family
11/29/05 19:00:17 DEBUG Got cached inode: /sets
11/29/05 19:00:22 DEBUG parentDir:/sets/Family:
11/29/05 19:00:22 DEBUG Creating file:/sets/Family/Wanggoolba Creek
05.jpg:with id:68237338
[geoffrey@Arial flickrfs-1.1.9]$
|
