[newbie] LimeWire

[Bryan]

Success! Thanks to all for the help. The following command worked [sh
LimeWireLinux.bin]

What was wrong before I haven't a clue. LimeWire runs fine and I like it
much better than Kazaa. 

mandrakeusers.org is also a good source of info.

Regards,
Bryan

On Wed, 2004-05-19 at 11:23, Ron St-Pierre wrote:
> Bryan wrote:
> 
> >On Mon, 2004-05-17 at 16:46, Mark McLaughlin wrote:
> >  
> >
> >>Hi Bryan
> >>
> >>In a console window type: echo $PATH   
> >>When you press enter the current listing of your PATH variable 
> >>will appear, something like; 
> >>
> >>/usr/local/bin:/bin:/usr/bin     would be common.
> >>
> >>If these are missing from yours, add them via;
> >>
> >>PATH=[/path/to/executable]   no brackets
> >>
> >>Try your action again. If it still fails, you need to explicitly 
> >>add the directory that the Java VM resides in to this PATH variable. 
> >>So locate the Java VM executable app via something like
> >>whereis java, or locate java.
> >>
> >>For instance, run      locate java | grep bin 
> >>
> >>This should point to the javaVM executable, 
> >>which you may add to your PATH.
> >>
> >>
> >>HTH
> >>
> >>    
> >>
> >This was the response:
> >
> >[bryan@d206-116-45-87 bryan]$ echo $PATH
> >/usr//bin:/bin:/usr/bin::/usr/local/bin:/usr/X11R6/bin:/usr/games:/usr/lib/jre-1.4.2_01/bin:/home/bryan/bin
> >
> >[bryan@d206-116-45-87 bryan]$ locate java | grep bin
> >/usr/lib/jdk-1.4.2_01/jre/bin/java
> >/usr/lib/jdk-1.4.2_01/jre/bin/java_vm
> >/usr/lib/jdk-1.4.2_01/jre/javaws/javawsbin
> >[bryan@d206-116-45-87 bryan]$
> >
> >Should {/usr/lib/jdk-1.4.2_01/jre/bin/java_vm} be added to the path? If
> >so, how is this done?
> >
> Usually you need the /bin directory in your path and the top level java 
> directory as your java home.
> 
> >
> >Thanks,
> >Bryan
> >
> >_______________________________________________
> >Newbie mailing list
> >Newbie@vlug.org
> >http://vlug.org/mailman/listinfo/newbie
> >
> >
> >  
> >
> There are a number of ways to set environment variables, including the 
> path. One way is to edit your .bash_profile file in your root directory 
> using vim or some other editor (note the first character in the file 
> name is a period). Here is a sample .bash_profile:
> 
> postgres@asdf:~$ cat .bash_profile
> # ~/.bash_profile: executed by bash(1) for login shells.
> # see /usr/share/doc/bash/examples/startup-files for examples.
> # the files are located in the bash-doc package.
> 
>      if [ -f ~/.bashrc ]; then
>          . ~/.bashrc
>      fi
> 
>      PATH=$PATH:/usr/local/java/bin
>      PATH=$PATH:/usr/local/ant/bin
>      PATH=$PATH:/usr/local/pgsql/bin
>      PATH=$PATH:/usr/local/scripts
> 
>      export JAVA_HOME=/usr/local/java
>      export ANT_HOME=/usr/local/ant
> 
> You can create and export whatever environment variable you want and 
> then just refer to the variable names to access them (eg: echo $PATH). 
> BTW I've never used LimeWire, so I don't know whether or not it's 
> explicitly looking for the JAVA_HOME variable. Also be aware that the 
> changes you make in your .bash_profile will take effect the next time 
> you log in.
> 
> Ron
> 
> 
> _______________________________________________
> Newbie mailing list
> Newbie@vlug.org
> http://vlug.org/mailman/listinfo/newbie