You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
- Use tmpfiles_create_package - Use sysuser-tools unconditionally (bsc#1205161) OBS-URL: https://build.opensuse.org/request/show/1043600 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/brltty?expand=0&rev=60 |
6 months ago | |
---|---|---|
.gitattributes | 13 years ago | |
README.SUSE | 12 months ago | |
brltty-6.5.tar.xz | 12 months ago | |
brltty-udev-dir.patch | 12 months ago | |
brltty.changes | 6 months ago | |
brltty.spec | 6 months ago |
README.SUSE
Some notes on SUSE-specific configuration of brltty ======================================================================== USB: ------------------------------------------------------------------------ Most USB Braille displays should be autodetected by udev, starting brltty. However, some Braille displays have the same product IDs as generic USB-to-serial adapters, and, in order to avoid a conflict with these adapters, the brltty udev rules for them are not installed by default. If you have an Albatross, Cebra, Hims, HandyTech, or MDV display and connect it via USB, then you may want to install the brltty-udev-generic package. Alternatively, you can have systemd automatically start brltty at boot. Run chkconfig brltty on as the superuser. Authentication: ------------------------------------------------------------------------ By default, brltty authenticates with clients (such as orca) via a key file. However, SUSE enables polkit-based authentication instead. This eliminates the need to, ie, add users to the brlapi group in order to be able to have orca interact with the Braille display. It also disallows remote users from interacting with the display. If you would like to change this behavior, then you can edit the api-parameters directive in /etc/brltty.conf.