Here are a two small bugs that i found in some scripts of the pandora-root-fs. I hope I quote the right sections as i fixed them yesterday and try to recall them now, but i'm quite confident:
##################################################################### from /usr/pandora/scripts/op_startup.sh
[ -f $OP_CHECKFILE ] && echo "\nOP_STARTUP: $OP_CHECKFILE exists, not first boot." || $OP_FIRSTRUN
The echo-command needs a "-e" to handle the \n correctly. Also a proposal: Whould it be sane and good to completely remove this script in case $OP_CHECKFILE exists? I think we could add "/usr/sbin/update-rc.d -f oprun-init" in that case. Or is there something happening that i am not seeing?
##################################################################### Then there is a bug in /etc/init.d/udev-cache. I noticed this when tracking down a message while booting, which said that /tmp/uname does not exist. I think the line before my editing looked like this:
[ -f /etc/default/udev ] && . /etc/default/udev
should IMHO be:
[ -f /etc/default/udev ] && /etc/default/udev
At least I didn't get the message afterwards anymore. ######################################################################
Lomaxx
On Mon, Jul 4, 2011 at 6:30 PM, Klaus Brinkmann bbrink@uni-koblenz.de wrote:
Here are a two small bugs that i found in some scripts of the pandora-root-fs. I hope I quote the right sections as i fixed them yesterday and try to recall them now, but i'm quite confident:
##################################################################### from /usr/pandora/scripts/op_startup.sh
[ -f $OP_CHECKFILE ] && echo "\nOP_STARTUP: $OP_CHECKFILE exists, not first boot." || $OP_FIRSTRUN
The echo-command needs a "-e" to handle the \n correctly.
True. Do you want to send formal git patch to get proper credit? It's in openpandora.oe.git: http://git.openpandora.org/cgi-bin/gitweb.cgi?p=openpandora.oe.git;a=tree;f=...
I think the line before my editing looked like this:
[ -f /etc/default/udev ] && . /etc/default/udev
should IMHO be:
[ -f /etc/default/udev ] && /etc/default/udev
At least I didn't get the message afterwards anymore.
Not really, by doing this you no longer source /etc/default/udev, DEVCACHE does not get set and /etc/init.d/udev-cache no longer does whatever it's supposed to do (it does nothing).