|
NOTE - before you go through this, read the comments to this post below. The comments indicate a far easier methodology to install Java. Sorry it's ben so long, and now I have something useful to contribute. I spent most of the past week, flat on my back following Sinus surgery. Hopefully, now I can just get well. I've had a cold (or at least feels and looks like one - sinusitis) since September. Things are really looking better since the surgery, and I can already breathe.
But in my heyday, I promised a better review and understanding of Songbird. What I had running was so far superior to even iTunes, I think it warrants implementation. The bad news is, I'm not there, just yet. The good news is I think I now know why it worked so well when I first found it, and then why it failed to meet my expectations the next time I visited the application. More on that later, but for now, I want to shed some light on Java install under Debian. So, like a good newbie, I follow the link to the Java page, where it explains what is open or closed code, and all the good stuff we all love to hate (license agreements). Anyway, I tried following their instructions, and I am not overly familiar with file commands in Debian, or Linux for that matter. So, I want to share what I felt was quite a few subleties, and hopefully an inspiration or two. First, the should be easy stuff that I don't always know or understand. The first couple of commands in the Java page for installation require you download a binary file (extension of bin). that was fairly straightforward. Then my fun began. Since Lenny now has a root terminal (I am guessing this is the issue), the first commands to change the access structure of the file as copied failed for me. So I eventually opened the file in the file browser (Applications - System Tools- File Browser)and here I could open the properties. From here, I went to permissions, and set the file to read and write for all entries (likely overkill, but it allowed me to now work with the file). I then moved the file from my desktop (default storage from the downloader) to my actual /home/username file. This allowed me to actually set up a link that would run the file. Just drag and drop the desktop file into the places I then changed directory over to my /usr/local/ area. cd /usr/local/ When I issue the next command from this directory it will allow Java to run anytime I use the machine. Since I only have 1 user account, this works for me. From here you run the binary install program from Sun(I was in the root terminal): /home/yourusername/jre-6u13-linux-i586.bin This runs the binary (spacebar through each reiteration of the more for the license agreement, yes to install at the end) and voila, once complete you should have a folder in the /usr/local/ file called/jre1.6.0_13/ At least today, for release 13 of Java 1.6.0. That's it for the install, except now you need to link the file, so your browser knows how to "see" or "enable" the java runtime. For all new versions of Firefox (Iceweasel for Debian) you move to the correct directory (BIG NOTE HERE - these commands are changed from the Sun Java pages, and the file reference build is a jre1.6.0_13. From my printout, it appeared to be an l, not a 1. make sure you use the number, not a letter): cd /usr/lib/iceweasel/plugins ln -s /usr/local/jre1.6.0_13/plugin/i386/nc7/libjavaplugin-oji.so This ties the Java runtime program in the /usr/local/ file over to the Iceweasel plugin base. This is also where I ran into an undocumented issue. You see, there can only be one Java file linked in to the install at a time. So when I went to the /usr/lib/iceweasel/plugins file, I discovered two similarly showing files with bad links. So once again, in the root terminal, I deleted the two bad link files, restart Iceweasel cd /usr/lib/iceweasel/plugins rm libjavaplugin.so rm ns7.so shutdown Iceweasel and then restart Iceweasel and now Java works! Till next time, ezsurfer
|
Blog Pushes
| 
. It may or may
