3 ms·
For what it's worth I'm always installing Java on Linux servers without using root rights (so no rpm, no .deb: rpms but good old tarballs). Certainly no "apt-g
by martinced 14y ago
For what it's worth I'm always installing Java on Linux servers without using root rights (so no rpm, no .deb: rpms but good old tarballs).
Certainly no "apt-get install whatever-jdk" for me. No, thank you very much. I want to be in control.
So I install the JRE (or JDK) in a user account and, once the .tar.gz file is decompressed/dearchived I do remove the unnecessary crap (examples, applets, etc.).
That's one big advantage right there about not needing to have admin rights to install: you know where all the files have been installed (in the user account, it's not possible to write anywhere else without being root) and you have more control on the crap.
That's not really possible to do as conveniently on Windows seen that you must have admin rights to install Java on Windows.
- rst 14y agoIf stuff isn't running as root, but still running as you, that still gives it access to a fair amount of private data. So, to keep really suspicious code from reading your banking details, etc., you need to run it under a different uid than the one that runs, say, your web browser.
- meaty 14y agoYes we do that as well. All java processes are given a single local user account. They have their own JDK installation as well. We even go as far as creating a new user account, deploying a JVM to it and wiping down during our build process so we get a consistent environment every time.
- RyanZAG 14y agoIf you're installing on Linux, rather install OpenJDK. Works like a charm, no more Oracle.