Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Martin Patzak (GMX)
who else thinks the following should find it's way onto the owfs web-site? > BY THE WAY, why are you compiling yourself? Raspbian packages > of owfs-3.1p1 are available. > > Edit (or create) your /etc/apt/preferences to contain: >

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Gregg Levine
Hello! Mick no you are not. The rules for building OWFS on a Debian based variety of Linux have never really changed since before the release of the first Raspberry Pi device. However we need to change the rules appropriately for the Raspberry Pi. And we need to get things updated on the website

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Mick Sulley
I have been compiling myself (and getting it wrong it seems!) for a long time now because the version in the repositories is so old, or so I thought. Just followed you instructions and I have 3.1p1 installed - easy!! Now to start testing out ow-shell Many thanks for your help once again. Mic

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Jan Kandziora
Am 25.07.2016 um 22:07 schrieb Mick Sulley: > I am sure my problems here are due to my lack of understanding of the > whole build process. > > This is a clean install of a RasPi, so no sudo config has occurred. My > normal method of install was - > > download the file from SourceForge to my de

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Don Veino
You can configure and make from any directory. Just use a subdirectory (for clean up later) under your home directory on the pi to copy over the files to. It will place the compiled binaries where they need to go through the process. On Mon, Jul 25, 2016 at 4:07 PM, Mick Sulley wrote: > I am sur

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Mick Sulley
I am sure my problems here are due to my lack of understanding of the whole build process. This is a clean install of a RasPi, so no sudo config has occurred. My normal method of install was - download the file from SourceForge to my desktop. Copy it to the RasPi and move it to /usr/local/src

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Jan Kandziora
Am 25.07.2016 um 19:28 schrieb Mick Sulley: > Hi Jan, > > Thank you for your help yesterday, my system is up and running again! > > I am just building a test system to try out owshell and also installing > without sudo. > > With owfs-3.1p1 when I try ./configure I get > ./configure: line 2256:

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Martin Patzak (GMX)
you just need to add write permission for your user or group to that directory to have the log written successfully, and NO, NEVER build as superuser, like Jan already emphasized! On 07/25/2016 07:59 PM, Mick Sulley wrote: OK, so do I need to change a permission or do I need to run as sudo?

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Mick Sulley
OK, so do I need to change a permission or do I need to run as sudo? On 25/07/16 18:49, Roland Franke wrote: > Hello, > >> I am just building a test system to try out owshell and also installing >> without sudo. >> With owfs-3.1p1 when I try ./configure I get >> ./configure: line 2256: config.lo

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Roland Franke
Hello, > I am just building a test system to try out owshell and also installing > without sudo. > With owfs-3.1p1 when I try ./configure I get > ./configure: line 2256: config.log: Permission denied > ./configure: line 2266: config.log: Permission denied here will be the config.log written in

Re: [Owfs-developers] owfs is DISABLED

2016-07-25 Thread Mick Sulley
Hi Jan, Thank you for your help yesterday, my system is up and running again! I am just building a test system to try out owshell and also installing without sudo. With owfs-3.1p1 when I try ./configure I get ./configure: line 2256: config.log: Permission denied ./configure: line 2266: config.

Re: [Owfs-developers] Owfs-developers Digest, Vol 122, Issue 15

2016-07-25 Thread Dr. Trigon
>In short: the fuse binding enables user programs to do read() and >write() on properties. Both read() and write() aren't atomic for >anything else but bytes. But most Onewire properties aren't bytes. For That makes perfect sense. Thanks for the nicely worked out example! Ok switching to owshell.