{"action":"created","issue":{"url":"https://api.github.com/repos/openhab/openhab-docker/issues/3","repository_url":"https://api.github.com/repos/openhab/openhab-docker","labels_url":"https://api.github.com/repos/openhab/openhab-docker/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/openhab/openhab-docker/issues/3/comments","events_url":"https://api.github.com/repos/openhab/openhab-docker/issues/3/events","html_url":"https://github.com/openhab/openhab-docker/issues/3","id":145990450,"number":3,"title":"z-way GPIO daughterboard","user":{"login":"snizzleorg","id":1573482,"avatar_url":"https://avatars.githubusercontent.com/u/1573482?v=3","gravatar_id":"","url":"https://api.github.com/users/snizzleorg","html_url":"https://github.com/snizzleorg","followers_url":"https://api.github.com/users/snizzleorg/followers","following_url":"https://api.github.com/users/snizzleorg/following{/other_user}","gists_url":"https://api.github.com/users/snizzleorg/gists{/gist_id}","starred_url":"https://api.github.com/users/snizzleorg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/snizzleorg/subscriptions","organizations_url":"https://api.github.com/users/snizzleorg/orgs","repos_url":"https://api.github.com/users/snizzleorg/repos","events_url":"https://api.github.com/users/snizzleorg/events{/privacy}","received_events_url":"https://api.github.com/users/snizzleorg/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/openhab/openhab-docker/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":{"login":"cyberkov","id":312590,"avatar_url":"https://avatars.githubusercontent.com/u/312590?v=3","gravatar_id":"","url":"https://api.github.com/users/cyberkov","html_url":"https://github.com/cyberkov","followers_url":"https://api.github.com/users/cyberkov/followers","following_url":"https://api.github.com/users/cyberkov/following{/other_user}","gists_url":"https://api.github.com/users/cyberkov/gists{/gist_id}","starred_url":"https://api.github.com/users/cyberkov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cyberkov/subscriptions","organizations_url":"https://api.github.com/users/cyberkov/orgs","repos_url":"https://api.github.com/users/cyberkov/repos","events_url":"https://api.github.com/users/cyberkov/events{/privacy}","received_events_url":"https://api.github.com/users/cyberkov/received_events","type":"User","site_admin":false},"milestone":null,"comments":22,"created_at":"2016-04-05T13:32:51Z","updated_at":"2016-06-16T04:12:35Z","closed_at":null,"body":"how does one use the GPIO mounted z-way wave daughterboard with this?\r\n\r\nThis works normally like a serial port /dev/ttyAMA0\r\n\r\nwith openhab 1.8 one has to add \r\n\r\n```\r\n -Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0 \\\r\n\r\n```\r\n\r\nand \r\n```\r\nzwave:port=/dev/ttyAMA0\r\n```\r\nin the openhab.cfg\r\n\r\n\r\nto the start script. Any way to mount /dev/ttyAMA0 to something the dockerized openhab will use?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/openhab/openhab-docker/issues/comments/226383958","html_url":"https://github.com/openhab/openhab-docker/issues/3#issuecomment-226383958","issue_url":"https://api.github.com/repos/openhab/openhab-docker/issues/3","id":226383958,"user":{"login":"polarathene","id":5098581,"avatar_url":"https://avatars.githubusercontent.com/u/5098581?v=3","gravatar_id":"","url":"https://api.github.com/users/polarathene","html_url":"https://github.com/polarathene","followers_url":"https://api.github.com/users/polarathene/followers","following_url":"https://api.github.com/users/polarathene/following{/other_user}","gists_url":"https://api.github.com/users/polarathene/gists{/gist_id}","starred_url":"https://api.github.com/users/polarathene/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/polarathene/subscriptions","organizations_url":"https://api.github.com/users/polarathene/orgs","repos_url":"https://api.github.com/users/polarathene/repos","events_url":"https://api.github.com/users/polarathene/events{/privacy}","received_events_url":"https://api.github.com/users/polarathene/received_events","type":"User","site_admin":false},"created_at":"2016-06-16T04:12:35Z","updated_at":"2016-06-16T04:12:35Z","body":"@cyberkov from what I've read around online, gid 10 is usually the `wheel` group on many linux distro's not `uucp` like on Ubuntu. `uucp` is related to serial ports as far as I understand, I came across it when working with Arduino as well.\r\n\r\nSo your solution is to adjust the gid on the host to that of Ubuntu's `dialout` group(gid 20) via udev?\r\n\r\nI've done some research and most commonly `dialout` has a gid of `20` and `uucp` a gid of `14`.\r\n- Debian and deriviatives such as Ubuntu - dialout:20, uucp:10 - [ref](http://www.togaware.com/linux/survivor/Standard_Groups.html)\r\n- Arch - no dialout, uucp:14 - [ref](https://wiki.archlinux.org/index.php/DeveloperWiki:UID_/_GID_Database)\r\n- Alpine - dialout:20, uucp:14 \r\n- RedHat: no dialout, uucp:14 [ref](https://www-uxsup.csx.cam.ac.uk/pub/doc/redhat/redhat7/rhl-rg-en-7.0/s1-sysadmin-usr-grps.html)\r\n- Linux From Scratch: dialout:10, uucp:32 [ref](http://www.linuxfromscratch.org/clfs/view/clfs-2.0/arm/final-preps/creatingfiles.html)\r\n- openSUSE: dialout:16, uucp:14\r\n- Fedora: dialout:18, no uucp . Past versions had no dialout and uucp:14 [ref](https://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-users-groups-standard-groups.html)\r\n\r\nDistro's without ref link, information was sourced via `getent group dialout` and `getent group uucp` via Virtual Machines.\r\n\r\n[Debian Wiki](https://wiki.debian.org/SystemGroups):\r\n- dialout: Full and direct access to serial ports. Members of this group can reconfigure the modem, dial anywhere, etc. \r\n- uucp: The uucp user and group is used by the UUCP subsystem. It owns spool and configuration files. Users in the uucp group may run uucico. \r\n\r\n[Original use of `uucp` is deprecated, now used for serial ports?](http://docstore.mik.ua/orelly/other/Docs/oreilly/other2/puis3rd/0596003234_puis3-chp-5-sect-1.html)\r\n- `Controls ownership of the Unix serial ports. (uucp traditionally managed the UUCP system, which is now deprecated.)`\r\n\r\n> UUCP was a collection of utilities to support \"Unix to Unix copy\" tools before there was an internet. HOW it dialed out was up to the setup script, and could use any method. - [source](http://forums.fedoraforum.org/showthread.php?t=309763)\r\n\r\n[This](http://unix.stackexchange.com/questions/152326/why-does-uucp-take-group-10) was a common rank 1 result in my searches.\r\n- Link to Ubuntu docs is broken and should be [this](http://manpages.ubuntu.com/manpages/precise/man1/uucp.1posix.html), it documents the legacy use of `uucp`.\r\n\r\n[This](https://fedorahosted.org/fldigi/wiki/Documentation/HOWTO/Serial_Port_Setup) link describes how serial port access group name of `uucp` or `dialout` depends on distro.\r\n- Another confirmation [here](http://wiki.mattercontrol.com/Running_on_Linux), they advise to keep the gid/group the same as what the OS uses for other serial devices.\r\n- Ubuntu [treating the same `ttyACM0` address/device as `dialout` group](http://askubuntu.com/questions/58119/changing-permissions-on-serial-port) vs `uucp` group on Arch.\r\n\r\n---\r\n\r\nReasons to include `uucp`:\r\n- `uucp` is used by some distro's instead of `dialout` for serial devices\r\n- gid of 14 is fairly standard for `uucp` and perhaps a more consistent gid than those for `dialout`\r\n- `uucp` group with gid 10 in the Docker image is unlikely to be used/accessed for serial devices, nor does openHAB have a use for the legacy `uucp` usage. Changing the gid to 14 should have no negative impact but result in supporting more host OS without the need for asking users to tweak the gid their device mounts as(may not always be udev). This aids in portability of the container.\r\n- If you switch to Alpine for a smaller image at a later date, which is popular for Docker images to base off, this will not affect users as the groups `dialout:20` and `uucp:14` would be the same allowing for seamless transition.\r\n\r\nRegardless, since `dialout` can vary with it's gid across various host OS, you'll probably want to add to wiki/docs about this issue popping up for users not using the same host OS as what the Docker container for openHAB uses. Then either a way to pass the gids for openHAB to use or udev rule advice. \r\n"}}
{"actor":{"display_login":"polarathene"}}