Hi, I've downloaded both packages from here (http://www.slackware.com/~alien/slac...dk/pkg64/14.1/), tried both and, together or not, when I try to run java it says 'command not found', can't run java applets on firefox either.

The package installer frequently puts the necessary java executables in an odd place outside the normal path.

On a 32-bit system the executables jar, java, javac tend to end up in /usr/lib/java/bin, but function normally once symlinked to /usr/bin, where programs can find them. I suspect something similar is the case in your 64-bit system. Try finding where the necessary executables have landed and symlinking them to a more normal directory in your path like /usr/bin

1 members found this post helpful.

I am following a tutorial I've found and I am recompiling it, hope it works

Ok, recompiled openjdk and icedtea. Got the java plugin but still no java (it is not on /usr/lib/java/bin). That is odd because before reinstalling my system I installed openjdk before and everything worked.

Icedtea-web plugin is installed to /usr/lib(64)/mozilla/plugins directory.

icedtea is working, what is not working is java (when I try to run it on a terminal)

EDIT: As strange as it didn't work, now it is working.
PS: This thread was worthless, nobody learnt nothing lol I have no idea how it is working now.

The openjdk package (just like Slackware's own jdk package by the way) installs a profile script in /etc/profile.d/ which expands your PATH and MANPATH variables and sets a new JAVA_HOME variable. You have to logout and login again if you want to make that script effective.
Perhaps your original issues were caused by not having logged on again. The java binaries are in the directory which is added to the PATH.

Eric

It is probably that because I didn't do anything special and it started working.

EDIT: So, is Slackware bringing the Windows way of solving things to the Linux world?

Logging out and back in again is not the same as rebooting your whole system. Most things can be done in Linux without rebooting.

Wow, such a display of ignorance and insult...

If you think logging off and on again is too Window-ish then all you have to do is execute the following command in your console
to get the same effect (PATH and MANPATH updated and a new JAVA_HOME variable in your environment).

Naturally, this works for that specific console only. If you are running a X desktop like KDE, XFCE or similar and you want to have it working for every terminal window and all other apps, then you'll have to logout and login again, that is how the login profile works.

But then, since you escaped from MS Windows in the first place I expect that you are now sitting behind your console, not running X Window. My suggestion will work for you.

Eric

Jesus Christ people, no need to react that way. I didn't mean to offend nobody, it was just a joke (I even put a "" in the end to make it clear).