Rajesh Kartha <[EMAIL PROTECTED]> writes: > I had some questions on the scripts residing under the new /bin directory:
[...] > 3) On Linux > ========= > (a) After unzipping the db-derby-10.2.1.3-bin.zip on Linux the > permission on the scripts in /bin is only readable > (b) In the bash shell, when I try sysinfo (after changing the > permission on sysinfo and derby_common) I am seeing the following: > > bash-3.00$ bin/sysinfo > Error: DERBY_HOME is not set. Please set the DERBY_HOME environment variable > to the location of your Derby installation. > bash-3.00$ export DERBY_HOME=/local1/rajeshk/derby/db-derby-10.2.1.3-bin > bash-3.00$ echo $DERBY_HOME > /local1/rajeshk/derby/db-derby-10.2.1.3-bin > bash-3.00$ bin/sysinfo > : command not foundby/db-derby-10.2.1.3-bin/bin/derby_common.sh: line 2: > : command not foundby/db-derby-10.2.1.3-bin/bin/derby_common.sh: line 10: > : command not foundby/db-derby-10.2.1.3-bin/bin/derby_common.sh: line 12: > : command not foundby/db-derby-10.2.1.3-bin/bin/derby_common.sh: line 19: > /local1/rajeshk/derby/db-derby-10.2.1.3-bin/bin/derby_common.sh: line > 27: syntax'error near unexpected token `in > /local1/rajeshk/derby/db-derby-10.2.1.3-bin/bin/derby_common.sh: line > 27: `case '`uname`" in > bin/sysinfo: line 29: exec: : not found > > Is anybody else seeing issues (2) and (3) ? Yes, I see the same problems on FreeBSD (I used the bin.tar.gz distribution). When I removed all CRs from the scripts and set the executable bit, they worked. I think we need some svn magic (svn:executable and svn:eol-style?). -- Knut Anders
