On Monday December 15, 2003 Chris A Czerwinski <chrisczerwinski@xxxxxxxxx> wrote: > On Sun, 2003-12-14 at 22:19, Robert G. (Doc) Savage wrote: >> Dave, >> >> Here's a micro-howto I use. It includes instructions for either J2 >> Runtime Edition or J2 System Developer's Kit. Pick one. [snip] >> >> That's it. > > or is it? > > Hi Robert (Doc), > > Great intro to -howto? that's what I like to see for me a newbie at > Fedora, not just "man" something or see link url. These finer points are > what newbies can appreciate and follow instructions and realize that's > it's not just RPM. Not all RPMS are thorough and do what people think > they should simply do. Newbies can now get their linux legs started. > > A couple of questions to a newbie (me especially) on using RPM's. > > How do you know you have Java and which version or want to upgrade? There are several ways to tell. 1. Search your (biological) memory. Do you remember installing it? :-) 2. $ /usr/java/j2sdk1.4.2_02/bin/java -version java version "1.4.2_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03) Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode) 3. In Mozilla click on Help -> About Plug-ins and look for: Java(TM) Plug-in 1.4.2_02-b03 File name: libjavaplugin_oji.so Java(TM) Plug-in 1.4.2_02 > Should you not check to see if you have Java installed? > and what would that command be ( > rpm -q java) ??? There's a trick here, and that's knowing to search for 'j2' rather than 'java': $ rpm -qa | grep j2 j2sdk-1.4.2_02-fcs > And if you have it, what would be the appropriate command for upgrade ( >> rpm -u or -U *.rpm) Actually I like to use -F (for 'freshen'). Think of this as an enhanced -U upgrade: # rpm -Fvh newrelease-X.X.X.i386.rpm > About plugin's - will you still have to modify the links (ln)? and will > the links stay on reboot? If you install the link in the generic /usr/java/mozilla directory, you will not have to re-install after each Mozilla upgrade. If you install it in the specific /usr/java/mozilla-xxxx directory, it won't be available to an upgrade. Simple as that. > 2nd last point, how can I test to see if Java is executing the proper > version or has been installed? Which comes back to the first question? Asked and answered. > Lastly, how do I do a cleanup or remove old/previous version of Java or > I don't - because there may be programs that have been linked to this > dir? If you upgrade to a later J2 release, RPM will take care of the housekeeping. The same is true if you use RPM to remove the current version prior to a fresh install. Remember to use 'rpm -qa | grep j2' before running 'rpm -e ___' to get the exact name of the J2 package to remove. As stated above, if you link to the generic /usr/java/mozilla directory, your new Mozilla will have access to your installed java. RPM is your friend. Spend an evening with 'man rpm'. Do the same with 'up2date'. Then look in the list archives to see how to install 'apt' and 'synaptic'. As good as RPM and up2date are, apt is better. ***** Now, some non-java stuff for newbies: 1. Be kind to list members with limited bandwidth and trim away all excess from your replies. 2. Put your replies at the bottom. Top posting excites several members. 3. Don't change the subject without changing the Subject:. 4. Lurk, search, and read before posting. You'll learn a lot for free. Hope this helps.... --Doc Savage Fairview Heights, IL
