Since I believe the Sun Java installation docs suggest adding
"PATH=$PATH:/usr/local/jdk1.x/bin" to /etc/profile, which will still
leave /usr/bin/java ahead of the JRE most people know about, it seems
like the Gnu package is potentially a landmine in other instances as
well. It seems like /usr/bin should be ahead of the Java
installation's executables path as a general rule.
Again, thanks very much for the help, Fernando.
--- Fernando Nasser <fnasser@xxxxxxxxxx> wrote:
> Dennis King wrote:
> > Thanks, Fernando. Can you tell me how I set the path correctly?
> >
> > I only posted this after I sent email to Red Hat support through
> > their Red Hat Network pages and didn't hear back.
>
> I am not sure where your mail went.
> Just use the rhdb@xxxxxxxxxxxxxxxxxx for Red Hat Database problems.
> This one I know we are subscribed to.
>
>
> > The "Using Red Hat Database with JDBC" tutorial also makes no
> mention
> > that there could be a conflict with the Sun JRE it instructs you
> to
> > install and assumes you use.
> >
>
> I guess this was written long before gcj started to install a
> /usr/bin/java (pointing to gij, I believe), which happened just now
> in
> 8.0. You are right, it needs updating. I will get that patched.
>
>
> Just make sure you have your $JAVA_HOME/bin directory ahead of
> /usr/bin
> so that the 'java' command that you get is the one from the Sun
> SDK, not
> the one installed by gcj.
>
> --
> Fernando Nasser
> Red Hat Canada Ltd. E-Mail: fnasser@xxxxxxxxxx
> 2323 Yonge Street, Suite #300
> Toronto, Ontario M4P 2C9
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
majordomo@xxxxxxxxxxxxxx
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)
|
