SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Slackware will not be allowed to keep shipping JRE and JDK the way it used to (re-packaging the official binaries). But there are two alternatives to that: either Slackware will ship OpenJDK instead (compiled from source) or it will ship only a jre.SlackBuild and jdk.SlackBuild script which enables you, the Slackware user, to package and install the official Java binaries painlessly.
I vote for OpenJDK.
My reasoning is that no matter which one you choose, there would be someone who would like the other option. It would be easier for a third party to write a SlackBuild script that packages the Sun JDK than to write a SlackBuild that builds and packages OpenJDK.
OpenJDK is the obvious choice. I've read somewhere (I can't find a link now) that, previously, OpenJDK and the official JDK differed in the sense that they were different products, but the goal is to have the official Oracle JDK based on OpenJDK plus a few changes, so distributing OpenJDK would totally make sense, even if it's going to be a bit of a bumpy road in the first moments.
But if you read the new license especially the parts about redistribution and such, all they ask is the documentation and license files as well as the whole of the package remain intact for the redistribution. There is nothing specifically mentioned about the method or means of the redistribution, only things regarding package integrity.
Judging from what Alien Bob posted before you wrote the above, you appear to be mistaken.