The script /etc/init.d/pandora-state outputs an error-message on a fresh
install, because there is no /etc/pandora/conf/filter.state
The related snippet is in dstart():
filter=$(cat /etc/pandora/conf/filter.state)
/usr/pandora/scripts/op_videofir.sh $filter
The file is not checked for existance. So op_videofir.sh is run without
parameter. The problem vanishes if you set the fir-filter in xfce once.
This little flaw could be solved by either adding a check for the file
or by adding a default /etc/pandora/conf/filter.state in the installation.
Now for something little special. I disabled boot-splash-screen and
created a bash-menu in which runs before logging in (started from
/etc/inittab) and from which i can start init-scripts by pressing a
number. While setting this up, i noticed that two scripts (so far) do
not launch from there, but work when i run them manualy as logged in
root: w1251-init and slim-init.
I tracked the problem down to the fact, that in these scripts a command
is run with "&" behind them to start them in background (once "slim-init
-d &" and once "dstart() &" ) When i removed these the scripts ran
nicely from my pre-logged-in-menu. Not sure if everyone wants or needs
these & removed, but at least for slim-init it doesn't bring any
advantage as it is launched in background anyway (-d).
For w1251-init the & brings a very slight speed-advantage for booting,
but is that really sane? Your choice. ;) I'm not that experienced in it.
Lomaxx