Bob McGowan wrote:
Hello,At least in bash, both '=' and '==' work as the condition. From the bash man page:string1 == string2 True if the strings are equal. = may be used in place of == for strict POSIX compliance.The original poster said "When I boot that system the boot stops solid in the grep stmnt in /etc/hotplug/usb.rc line 200:if [ ”$SYNTHESIZE” = false ]"I'd suggest looking at the 'grep' command itself. Since I don't know what the script looks like, this is just a guess, but if the file name being grep'd on is provided via a variable, and the variable never got an assignment, then the grep would be reading STDIN, which would cause the whole process to 'hang', while 'grep' waits for input. There may be other reasons for lack of input, but I'd wager it's 'grep' that is causing the hang.Bob John Schmidt wrote:On Wednesday 29 March 2006 16:25, Hugo Vanwoerkom wrote:Hi, Maybe someone has a suggestion here. Problem: In Sarge I normally run the -ck kernel patches from Con Kolivas. He just came out with 2.6.16-ck1 and -ck2. When I boot that system the boot stops solid in the grep stmnt in /etc/hotplug/usb.rc line 200: if [ ”$SYNTHESIZE” = false ]It appears like this is a bug in the script, and it should be if ["$SYNTHESIZE" == false] (note the == instead of the =)
Thanks John and Bob for the answers.I "solved" it by first removing hotplug and then installing udev. Now it boots normally.
That line 200 in /etc/hotplug/usb.rc still reads ”$SYNTHESIZE” = false, with an = and not an ==.
Why this happend, I haven't got the faintest.The side effects of udev are (for me), an application I wrote for writing to /dev/vcsa<x> as a replacement for vcstime now finds the screen offset differently, and nVidia won't start.
I googled for the latter and found a number of suggestions, which I am about to try out.
But the most important part is that 2.6.16-ck2 is up and running ;-) H