Mafia, Dropbox and Ubuntu
- Thread starter Lxndr
- Start date
I seem to have some vague recollection that -DuseCWDasROOT=true needs to go before kolmafia.jar.
xKiv
Active member
I just did
from command line, and it ran ... but it doesn't work:
... got it, Boolean.getBoolean("x") only returns true when the value of x is true ...
so you need to
instead ...
(and the -D... can't be after the jar, because that would be an argument to the mafia application instead, and you want an argument to java itself)
ETA: try running that (with the correct path to your .jar) from command line - what does it say?
Code:
java -DuseCWDasROOT -jar KoLmafia-12892.jar
Code:
KoLmafia v16.0 r12892
Released on May 17, 2013
Currently Running on Linux
Local Directory is /home/xkiv/.kolmafia
Using Java 1.7.0_25... got it, Boolean.getBoolean("x") only returns true when the value of x is true ...
so you need to
Code:
java -DuseCWDasROOT=true -jar KoLmafia-12892.jar(and the -D... can't be after the jar, because that would be an argument to the mafia application instead, and you want an argument to java itself)
ETA: try running that (with the correct path to your .jar) from command line - what does it say?
Hate to be a bother, but could you walk me through how to do a shell script in ubuntu?
xKiv
Active member
The important things are:
1) it's a text file that cointains a sequence of shell commands (like on the command line), one for each line. [1]
2) it should be executable (that's what the chmod +x !@#$ does), otherwise you can't execute it directly
3) the #!/bin/bash on the first line is nice, but not necessary
4) don't torture yourself with vi (or emacs, or ed) unless you are already comfortable with it
ETA: [1] this is a "lie to the children" - commands can span multiple lines, and there can be multiple commands on a single line, and there are subtle differences between putting something on a command line and putting it in a shell script; but the general idea is a good starting point
1) it's a text file that cointains a sequence of shell commands (like on the command line), one for each line. [1]
2) it should be executable (that's what the chmod +x !@#$ does), otherwise you can't execute it directly
3) the #!/bin/bash on the first line is nice, but not necessary
4) don't torture yourself with vi (or emacs, or ed) unless you are already comfortable with it
ETA: [1] this is a "lie to the children" - commands can span multiple lines, and there can be multiple commands on a single line, and there are subtle differences between putting something on a command line and putting it in a shell script; but the general idea is a good starting point