On Tuesday 18 October 2005 10:37 am, Geo Carncross wrote:
> I should clarify, that providing a common API to the language bindings
> isn't bad, but requiring that they use them is- that is, having other
> parts of OW use the same mutexes and locks and whathaveyou that the OW
> language bindings do.
On Tue, 2005-10-18 at 10:28 -0400, Geo Carncross wrote:
> All of which makes exposing the synchronization primitives used by OW
> pretty much worthless.
I should clarify, that providing a common API to the language bindings
isn't bad, but requiring that they use them is- that is, having other
part
On Mon, 2005-10-17 at 20:09 -0400, Paul Alfille wrote:
> This gets to a larger question: what should be internal to owlib, and what
> should be in ow.h that is used by other programs. In the past, the only
> direct clients of owlib were the included programs owfs., owhttpd,
> owserver, ... They
On Tuesday 18 October 2005 01:52 am, Gregg Levine wrote:
> Hello from Gregg C Levine
> Just for kicks, what release version of FUSE are we using this
> timeperiod? From that project's CVS, or a numbered version that
> they've built, and numbered accordingly?
Christian's note is definitive in this.
I have updated the configure script a bit to test the installed fuselib.
I compiled latest owfs-cvs with fuse-2.4.1 and installed everything.
Tested "/opt/owfs/bin/owfs -u /mnt/1wire/" and it worked of course.
rm -f /usr/local/lib/*fuse*
rmmod fuse
Compiled and installed fuse-2.2.1.
Tested "/op
I have updated the owfs code to work with the latest released
fuse-2.4.1, but it should also compile with all versions between
fuse-1.4 -> fuse-2.3.
I don't know which version to recommend since all versions seem to
work when you compile them together from scratch.
Just to be sure about the fuse-
