DamnSmallLinuxThis forum is for the discussion of DamnSmallLinux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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?
Title: owfs.uci
Description: One Wire File System
Version: 2.2
Author: http://owfs.sourceforge.net
Original-site: http://owfs.sourceforge.net
Copying-policy: GPL
-----==[ Color = blue Filesize: 181K ]==-----
Extension-by: Paul Alfille (palfille@earthlink.net)
Comments: Use Dallas 1-wire sensors from the command line
Change-log:
Current: 08/21/2005 - First
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.
Quote:
When you get it all working, can you help me post a newer owfs-dsl file?
Of course, you bet!
Thanks again,
Brian H.
Last edited by bjh; 02-16-2008 at 09:09 PM.
Reason: clarification
1-wire side (device):
-d --device devicename |Serial port device name of 1-wire adapter
| e.g: -d /dev/ttyS0
-u --usb [number] |USB 1-wire adapter. Choose first one unless number specified
| e.g: -u -u3 first and third USB 1wire adapters
-s --server [host:]port |owserver program that talks to adapter. Give tcp/ip address.
| e.g: -s embeddedhost:3030
Client side:
mountpoint |Directory the 1-wire filesystem is mounted
-h --help |This basic help page
--morehelp |Optional items help page
-C --Celsius |Celsius(default) temperature scale
-F --Fahrenheit |Fahrenheit temperature scale
-K --Kelvin |Kelvin temperature scale
-R --Rankine |Rankine temperature scale
-P --pid_file |file where program id (pid) will be stored
--background |become a deamon process(default)
--foreground |stay in foreground
-r --readonly |no writing to 1-wire bus
-w --write |allow reading and writing to bus(default)
-t |cache timeout (in seconds)
-f --format |format for 1-wire unique serial IDs display
| f[.]i[[.]c] f-amily i-d c-rc (all in hex)
--error_print |Where information/error messages are printed
| 0-mixed(default) 1-syslog 2-stderr 3-suppressed
--error_level |What kind of information is printed
| 0-fatal 1-connections 2-calls 3-data
-V --version |Program and library versions
--fuse_opt |Options to send to fuse_mount (must be quoted)
| e.g: --fuse_opt="-x -f"
-h --help |Basic help page
--morehelp |This optional items help page
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:
Quote:
opt/owfs/bin/owfs.bin -s 3333 /home/dsl/1wire
where upon, it reports:
Quote:
fusermount: mount failed: Operation not permitted
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 ?
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.
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.
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.
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?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.