No idea. Some repository or other; I tried various combinations of numbers and jre/jdk in the apt-get instruction Ron showed you and they all seemed to work.
Terrance Samson wrote:. . . where exactly is the OpenJDK 8 package? And the JRE too
Afraid it does. You can download openJDK as a .tar.gz file from the standard download link You can probably get a Java8 JRE but they withdrew the separate JRE for Java11+. Put the .tar.gz onto a USB thumb drive/memory stick and unzip it from there, and update JAVA_HOME as per usual.
. . . . does not have access to the internet. I don't know if that affects anything.
Terrance Samson wrote:How do I decompress/extract the files from that? Or should I do it in Windows and then just take those extracted files and put them in Java? Or can I even do it in Windows?
Follow the link Rob posted. Also consider trying the 7‑zip program; it occupies <1MB of download and works really well, but most Linux installations include apps to handle 7z files as a default. Assuming you have the .tar.gz in Downloads, try this sort of thing.Depending on the permissions of your locations, you may need sudo too. You probably need to open the terminal anew to see the new version numbers (lines 4‑5).
Terrance Samson wrote:. . . How do I decompress/extract the files from that? . . . .
Yes . . . No
Terrance Samson wrote:. . . NetBeans . . . an IDE like Eclipse . . . So then would I need to install that just to run Java programs . . .
Don't know. Use man tar and see what it tells you.
- I've seen the zxvf written with the "-" before it and without. . . .
use whatever text editor I have . . .
It probably won't have JAVA_HOME and PATH in at all; you will have to add them both. If you don't use NetBeans, you can probably telescope the two into export PATH=... and omit JAVA_HOME.
open the file called "~/.bashrc" and then find where it mentions "JAVA_HOME" . . .
You can't do any harm with update, but inflating the .tar.gz doesn't require update at all.
. . . update twice? . . .
It means the new entry coems first, as I wrote it. It means that directory is searched first when looking for java, javac, etc. Otherwise there is a risk of finding multiple installations with mutually conflicting version numbers.
. . . Do you mean the beginning of the line of text? . . .
It adds the new entry to the previously set PATH for the purposes of the current terminal.
. . . PATH=$PATH... does that append the path variable . . .
It means rather than writing two lines as I showed earlier, you write export PATH=/my/path/to/java/jdk8_261/bin:$PATH or similar.
Terrance Samson wrote:. . . you can probably telescope the two into export PATH=...", . . .
First time for everything; nobody else thinks what I write makes sense
I'm pretty sure it makes sense. . . .
It should look just like Java® developed on a Windows® partition.
I may yet develop using Java on a Linux partition . . .
Terrance Samson wrote:Thanks for clarifying that line. And I've heard all about Java working the same in all circumstances (I guess as long as you're not relying on DLLs compiled in C or something), but I don't think I've ever seen it before, so that will be interesting. Anyway, thanks again!