Samuel Thibault, le Thu 05 Apr 2012 14:26:26 +0100, a écrit :
> Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :
> > Can brltty be convinced not to grab this connection?
>
> It could, but we don't want to, as it would break brltty for people who
> use the braille devices with chips using that ID, making the computer
> completely unusable for them, really not a good thing.
>
> How brltty ended up being installed on your system? Was it brought
> through some dependency?
And still, ideally we'd want brltty installed by default on all systems,
ready to be triggered by udev (but not for all devices, all those which
are known not to conflict with other serial/USB converters).
What Ubuntu did was to disable brltty startup by default, which we don't
want either.
Let me summarize the scenario I can see:
- brltty is used during the Debian Installer, and shall thus be
installed and enabled on the target system.
- brltty is not used during the Debian Installer, but should still be
installed on the target system, but not enabled, and rather just
triggered by udev.
- someone installs brltty by hand. I believe in that case we want
to enable it too ("all it takes to make braille work in consoles is
installing brltty").
So perhaps we should ship brltty enabled by default, and make the Debian
Installer disable it when it was not used during installation?
Samuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
