Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Okay after what seemed like three thousand hours of playing I finally got Java to work... For those who really want to give up don't and make sure you do the following...
create the symbolic link to: java/j2re1.4.2_01/plugin/i386/ns610-gcc32/libjavaplugin_oji.so
from within the Netscape/plugins directory. This is really important. When you are finished "ls" the directory and the link should be grey or pink or what ever color (I'm color blind) and not highlighted... That was my problem I was linking from the java/plugins directory and sending it to the netscape/plugins directory not vice versa.
I ls'd the directory and it shows the plugin in there, but it is white text with a red background, not sure about that. I closed out Mozilla and it didn't work. Hmm, I am going to look at the plugin preferences and see, but it doesn't show up in the about plugins.
Yea sorry about I think it uses the ns610 one... I run Netscape 7.1 which I found gives me better controls over popups and all around usage...
(that runs the ns610-gcc) So this whole forum was moot... go back and select the right plugin dir... rm the links and press the up arrow a couple of times until you get back into your old link command and change the ns610-gcc32 to the appropriate directory... ns610 I believe...
(hint: when your typing the directories just put a couple of letters and press the TAB button...)
And frank left the building... If I don't see ya good afternoon, good evening, and good night...
I had to install a newer version of Mozilla, here is what I found out.
On Linux, Mozilla requires JRE 1.4.2 or later.
Mozilla 1.4 and later, and Mozilla Firebird, are compiled with gcc 3.2.3. A gcc 3.x compatible version of the Java plugin must be used. JRE 1.4.2 contains a compatible plugin.
If you installed the JRE 1.4.2_01 RPM, this plugin is /usr/java/j2re1.4.2_01/plugin/i386/ns610-gcc32/libjavaplugin_oji.so - and to install it for Mozilla (including Mozilla Firebird), do the following:
* Open a terminal
* Change to your Mozilla (or Mozilla Firebird) plugins directory
* Issue the following command: ln -s /usr/java/j2re1.4.2_01/plugin/i386/ns610-gcc32/libjavaplugin_oji.so
If you are using an older Linux distribution, you may need to install the gcc3 support libraries, as the gcc 3.2 version of the Java plugin requires libgcc_s.so.1 to operate. You may be able to find packages using Google.
If you are using an old or unofficial build of Mozilla (1.4a or later) or Mozilla Firebird, you can check which compiler was used by entering about:buildconfig in the location bar and pressing enter. You will see a line such as "gcc version 3.3 20030226 (prerelease) (SuSE Linux)", which will show the compiler that was used. If gcc2.9x was used, you need to use the ns610 plugin, not the ns610-gcc32 plugin.