Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
OK adding a coin, but how is profitable to mine DSR
?And i want to tell all that unimining.net had some saturation on neoscrypt pools. I tried to mine GBX at this pool and they can't provide me any blocks to mine.
in additions :
1/ I'm not sure that all of us have a folder named KTccminer-817 in /home/m1
2/ I think there is a "typing error" in the command line
Code:
-o stratum+tcp://$DSR_POOL:$DRS_PORT
must be
Code:
-o stratum+tcp://$DSR_POOL:$DSR_PORT
You have to be more precise an readable in your post. You can post a modification understandable and easy to do without being a computer scientist or a computer technician. This system is named "easy to use" for reminder.
Thanks for adding.
You 're right sorry for the typo,
A patch is the easiest way to do the modification, you don't even need to know where to put the lines in the patched file.
just do
patch -p0 < file_with_the_patch
fastest than anything
KTccminer 817 was posted few days ago here by Papampi
I don't know if this coin is profitable, I just want to mine some so made the modification and shared.
Code:
patch -p0 < file_with_the_patch
I just do not understand what it means.
KTccminer 817 was posted few days ago here by Papampi
That's right, but I do not know if you noticed that the main coders are trying to maintain a naming convention with a special method for updating minors.
For example, the latest update proposed by papampi included a script to update the DSTM or ZM software in several steps that I will briefly describe below:
1 / DL in the folder Downloads / miners
2 / creation in the zec / zm folder of a folder 5_8
3 / copy of the latest version in Dwonloads / miners in this folder 5_8
4 / copy to the latest folder of the necessary files in the folder / zec / zm / latest
Similarly, version numbers were not added to the first folder containing the minor for Klaust's software. AInsi, your naming proposal from KTccminer will cause problems for other people who do not have it in this form.
This can create confusion. Better to stay in the starting naming conventions otherwise every update will cause problems.
So I think it's best if the KTccminer8.17 path is written like this /home/m1/KTccminer/ccminer