nvOC 19 2.1 beta testing

This guide is outdated. Do not follow this guide if you are not using the old 2.0 stable image. If you need a full image get a new one from the latest release branch: https://github.com/papampi/nvOC_by_fullzero_Community_Release/blob/release/README.md

If you are using this guide as a reference for side-by-side installs on newr branches here is an updated and general version: https://github.com/papampi/nvOC_by_fullzero_Community_Release/wiki/nvOC-setup-from-a-git-clone

---

Test/run nvOC 19-2.1 beta in existence with 19-2.0 stable.

Beta testing and upgrading is only possible if you have access to local machine to edit gnome-terminal profile.

Step 1:

git clone --depth 1 --branch 19-2.1 https://github.com/papampi/nvOC_by_fullzero_Community_Release.git /home/m1/NVOC/testing

cd /home/m1/NVOC/testing

git submodule update --init --depth 1 --remote miners

cd miners

bash nvOC_miner_update.sh

Edit your new 1bash: /home/m1/NVOC/testing/1bash

Step 2:

Create new gnome-terminal profile and start up command:

gnome-terminal menus: Edit > Preferences > Profiles > Clone the mining profile and edit the clone.

Rename the cloned mining profile to "mining-beta", "mining-testing" or whatever you like.

In 2nd tab from left, "Command" change custom command.

from :

/home/m1/2unix

to:

/home/m1/NVOC/testing/2unix

Choose the "Profile used when launching ..." to the one you made.

Step 3:

It's better to reboot, to start fresh.

But you can also do:

./nvOC stop

gnome-terminal will be closed, open it again, it should start with the new profile.

Switch back

To switch back to 19-2.0 stable just change the "Profile used when launching ..." in gnome-terminal profiles. If you are in a remote situation and you don't like TeamViewer you may find this script helpful https://pastebin.com/sxegp8C4

Updates:

Updating your nvOC to the latest updated version is now really, really easy. You don't need anymore to wait for update scripts to be released, the update is faster and your miner will be stopped for a very small amount of time just if really needed.

• If you only customized 1bash and the first git pull command below raises no conflicts you can simply follow next few steps.
• If in the updated version there are structural changes to 1bash, or any other script file you may have patched/customized, it's likely that the git pull will raise conflicts. In such a case you have to take a copy of your modified files, either remove them from the testing directory or git stash them, and repeat the git pull command.

Basic and easy nvOC update steps:

cd /home/m1/NVOC/testing

git pull origin 19-2.1

Update nvOC/miners to latest commit:

cd /home/m1/NVOC/testing/

git submodule update --depth 1 --remote miners

cd miners

bash nvOC_miner_update.sh This last step above will also propose you to recompile miners of you know you need it. Only In such cases, the miner sources are directly pulled from their developer repository.

Always keep a copy of your 1bash (old, new, beta, ...) in a safe place.

Please post your issues and found bugs as GitHub issues.