Indeed this was the problem.
The original OWFS is located in /usr/bin, but the new one is installed in
/opt/owfs.
Thank you for the help.
Peter
2018-01-06 10:40 GMT+01:00 Colin Law :
> On 6 January 2018 at 00:19, Péter Zsembery
> wrote:
> > Hi,
> >
> > Back in May last year I asked for help to m
Hi,
running owfs 3.2p1-1 on ArchLinux (installed via aur), with recent
systemd the mount for owfs does not show up in the system. This is
caused by the RuntimeDirectory in /run essentially being a bind-mount
from somewhere else (as researched by the nice folks in the #systemd
channel). The mo
Am 07.01.2018 um 14:38 schrieb Christian Vogel:
> Hi,
>
> running owfs 3.2p1-1 on ArchLinux (installed via aur), with recent
> systemd the mount for owfs does not show up in the system. This is
> caused by the RuntimeDirectory in /run essentially being a bind-mount
> from somewhere else (as resear
On Sun, Jan 07, 2018 at 02:38:29PM +0100, Christian Vogel wrote:
> Hi,
>
> running owfs 3.2p1-1 on ArchLinux (installed via aur), with recent systemd
> the mount for owfs does not show up in the system. This is caused by the
> RuntimeDirectory in /run essentially being a bind-mount from somewhere
Hi,
the current version of owfs only provides a php module for php versions 4 and
5.
To support php7 the parameter when calling swig in the makefile needs to be
changed to -php7.
php7 is supported by swig since version 3.0.11.
The attached patch does this, but may need some cleanup. Also a check
> On 7 Jan 2018, at 14:38, Christian Vogel wrote:
>
> Please change the mount to somewhere outside of /run, I propose
> /dev/bus/owfs. See attached file.
As a rule of thumb everything controlling a node in /dev should run in
kernel-space, not user-space. Owfs is entirely user-space, so no do
