That's a case of DirectFB magic.. I don't know any other interesting side effects besides timing; When you use a log-file it will create a file which might delay startup for something else critical to complete in time. Alternatively, opening your console might have failed..
Tim Richardson wrote: > Debian has a boot splash program called splashy which uses directfb v1 > Recent changes to splashy cause a start-up failure on my three Debian > machines. The error occurs in a code that's initialising directfb. The > recent changes move the initialisation earlier in the startup, to hook > into premount. > > While trying to debug this, I stumbled on a workaround. > If I create the file > /etc/directfbrc > and put this one line in it: > > log-file=/tmp/directfblog > > then splashy starts successfully. I have no idea why. > > The use of /tmp seems to be necessary; /root didn't work. > I don't actually see any such file /tmp/directbflog when the system > finishes booting. > > I wonder if a directfb developer may be able to connect this > workaround to a useful insight. > > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > directfb-dev mailing list > directfb-dev@directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > -- .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
