Great,
At least we got some good analysis tools out of this.
Paul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Krzysztof
Sent: Friday, July 08, 2005 6:17 PM
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] Re: CVS
Krzysztof
Krzysztof wrote:
>> I can see we are running out of ideas, do not we?
>
> I'm talking to myself ;-)
>
again :-)
It turned out that fuse installer DID NOT update all librarys :/
and it was the cause...
/usr/lib
/usr/local/lib <- old librarys (30 april) where still there WHY!? :-)
I have moved "f
> I can see we are running out of ideas, do not we?
I'm talking to myself ;-)
But...
http://hannibal.lr-s.tudelft.nl/~vincent/fusesmb/ I have found that app
while browsing fuse project site.
And guess what, yes, it does NOT work too - mount point becomes red (I use
mc to browse file system) an
> Everything looks good so far...
>
Guess what... looks good but mount point is not accessible again...
> Try adding error_print=2 to the command to make sure everything is
> sent
> to the command line... Some debug-output might be in your syslog
> (/var/log/messages)..
>
> owfs --foreground --e
Hi Krzysiek,
On Fri, 2005-07-08 at 18:19, Krzysztof wrote:
> Christian Magnusson wrote:
> > Try the very latest owfs version in the cvs. I have added TONS of
> > debug messages right now, and if you start owfs with error_level 9
> > you should get much more details of what's going wrong.
> >
> >
You can ignore those warnings.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Krzysztof
Sent: Friday, July 08, 2005 12:20 PM
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] Re: CVS
I never know if a warning that appears is worth
Christian Magnusson wrote:
> Try the very latest owfs version in the cvs. I have added TONS of
> debug messages right now, and if you start owfs with error_level 9
> you should get much more details of what's going wrong.
>
> Also make sure fuse is not used by any old process and reload it.
I did
Try the very latest owfs version in the cvs. I have added TONS of
debug messages right now, and if you start owfs with error_level 9
you should get much more details of what's going wrong.
Also make sure fuse is not used by any old process and reload it.
>lsmod | grep fuse
fuse
Christian Magnusson wrote:
> You should probably try the latest cvs-version of fuse. That version
> works much better with mount-permissions.
>
> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/fuse login
> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/fuse -z3 co fuse
Did not help :-(
Any ideas? Maybe som
You should probably try the latest cvs-version of fuse. That version
works much better with mount-permissions.
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/fuse login
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/fuse -z3 co fuse
/Christian
On Fri, 2005-07-08 at 10:56 +0200, Krzysztof wrote:
> Christ
I have forgotten, maybe this will help?
[EMAIL PROTECTED]:/# cat /etc/mtab
/dev/hda1 / reiserfs rw 0 0
proc /proc proc rw 0 0
/dev/hda2 /usr/squid-cache reiserfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
none /proc/bus/usb usbdevfs rw 0 0
/tmp/.fuse_devKgmifY/fuse /mnt/1wire fuse
rw,nosu
Christian Magnusson wrote:
> You probably have problems with the fuse permissions. If you are
> using a new fuse-version there is a mount-flag called allow_other
> that you should try if other users than root should be able to access
> the directory.
I'am a root user, I use new fuse 2.3.0 and a CV
You probably have problems with the fuse permissions. If you are
using a new fuse-version there is a mount-flag called allow_other
that you should try if other users than root should be able to access
the directory.
owfs --fuse_opt="allow_other" -d /dev/ttyS0 /var/1wire/
[EMAIL PROTECTED] /var]#
13 matches
Mail list logo
