mess-mate, Nov 5, 18:23 +0100:
Uli Fahrenberg <[EMAIL PROTECTED]> wrote: | Allard Welter, Nov 1, 17:02 +0100: | | >This looks like a bash (non-)thingy Have you checked the startup scripts for the occurrence | >of "[: ==" ? I can't recal a colon being part of any conditional - perhaps a typo? | | Without additional information it is unlikely anybody can help you with this. It's like the | needle-in-a-haystack problem. | | But I believe Allard is wrong above; IIRC this error is typically caused by a line like | | [ $X == blah ] && do_something | | which in case $X is empty becomes | | [ == blah ] ... | | and then bash complains that the [ is followed by an == operator. | | This kind of problem can be prevented by instead of the above test saying | | [ X$X == Xblah ] ... | | but again, without additional info this is difficult to debug. | Thanks for the help at now guys, but the only startup-script i've found containing a ':' is udev ( with :space: ).
Re-read my above explanation, and you'll find that searching for files containing ':' is *not* the way to go.
uli -- Uli Fahrenberg -- http://www.math.aau.dk/~uli -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
