myDSL Extensions (deprecated) :: New Extensions in Testing - March 2005



In regards to the limewire.dsl,

It works great.... once it's running.  I have to open an xterm and type
Code Sample

PATH=$PATH:/opt/jre1_5_0/bin limewire

to get it to start.  After that it's great.  And if you add home/dsl/.limewire to filetool.lst, all of the settings will be backed up for the next session.

josh
ke4nt; one testing .dsl you kindly put together but which didn't work for me and some others was iScribe.dsl.  There is a 'cannot  connect to the network' 'socket 34' problem which is not inherent in your conversion but to some linux distro's generally.  ie. the linux version installs to some other distros with the same problem.  
The developer has confirmed it as his no.1 bug fix for the Linux version.
I still think that with it's small size, pop server preview, and calender feature, this has more bang for it's bucks than other e-mail options that I have come across in playing with DSL. Especially for old hardware.
It would be nice if somebody could shed some light on a workaround that could make this useable.
Quote (jshaw @ Mar. 16 2005,22:41)
In regards to the limewire.dsl,

It works great.... once it's running.  I have to open an xterm and type
Code Sample

PATH=$PATH:/opt/jre1_5_0/bin limewire

to get it to start.  After that it's great.  And if you add home/dsl/.limewire to filetool.lst, all of the settings will be backed up for the next session.

josh


I encountered this issue as well; when I clicked on the icon nothing would happen, and when I opened an xterm and ran it said it couldn't find java.
I did add /opt/jre1_5_0/bin to my path and it does work. Question is, I wanted to have this done for me behind the scenes, so I tried this:

1) Created a script:
Code Sample

#!/bin/sh
export PATH=$PATH:/opt/jre1_5_0/bin
/usr/bin/limewire


(note, I'm not running DSL now, so the paths may not be correct, but they were when I tried this)

2) Modify .xtdesktop/limewire.lnk so it will run this script instead of directly calling limewire

But this didn't work. Any idea why, and what else I could try to get the PATH changed automatically?
thorzul,

I've searched the forum for ways to change the PATH globally, but appearently there isn't a way to do this.  Just change the path in the link to
Code Sample

PATH=$PATH:/opt/jre1_5_0/bin limewire

and the link should work.

josh
Quote (thorzul @ Mar. 17 2005,13:54)
Question is, I wanted to have this done for me behind the scenes, so I tried this:

1) Created a script:
Code Sample

#!/bin/sh
export PATH=$PATH:/opt/jre1_5_0/bin
/usr/bin/limewire


(note, I'm not running DSL now, so the paths may not be correct, but they were when I tried this)

2) Modify .xtdesktop/limewire.lnk so it will run this script instead of directly calling limewire

But this didn't work. Any idea why, and what else I could try to get the PATH changed automatically?

Is your script executable? chmod 755 /path/to/script
Next Page...
original here.