Hello guys,

I was looking into bash template here https://github.com/papampi/nvOC_by_fullzero_Community_Release/blob/release/1bash.template

I would like to use ethermine.org and I did not find option how to setup it for this pool. Is it possible or this OS works only with zpool, nicehash and miningpoolhub?

I was thinking if I can add my pool here, I'm not sure

ALT_POOL="NO"               # YES or NO, Set to YES if you want to enable  poolswitch.
                            # Switch to alternate pool if main pool goes down.
                            # Dual mining and salfter auto switch not supported.
                            # If pool goes down, poolswitch will stop/disable wtm auto switch and will enable/start it after pool comes up to prevent coin data mixed up.
                       # If main pool use username, alternate pool should use same username and workername.
                            # If anonymous mining with coin address alternate pool should use same.
                            # If ALT_POOL="YES" add as follow to your coins data (order should be the same).

###alternate pool setup example:
#ZCL_POOL_1="europe.equihash-hub.miningpoolhub.com"
#ZCL_PORT_1="20575"
#ZCL_POOL_2="zcl.suprnova.cc"
#ZCL_PORT_2="4042"
#ZCL_POOL=$ZCL_POOL_1  #Dont edit this
#ZCL_PORT=$ZCL_PORT_1  #Dont edit this


Thanks for advice ;-)

Just out of curiosity
Is anyone mining BCI and
what is your setup for this?

You renamed 1bash.template to 1bash,
Just remove 1bash.template, run the upgrade command again

Sorry forgot to mention to update miners after update nvOC.
Run miner upgrade command (No need to recompile, it will take very long time):

Guys, thank you both for the support, I greatly appreciate it.
There must be something basic I am missing.
When I run the command:


I get a usage list like this:

https://image.ibb.co/mTqEzJ/error1.jpg

Any guidance you guys can provide?

Thanks again for all the help!  

Hi,
With git version, on nvOC restart (or nvOC start-service), I have:
And I don't find any log about this.

Try this:

I try nvOC install-service because I have a lbocking problem with reboot:
And I thought installing (and stopping) nvOC as service could resolve it.

edit: note that I try all the known ways to (ssh) reboot linux and none works. I didn't even know it was possible!

@parentibule you messed up something, I see you are running commands from an home directory of an user named 'm1_2.1'. Have you intentionally did this or you were just trying to put nvOC into a different folder? If you know how Windows users profile works, you know that there exist a folder for each user in C:\Users\ for example my user folder is C:\Users\LuKe. In Ubuntu that is the same thing but every user has a folder inside thehome directory, so in nvOC images the default user is 'm1', therefore exists a folderhome/m1 which is the place where all user files need to be. If you created a new user named 'm1_2.1' then it is correct that suchhome/m1_2.1 folder exists, but in such a case you did a horrible choice in placing nvOC files inside his home folder because Ubuntu uses that folder to store all system files related to that user, that's why the default location for nvoc files in prebuilt images is '/home/m1/NVOC/something',home/m1 is the home folder for m1 user, NVOC is just a folder like any other. If, instead, you choosed to place nvOC files inside an arbitrary folder namehome/m1_2.1 but you created no user named m1_2.1 then you did a mistake, reinstall nvOC into another folder. Remember that the default m1 user is a NOPASSWD sudoer, he can reboot doing 'sudo reboot' without being asked for credentials. Don't care the nvOC as a service mode, it is an alternative to gnome for who really needs it.

@Ventero I don't understand which kind of "settings" for claymore you are in search of. It is just a miner, the only things you need to set are the pool and the algorithm you intend to mine and it is done automatically by nvOC when you set COIN="ETH" and related ETH_* settings. You don't need nothing else in most cases. Try start mining and see the miner command line built up by nvOC in the miner log window, if you see there are some missing arguments come back here to ask why a certain argument is not set correctly, but I don't tkink this could happen to you with a well supported miner like claymore. Let me know.


The instructions you are referring to explain how to configure and customize the prebuilt image setup. Most people would be fine with defaults. firstboot.json file configures the very first boot of your rig during which nvOC is installed and then it is never ever used again in your rig lifespan. 1bash contains settings for nvOC. During the first boot the 1bash file you palce in the small fat partition is imported to the nvOC installation when it is ready.


The auto_expand option enables the Ubuntu disk partision to be enlarged (during firstboot) up to the entire disk sapce. The prebuilt image you download is small to fit various drive sizes. If you do not a lot of free space available on your rig ubuntu partition leave it to false.

Compiling a software means you take its source code (written in some programming language) and build again from sources the executable binary (think to .exe files in windows). nvOC comes with a set of already compiled miners, some of them are open source, we have the source code, some other are closed source, the source is secret and only the author has it. Therefore you can recompile only open source software or that one you authored. You don't need to recompile open source miners you find in nvOC unless the the compiled version is not compatible with your platform/runtime. Finally, claymore is a close source miner, nobody can recompile it. When someone install nvOC on a lagre number of rigs where he already knows in advance that a recompilation will be needed, he may find usefult to instruct the firstboot setup to do it before starting to try mining otherwise it will fail and he will need to manually recompile the miner on each rig. Compiling a miner require a lot of disk space to store sources and various files generated during the compilation, so it is usually needed to also enable auto_expand in such kinf of scenarios.

Long story short: you just need to write the image to drive, download a 1bash.template from github, customize it with mining-related settings (start by only setting coin and mining pool) and place this shiny 1bash file in the small fat partition. And boot the rig. That is why this thread title includes "easy-to-use"

  I don't know why I done this! It's clearly totally stupid :/ Thanks for your explanations.