From: Riley Williams (terhi.victor@logonet.com)
Date: Fri Jun 28 2002 - 01:02:06 EEST
Hi John.
> Someone running Red Hat 6.2 had a similar problem with the install
> scripts. It was cured by changing the '==' tests to '='. I'm not
> sure why this was necessary.
At a guess, the install script was written on a system where sh != bash
either because the Bourne shell is installed on the development system
or because sh is a symlink to some shell other than bash (perhaps csh
instead).
Another possibility: on MOST systems, if a script doesn't explicitly
state which shell it is written for, /bin/sh is always used, but on SOME
systems, the login shell is used instead. This latter appears to be more
common where the login shell is not bash, so the choice of login shell
may affect this, but I can't state that I know the logic behind this.
My understanding is that this particular problem is the reason for the
tests to ensure that the current shell is bash in the Configure and
Menuconfig scripts for the Linux kernel, in which case this is obviously
a recognised problem.
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to imm.yaly@ktv.lt
More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Fri Jun 28 2002 - 02:16:03 EEST