![update java 1.7.0_101 in linux update java 1.7.0_101 in linux](https://issues.jenkins.io/secure/attachment/33224/config.png)
This curiously failed when rebooting, with a strange "fan error" message. No use, gpk was still active, so decided to overkill
UPDATE JAVA 1.7.0_101 IN LINUX UPGRADE
So far this hopefullly alleviates the steadily recurring upgrade request of the gpk GUI, but I am somewhat uncertain whether this all is OK?
![update java 1.7.0_101 in linux update java 1.7.0_101 in linux](https://i.stack.imgur.com/Nip2O.png)
Prelink: /tmp/#prelink#.6Sf2tU: Recorded 2 dependencies, now seeing -1 Prelink: /tmp/#prelink#.o0Bf3k: Recorded 5 dependencies, now seeing -1 Prelink: Couldn't stat /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.181.x86_64/jre/bin/tnameserv: Permission denied Prelink: Couldn't stat /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.181.x86_64/jre/bin/servertool: Permission denied Prelink: Couldn't stat /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.181.x86_64/jre/bin/rmiregistry: Permission denied Prelink: Couldn't stat /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.181.x86_64/jre/bin/policytool: Permission denied On issuing the suggested "# mkdir -p /var/lib/rpm-state" command.
![update java 1.7.0_101 in linux update java 1.7.0_101 in linux](https://europepmc.org/articles/PMC5461230/bin/13321_2017_220_Fig3_HTML.jpg)
UPDATE JAVA 1.7.0_101 IN LINUX UPDATE
It becomes quite uncomfortable when selecting hourly update check (I do this for a reinstalled system only). Prior to installing or updating the package, create the /var/lib/rpm-state directory, as shown below # mkdir -p /var/lib/rpm-state