Hi Everyone,
Years ago the recommended way to install Sun's java was to install from the tar.gz file because the RPM they supplied did some bad things (clobbered other files or something...can't remember the details). Is this still the case with Oracle's java RPM, or is it now safe to install?
Ranbir
On Fri, Sep 4, 2015 at 4:13 PM, Kanwar Ranbir Sandhu m3freak@thesandhufamily.ca wrote:
Hi Everyone,
Years ago the recommended way to install Sun's java was to install from the tar.gz file because the RPM they supplied did some bad things (clobbered other files or something...can't remember the details). Is this still the case with Oracle's java RPM, or is it now safe to install?
Ranbir
-- Kanwar R.S. Sandhu
jailed in a docker is safe to install,
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Kanwar Ranbir Sandhu Sent: den 4 september 2015 21:22 To: centos@centos.org Subject: Re: [CentOS] Oracle java RPM
On Fri, 2015-09-04 at 16:16 -0300, Itamar Reis Peixoto wrote:
jailed in a docker is safe to install,
Cool, but it doesn't really answer my question. :P
Since a few years back I always use the rpm. Works fine on my plain-vanilla CentOS-systems. YMMV as they say though.
On Fri, Sep 04, 2015 at 03:13:45PM -0400, Kanwar Ranbir Sandhu wrote:
Years ago the recommended way to install Sun's java was to install from the tar.gz file because the RPM they supplied did some bad things (clobbered other files or something...can't remember the details). Is this still the case with Oracle's java RPM, or is it now safe to install?
Since the Oracle Java packages are packaged by RH in RHEL, we use those packages. I kinda wish there was a way to get those Packages in CentOS too.
On 2015-09-04, Kanwar Ranbir Sandhu m3freak@thesandhufamily.ca wrote:
Years ago the recommended way to install Sun's java was to install from the tar.gz file because the RPM they supplied did some bad things (clobbered other files or something...can't remember the details). Is this still the case with Oracle's java RPM, or is it now safe to install?
I've been using the Oracle RPMs. From what I can tell they restrict their writes to /usr/java (plus making symlinks in /usr/bin).
--keith
On Sep 4, 2015, at 4:57 PM, Keith Keller kkeller@wombat.san-francisco.ca.us wrote:
I've been using the Oracle RPMs. From what I can tell they restrict their writes to /usr/java (plus making symlinks in /usr/bin).
Does it use the ‘alternatives’ system for the symlinks in /usr/bin? You can check quickly by looking at where the symlink /usr/bin/java points to, if it points directly to the java executable, then it isn’t using ‘alternatives’.
-- Jonathan Billings billings@negate.org
I use this :
http://awel.domblogger.net/7/special/repoview/oracle-java-jdk.html
It's a nosrc.rpm that makes an rpm from the x64 binary tarball.
You have to update the spec file for the actual version being used.
I don't know if it is the right solution for everyone but it meets my needs just fine, every new Java release I just build it on one machine and distribute the resulting rpm to my other CentOS boxes that need Oracle Java.
On 09/04/2015 12:13 PM, Kanwar Ranbir Sandhu wrote:
Hi Everyone,
Years ago the recommended way to install Sun's java was to install from the tar.gz file because the RPM they supplied did some bad things (clobbered other files or something...can't remember the details). Is this still the case with Oracle's java RPM, or is it now safe to install?
Ranbir
On 9/4/2015 12:13 PM, Kanwar Ranbir Sandhu wrote:
Hi Everyone,
Years ago the recommended way to install Sun's java was to install from the tar.gz file because the RPM they supplied did some bad things (clobbered other files or something...can't remember the details). Is this still the case with Oracle's java RPM, or is it now safe to install?
we're happy using the RHEL/CentOS provided OpenJDK 6 or 7, all our j2se stuff just works....
ok, we had one anomaly relating to figuring out the local time zone, long story short, the lowest impact fix was for root to
# echo "America/Los_Angeles" > /etc/timezone
(using your local canonical timezone name, of course!)