A serious nuinsance in J linux installs is getting jwd to start. The
distributed jwd shell script for both J32 and J64 runs command java.
This depends on java being in PATH and matching (Java 32 for J32 and Java 64
for J64).
My Suse system is quite old (earliest 64 bit version). It came with java for
Java 32 on the path and J32 jwd runs out of the box. But I had to install
Java 64 later on and there were no suggestions so it just sits in home and I
have to manully edit J64 jwd to have the fullpath to the Java 64 java
binary.
My impression is that modern linux systems have Java 32 java binary in the
path and that J32 jwd starts OK. And if it doesn't, it probably takes local
knowledge to fix and it isn't reasonable for the install to try to be
smarter.
Do modern linux64 systems come with Java 64 installed such that there is a
standard way for running the java binary? Something that was standard enough
that it made sense to hardwire into the jwd script so as to increase the
chance that J64 jwd would run out of the box.
Feedback on how to best invoke Java 32 and Java 32 on modern linux systems
would be appreciated.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
