the letter is like the version number, m > k
You need to download the file for your architecture and extract it. There's a yam-mmc.cfg inside the tar. Modify that file to use your addresses and upload it to your own dropbox account. Upload the tar too.
Then, modify the script to use your dropbox urls and the file/foldernames for your chosen architecture. You can add a cd ~ after #! /bin/bash to be sure it's happening in your home folder.
It seems that I start to wake up now... LOL!
So, I have to edit this adding my own addresses and I’m done:
threads = 0
mining-params = mmc:av=1&aesni=on&m=1024
mine = getwork://MTb1JHjoJCSJBjTLUgqeyJ1nXxYxBRJEUX@work.mmcpool.com:80:8880:8881:8882:8883/mmc
mine = getwork://MSkLPYJQuskzp8wNqvZCpiTNYw7pJ83zGe@mmcpool.1gh.com:8080:8081:8082:8083/mmc
mine = getwork://yvg1900.mmc_1:x@mmc.gpools.com:8080/mmc
#proxy = socks4a://127.0.0.1:9150
compact-stats = 1
print-timestamps = 0
Final questions
1. If I create a droplet with 4 CPUs do I have to edit the “threads = 0” or something else?
2. Since I’m creating clouds to services like DigitalOcean, HP Cloud and Windows Azure, will yam-yvg1900-M7m-linux64-sandy-bridge.tgz do for “my” architecture?
Big thank you to all of you that help!