At Sun, 14 Feb 2016 19:20:48 -0500 Robert Heller heller@deepsoft.com wrote:
At Mon, 15 Feb 2016 09:41:32 +1100 CentOS mailing list centos@centos.org wrote:
On 14/02/16 02:14, Robert Heller wrote:
I sent this out about a week or so ago, but I have heard nothing. I am *thinking* it is a SELINUX problem, but I cannot figure out what.
If you suspect SELinux is to blame, have you tried putting SELinux into permissive mode to see that resolves the issues?
setenforce 0 (re-enable with setenforce 1)
I guess I can try that.
If everything works with SELinux in permissive mode, then you'll need to create a policy for it *[0]*.
That would imply that somehow the policies on my laptop are *different* than the policies on my desktop. *I* don't remember setting any such policies...
OK, I just tested it:
sauron.deepsoft.com% sudo /usr/sbin/setenforce permissive sauron.deepsoft.com% sudo minicom Device /dev/ttyACM0 access failed: No such file or directory. sauron.deepsoft.com% sudo /usr/sbin/setenforce enforcing
Nope, that did not help.
ak.
*[0]*: https://wiki.centos.org/HowTos/SELinux#head-faa96b3fdd922004cdb988c1989e5619...
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 16/02/16 01:32, Robert Heller wrote:
OK, I just tested it:
sauron.deepsoft.com% sudo /usr/sbin/setenforce permissive sauron.deepsoft.com% sudo minicom Device /dev/ttyACM0 access failed: No such file or directory. sauron.deepsoft.com% sudo /usr/sbin/setenforce enforcing
Nope, that did not help.
When using my USB to serial device I've had to make sure that I'm a member of the 'dialout' group. Even though you are using sudo to run minicom, could it be that the user account you are logged in as still needs to be a member of the dialout group? (tol - thinking out loud)
ak.
-
Anthony K -
Robert Heller