owfs is a package that allows Dallas Semiconductor's 1-wire devices to be accessed as though they were files and directories. I would suggest that this package be registered as sys-fs/owfs. Ian
Created attachment 47974 [details] owfs-1.0_pre0.ebuild
Things to fix: * Don't hard code the version number * use_enable is your friend * Why no econf? * Why no emake? If it really doesn't work, put an explicit comment there saying why, or use 'emake -j1'.
Created attachment 48158 [details] owfs-1.0_pre0.ebuild the designation "p" is being used instead of "pre" to denote a pre-release, so that must be changed from the ebuild version number for downloads. Other than that, all suggested changes have been made.
I'd love to see this get into portage asap. Is there any particular issue holding it up? -Jacob
any update about this ebuild getting into portage ? mvg Maarten
Created attachment 120017 [details] owfs-2.6_p4.ebuild Created an ebuild of the most recent version of owfs. I added a bunch of use flags and got rid of the hard coded version number. I've had owfs installed for a while (without using an ebuild), so it's possible I may have forgotten some vital step that I had to do the first time I installed it. Please give it a try and post your results. Specify the "vanilla" use flag for sys-fs/owfs in /etc/portage/package.use to get the generic configuration. (Is there a better way I should have done that?) Never having created an ebuild before, I'm not sure what is the next step to getting it into the official portage tree. Thanks, Ben
When thread safety is enabled, owfs doesn't compile cleanly with php use flag. Adding an adoption of this patch to your PORTAGE_TEMP/sys-fs/owfs-2.6.p4/work/owfs-2.6p4/module/swig/php/ow_wrap.c should help a lot: https://lists.ubuntu.com/archives/ubuntu-bugs/2005-February/036494.html Version p5 is also out (5 Days after p4 was added here :-) ) and it still hast the same problem that can be fixed with the patch. Worked fine for me.
(In reply to comment #7) Hi Daniel, Thanks for checking the ebuild out. The file you suggest patching is actually auto-generated by swig during the build process (and apparently the process of creating the tar.gz source file), and it is swig that introduces the problem. It is a target of owfs/module/swig/php/Makefile.am. Could you try modifying that makefile as follows and verify that it solves the problem? You'll probably have to delete/rename ow_wrap.c to force it to create a new one. 36c36,38 < $(SWIG) -php4 -o $@ ../ow.i --- > $(SWIG) -php4 -o $@.tmp ../ow.i > sed 's/zend_rsrc_list_get_rsrc_type(z->value.lval)/zend_rsrc_list_get_rsrc_type(z->value.lval TSRMLS_CC)/' <$@.tmp >$@ > @RM@ -f $@.tmp Thanks! Oh - I didn't bother creating another attachment for 2.6-p5 because all that needs to be done is change the name of the file to reflect the new version.
owfs-2.6_p6 seems to raise some ERROR while installing the progs. Something changed and installing some file in /usr/bin fails with sandbox ACCESS violation. owfs-2.6_p5 works To get the error, simply copy owfs-2.6_p4.ebuild to owfs-2.6_p6.ebuild and try installing it. My use flags where "fuse httpd perl php python server usb -debug -ftp -parport -tcl -vanilla".
Just used the owfs-2.6_p4.ebuild after changing the name and building the digest to emerge sys-fs/owfs-2.7_p0 and compiled fine. Used USE flags USE="ftp fuse httpd perl php python server vanilla -debug -parport -tcl -usb Haven't tested it working yet cause have never used owfs, have been using digitemp. But getting relay board from hobby boards and even though digitemp says it supports the DS2406 switch, I don't think it really does. So going to try owfs.
There is so much owfs documentation, but figuring out what I need to do to start using it is lost on me. Digitemp is still working fine but can't get owfs to work, I do have a /mnt/1wire folder that has stuff in it, but it doesn't like my serial device and can't seem to get anywhere. # owfs -d /dev/ttyS1 /mnt/1wire DEFAULT: Cannot detect DS9097 (passive) interface on /dev/ttyS1. fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option decibelshelp decibels # owfs -d /dev/ttyS1 The device is correct. Any of you know a good LINUX site that I use that has information in a more straightforward manner, than gobs of information in a lous y format like I am finding? Thanks.
The vanilla use flag causes all the others to be ignored. It just uses the default settings, which should work fine unless you need something special. You must not have digitemp (or anything else that uses that serial port) running when you try to use owfs. It looks like your /mnt/1wire directory has something in it before starting owfs. That might cause problems. It should be empty. HTH (In reply to comment #11) > There is so much owfs documentation, but figuring out what I need to do to > start using it is lost on me. Digitemp is still working fine but can't get owfs > to work, I do have a /mnt/1wire folder that has stuff in it, but it doesn't > like my serial device and can't seem to get anywhere. > > # owfs -d /dev/ttyS1 /mnt/1wire > DEFAULT: Cannot detect DS9097 (passive) interface on /dev/ttyS1. > fuse: mountpoint is not empty > fuse: if you are sure this is safe, use the 'nonempty' mount option > decibelshelp decibels # owfs -d /dev/ttyS1 > > The device is correct. Any of you know a good LINUX site that I use that has > information in a more straightforward manner, than gobs of information in a > lous y format like I am finding? > > Thanks. >
(In reply to comment #12) > The vanilla use flag causes all the others to be ignored. It just uses the > default settings, which should work fine unless you need something special. > > You must not have digitemp (or anything else that uses that serial port) > running when you try to use owfs. > > It looks like your /mnt/1wire directory has something in it before starting > owfs. That might cause problems. It should be empty. > > HTH Thanks, I just got on the owfs-dev list at nabble. Hopefully some one helps me there. I don't have digitemp running unless called manually, so not in cron,... and seems that /mnt/1wire is populated as soon as fuse starts. I am just not finding clear info on getting started. It don't even see my device on /dev/ttyS1 and digitemp does. Confused? > > (In reply to comment #11) > > There is so much owfs documentation, but figuring out what I need to do to > > start using it is lost on me. Digitemp is still working fine but can't get owfs > > to work, I do have a /mnt/1wire folder that has stuff in it, but it doesn't > > like my serial device and can't seem to get anywhere. > > > > # owfs -d /dev/ttyS1 /mnt/1wire > > DEFAULT: Cannot detect DS9097 (passive) interface on /dev/ttyS1. > > fuse: mountpoint is not empty > > fuse: if you are sure this is safe, use the 'nonempty' mount option > > decibelshelp decibels # owfs -d /dev/ttyS1 > > > > The device is correct. Any of you know a good LINUX site that I use that has > > information in a more straightforward manner, than gobs of information in a > > lous y format like I am finding? > > > > Thanks. > > >
Not sure if this problem or not. If is maybe a note in the ebuild. Or maybe I have had a long day and this just isn't making sense. Do you need the fuse userspace program AND the kernel compiled with CONFIG_FUSE_FS in order to use it with OWFS? Otherwise I have a /dev/fuse even without the kernel module. So little confused.
Nope your right Ben don't need fuse in kernel. Didn't even try it after you said that. The ebuild is working fine for me though. With different versions.
OWFS 2.7_p0 is now in CVS. Have fun.
