Eric Iverson wrote: > 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.
> 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? I don't think there is an easy way around this, but I would not worry about it. I am running Fedora 6, a relatively recent version of Linux. This comes with gcj, which I do not have configured correctly. I have installed Sun 32-bit and 64-bit Java, and Blackdown Java. I use all three: the Sun versions for normal Java, and the Blackdown version for a 64-bit browser plugin. Even if you reset the defaults using the alternatives mechanism, the java command will only run one of these, and it will not change from 32-bit to 64-bit automatically. I do not believe there is a standard way of distinguishing these cases, even within a Linux distribution; however, installing or upgrading Java requires setting paths, so a user can reasonably be expected to edit the jwds (and you probably want to put absolute path names in both). In my case it took less than a minute. Best wishes, John ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
