Uli Fahrenberg <[EMAIL PROTECTED]> wrote: | 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. | You are right.. but there is a misunderstanding. I didn't write/create any script. This concern a LFS/BLFS script somewhere. The error occure just after the first line(s) of 'mountkernfs'. It says first '/proc is not a mount point' and then above error ([: ==: ......) Then the system continu loading with at every try to load a device ( i presume) that error. All these errors (always the same error) are NOT logged.
After logged-in the /proc, /sys are MOUNTED and are NOT empty but don't contain some devices. Somewhat wrong with LFS 6.1-3 ? mess-mate -- Communicate! It can't make things any worse. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
