07.12.2020 04:39, Dave Mielke пишет:
There's another possibility worth trying, i.e. to use the /sys/ path rather
than the /dev/ path. I've updated the systemd-wrapper script to handle this.
The patch (attached as systemd-wrapper.patch) is attached to this message.
Then, to use the /sys/ path, a change must be made to brltty's udev rules. Go
to the SYSTEMD_WANTS line and remove the DEVNAME bit. In other words, change:
SYSTEMD_WANTS}+="brltty@$env{DEVNAME}.service"
to:
ENV{SYSTEMD_WANTS}+="[email protected]"
And then, of course, run: udevadm control --reload
I hope this works because it's actually nicer.
i applied the patch and changed udev rule. unfortunately i still get:
дек 07 12:20:17 alex-pc systemd[1]: [email protected]:
Succeeded.
дек 07 12:20:17 alex-pc systemd[1]: Stopped BRLTTY Instance:
/dev/bus/usb/001/015.
--
Sincerely, Alexander.
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://brltty.app/mailman/listinfo/brltty
