On Tuesday 01 November 2005 19:24, Uli Fahrenberg 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. Yes, this makes sense - Bash is trying to be grammatically correct. Thanks Uli. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
