Disabling graphical boot and starting applications early

[Tom H]

On Tue, Dec 11, 2012 at 6:23 AM, Daniel Dalton
<daniel.dalton at iinet.net.au> wrote:
>>>
>>> The brltty daemon is starting far to late.
>>> How to make this start as soon as the root fs is mounted?
>>> I disabled brltty in /etc/default/brltty yet it is still starting.
>>> So I have not even figured out where abouts it is being started.
>>
>> Theoretically, set "START_IN_INITRAMFS=true" and "RUN_BRLTTY=yes" in
>> "/etc/default/brltty" and run "update-initramfs -u -k $(uname -r)".
>
> Yes, that is correct, but I'm trying to get it to start earlier. On
> debian it would start as soon as the root fs was mounted and the brltty
> files were accessible.

I've compared the Ubuntu and Debian 4.4.5 packages and there's a difference.

There are a few differences between the Debian and Ubuntu packages.

Debian has some "extras". The following's not a comprehensive list.

Debian has a few scripts "/sbin/brltty-setup",
"/lib/brltty/brltty.sh", "/usr/lib/ubiquity/target-config/31brltty",
"/usr/share/initramfs-tools/scripts/init-top/brltty",
"/usr/share/initramfs-tools/hooks/brltty", and
"/usr/share/brltty/initramfs/brltty.sh" as well as udev rules in
"/lib/udev/rules.d/".

So Debian has stuff happening in the initramfs that Ubuntu doesn't.
Either the Ubuntu maintainer ripped it out or he/she replaced it with
something that isn't being triggered as early. You might want to file
a bug report...

(You could uninstall the Ubuntu package and install the Debian one.)