Yep, it has been a while. I used the defaults and that worked fine. But when I try to use firstboot to set nvoc_path to just /home/m1, it goes craptastic (same errors as post above) and I am left with a base Ubuntu install. Why give people the option to set it if it doesn't work? The recompile miners and expand disk options did work fine, however.

The other bug that I wanted to point out is that if while running REMOTE, on the console, every time I open a terminal it tries to re-run nvOC. I didn't dig into the details but whatever launches that should check to see if it is already running. All that I wanted to do was open a terminal to troubleshoot miner startup issues right there on the console without having to ssh in from another machine.

Enough with the bad, what is really cool is the reorganization of 1bash and the total rewrite/streamlining of 0miner. It took me a few minutes to figure out what is going on with 0miner as it is such a deviation from the very repetitive old version. Kudos on that. The downside is that adding a new miner that doesn't fit the mold of an existing algo is quite cumbersome. However, I don't figure most people would ever need to do that.

But overall, great job to the team. I am pleased to see how much progress you guys have made.