Re: Missing braille durring boot
Odd Martin Baanrud <martin@la5ska.net> writes:
> Hello Mario,
>
> At 12:32 09.03.2009, you wrote:
>
>> > Btw, this was not a problem in Etch.
>>
>>I know. The actual problem is that BRLTTY now links against
>>three libraries in /usr/lib. While libstdc++ is probably a bug, and libgpm
>>could be avoided, libicu is something we really want to link against since
>>BRLTTY now has Unicode support. Maybe we should try to convince
>>ICU upstream to move it into /lib?
>
> That' sounds to me as a better solution.
> However, I don't know much of development, so others need to take the
> final dissision.
>
>> > In all of my Etch installations, with /usr on a separate partition,
>> > BRLTTY starts just out of the box.
>>
>>Because I put some extra effort into avoiding linking against libraries
>>in /usr during the Etch release. Apparently, I let this slip
>>for Lenny. So, I am the one to blame, go ahead.
>
> Well, let me come up with a suggestion instead.
> What if we could get BRLTTY into the initrd used durring boot?
Support for BRLTTY in initramfs is necessary anyway to support
crypted volumes. I have a sort of working solution sketched on a workstation
of mine that needs access to the crypt password prompt, but I
decided to delay this change until the squeeze cycle starts.
> Then the user is able to check what happends if the root partition
> isn't mounted for some reason, amung other things.
There is one problem involved here though, BRLTTY apparently needs
to be restarte during bootup when it was started from within the initrd.
While this is not pretty, I dont see an obvious way around it, so
if we want to have access during initrd time, we will have to bite the bitter
fruit.
--
CYa,
⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger mlang/key@db.debian.org
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/>
Reply to: