![]() |
|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
Other For questions about installing LimeWire or WireShare on alternate operating systems NOT including Windows or Mac. (Such as Linux variations.) |
![]() |
| LinkBack | Thread Tools | Display Modes |
| |||
![]() The problem turns out to be due to some '\r' characters in the "runLime.sh" script in the new version. I had an older version (4.12) of LimeWire working on Linux, but when I tried to install and use LimeWire version 4.14 I got the exact behavior that you described. When I replaced the "runLime.sh" script in the new version with the corresponding script from the old version, the problem went away. The files look the same to the eye, but examining them using "od -c" shows the following: OLD runLime.sh (LimeWire 4.12, good): 0000000 # ! / b i n / s h \n # \n # R uNEW runLime.sh (LimeWire 4.14, bad): 0000000 # ! / b i n / b a s h \r \n # \r \nYou can see the '\r' characters that are causing the problem. The simplest solution would be to grab the runLime.sh script from an older (working) version of LimeWire, if you can. Otherwise you can try to get rid of the '\r' characters (the "tr" command would work, as would a sed script). |
| ||||
![]() Don't appear to see the 'r' problem: #!/bin/bash/ # # Runs LimeWire. This script must be executed in your LimeWire # install directory. # this should allow starting limewire from # gui-based explorer interfaces cd "`dirname "$0"`" # try to discover java MSG0="Loading LimeWire:" MSG1="Starting LimeWire..." MSG2="Java exec found in " MSG3="OOPS, your java version is too old " MSG4="You need to upgrade to JRE 1.5.x or newer from http://www.java.com" MSG5="Suitable java version found " MSG6="Configuring environment..." MSG7="OOPS, you don't seem to have a valid JRE. LimeWire works best with Sun JRE available at java.com: Hot Games, Cool Apps " MSG8="OOPS, unable to locate java exec in " MSG9=" hierarchy" MSG10="Java exec not found in PATH, starting auto-search..." MSG11="Java exec found in PATH. Verifying..." look_for_java() { JAVADIR=/usr/lib/jvm if look_for_javaImpl ; then return 0 fi JAVADIR=/usr/lib if look_for_javaImpl ; then return 0 fi JAVADIR=/usr/java if look_for_javaImpl ; then return 0 So any other ideas ? |
| |||
![]() Well, if you're just looking at the file on the screen, the '\r' (0xd, "carriage return") won't show up -- you'd need to look at the individual characters in the file, e.g., using the "od -c" command. If you want, you can drop me your email address and I'll email you my working copy of that file. Of course, if you're half as paranoid about security as I am, you wouldn't accept a shell-script mailed to you by a total stranger ![]() |
| ||||
![]() OK, that explains things a little clearer. I'll go RTFM re ' od ' to learn about it some. As to your offer ~ will meet you 'half way'. ![]() Er... that is ~ my email address cannot be printed here ( good security by the moderator ) ~ please include it here, and I'll change the extension this end. Thanks for the offer, greatly appreciated. Quick update: I see I do need an earlier copy of the runLime.sh file to be able to compare. Though the od -c command would normally be a little over my head, your comments earlier has helped to see where the changes might be. ________________________________________ Edited to comply with the House Rules. Do not divulge anyone's personal information in the forum, not even your own. Last edited by Snapafun; August 16th, 2007 at 08:06 PM. Reason: Took a look at the od command man page. |
![]() |
| |