Hi,

I'd like some help getting DSL, OWFS , CURL and FUSE all to work together as advertised. Any experts here?

I have had a thread going on the DSL forum this week but still have not found better than a work around.

In a nut shell, I can get the OWFS to work with the latest DSL except that the local file system access to the 1wire devices isn't there. FUSE is touted as the miracle by which this should happen. I have FUSE loaded and installed but no go. My work around is to use the //localhost interface.

I have seen it all work together, with a prepackaged DSL iso version at the OWFS download site but it is quite an old version of DSL and I cannot get CURL to work on it. I am not too interested in putting time into the old DSL version and am concentrating on the new one.

Suggestions anyone?

Thanks and best regards,

Brian H.
Toronto Ont.

I'd like some help getting DSL, OWFS , CURL and FUSE all to work together as advertised. Any experts here?
---------------------------------------
Well, I have some expertise, having written owfs and the earlier dsl support.

CURL should be an independent issue, it expects to access a web server, so owhttpd (the webserver version of owfs) will be your access.

How are you installing owfs? Building it under DSL or installing it from an rpm or deb file? I ask, because the problem could be:
1. building on DSL needs the FUSE header file, usually in fuse-dev
2. The pre-built versions were probably built in 2.6 kernel machines and perhaps will have problems with 2.4 kernels.

If you start owfs with debugging (owfs -u -m 1wire --error_level=9 --foreground) you should get more information. Please post what you see.

Paul Alfille

P.S. When you get it all working, can you help me post a newer owfs-dsl file?

Hi Paul,

Thanks for weighing in on this, I couldn't imagine a better expert to have advice from. I feel I've hit the motherlode!

First off, I have been using the owfs.uci from ibiblio as follows:

The info file for which says:

If there is a better source or version, I am so far unaware of it.

I have been starting OWFS with the owfs.all script, borrowed from your mydsl.iso at the OWFS download site.

I will restart OWFS with the debugging as you suggest and post the results ASAP.

Of course, you bet!

Thanks again,

Brian H.

Ok I tried the running OWFS with debug as suggested:

First off, it objects to the -m and claims not to know about that one.--help and --morehelp seem to concur.

--help:

--morehelp:
When I run the lines of the owfs.all script manually by typing each at the command prompt, I get no arguements until I reach the line:

where upon, it reports:

This is beginning to feel like a file permissions issue to me. Do I need to change file permissions to allow OWFS to access the /home/dsl/1 wire directory ?

Also, in the old canned version of mydsl packaged with OWFS, the OWFS.all is in, and run from, the /opt/OWFS/bin directory. I cannot seem to write it to there, as dsl tells me its a read only file system, so I have been running it from the /home/dsl directory. Might that be an issue ?

Thanks,

Brian H.

Hi Brian,

My original recommendations were before I realized you were using the (older) pre-packaged version of OWFS.

You are right, the "-m" option wasn't implemented back then (the function was there, but we didn't need "-m" until new features threatened ambiguity).

Since all your problems come from FUSE, I suspect that a new version would work with the newer fuse.

One suggestion would be to try "sudo modprobe fuse" first.

owfs.all is a setup script that tries to load fuse (it wasn't included in older dsl version, like 1.2) load the library path, and then run owfs (renamed owfs.bin I think).

The read-only file access is DSL's approach to the filesystem. It's probably a loopback directory located in a compressed file, but I don't know for sure.

Perhaps the easiest would be a new version of everything. It's possible that a standard Ubuntu or debian package would work -- let me experiment.

Paul Alfille

Hi Paul

Here is the sequence I habitually have been going through to start OWFS, based on suggestions at the dsl forum noted earlier.

1. Starting from a fresh boot from the CD.
   
2. Install ntfsprogs-2.uci from the my dsl control panel.
3. Install fuse with 'sudo modprobe fuse' at the command prompt.
4. Install OWFS.uci from the uci section of mydsl.
5. Run the OWFS start script borrowed from the other older DSL version packaged with OWFS

Sounds good to me. Thanks for the assist.

Brian H.

Hi Paul,

Any progress ?

Thanks,

Brian H

Just uploaded a new version.

Probably in the "testing area".

It is also on the owfs website at http://sourceforge.net/project/showf...group_id=85502

Change the file names from owfs-2.7p4.* to owfs.*

Paul Alfille

Hi Paul,

Thanks for the new version, I am not having any joy with it however.

I confirm it as the 2.7 version and d/l it from the testing area of the ibiblio repository. It installs fine apparently, but when I invoke it using the 'run all OWFS programs' under mydsl/OWFS, it only starts up the browser window and creates the /hpme/dsl/1wire directory, but it doesn't see the serial 1wire controller on my serial port and shows that there are no 1wire devices connected in both the filesystem and web 1wire directories. I don't have any usb 1wire controllers sad to say.

If I reboot my computer and run the old version, I can at least see the connected 1wire devices through the web interface at port 3001.

I have compared the start.all scripts from old and new OWFS versions and it looks like a serial 1wire contoller should work. Am I missing something?

I'll try it on my other system at home tonight to see if it behaves same or different.

Thanks and best regards,

Brian H.

Rather than use the intermediate version I sent you, take a look at the official DSL site. There is a new version there (based on OWFS 2.7p4) that works pretty well, in my test scenario.

Paul Alfille

Sorry Paul but I have looked the dsl site & forums over but cannot find the new version's location. Can you be a bit more specific as to its where abouts?

Thanks,

Brian H.

Under "Testing"
e.g.ftp://ftp.oss.cc.gatech.edu/pub/linu...sting/owfs.uci

or on the owfs site:
https://sourceforge.net/project/show...ckage_id=88590

Paul Alfille

Here is the sequence I use to start OWFS:.

1. Starting from a fresh boot from the CD.
2. Install ntfsprogs-2.uci from the my dsl control panel.
3. Install fuse with 'sudo modprobe fuse' at the command prompt.
4. D/L owfs.uci to ~/ from ftp://ftp.oss.cc.gatech.edu/pub/linu...sting/owfs.uci
5. Move owfs.uci to mydsl/
6. Open mydsl browser and Load Local/owfs.uci

I get the /1wire directory in a different path now:

ramdisk/tmp/1wire instead of ramdisk/home/dsl/1wire


but still my 1wire devices are not recognized or available either to the local file system or to the html port 3001.

Perhaps fuse is still not setup properly ? How have you setup fuse on your testbed system?

Thanks,

Brian H.

Does your user account have permissions to the fuse group?

Ok, let's figure this out in order.

After you have done the sequence you describe, I presume you run "owfs-startall" from the Mydsl menu.

Can you then start an XShell window and type "ps axf | grep ow" to see all the programs running. owserver, owhttpd, owfs and owftpd should all appear.

The next step, in that same window is to type "owdir" which should show the list of devices, or at least "statistics, uncached, structure, ..."

Paul Alfille

Also, what version of DSL are you running. The current uci was created under 4.2.5.