Not sure how policies is a moving target? You can also just disable the windows update service if you don’t want to mess with policies.
Windows does indeed have licensing costs, but when you’re spending $1500 on a rig that’s not really that much. In addition to being able to have a system with more then 6 GPUs. There are less savy ways of acquiring Windows as well, which I’m sure no one here is familiar with. Either way, it’s worth it when you put it into context of everything you’re doing with your system and how you want to do it. I spent awhile mining on the nix train and after realizing all the time I was spending babying my systems I moved it all over to Windows. That’s back when I did scrypt mining, little has changed besides having dedicated OS’s designed for mining and have almost no flexibility, it’s still the same crap.
Even if the programs and tools were available for nix, it’s still nix. When something breaks you need a degree to fix it. Knowing exact command line arguments, parameters, and syntax (much like programming). There are people literally paid to manage nix systems because it’s not remotely user friendly. There are also people paid to manage Windows as well, but that’s not nearly the same thing.
Time is money as well, something a lot of people don’t factor in when they’re saving $100 on a license then put in 10x as much effort when something is broken or something new comes out.
This is another major reason why no serious GPU farms use Windows. Don’t need spyware/keyloggers where money is concerned. A mining farm is like a bank. The less backdoors the better.
Windows 10 is quite effective for home mining, don’t get me wrong. But it’s a terrible OS for the kind of work we’re talking about here on a large scale. It’s a consumer workstation OS that’s been merged with a tablet OS, and it’s not something you want to try and run highly available services or compute tasks on; it just is not.
Microsoft will have you running through hoops to avoid their update policies, and the alternative that you’re putting forwards - disabling the Windows Update service - is again something that is really only good for home miners. A big farm running with Windows Update disabled is going to find themselves mining for someone else every other week.
Windows Server is still suitable for the kinds of highly available services you’re talking about, but we’re not talking about Windows Server, are we?
On the other hand, if you’re running a big farm you should able to afford a Linux admin, if you are nto one yourself. The tasks you seem to think are hard in Linux are in fact only hard for casual workstation users. (Even Windows Server admins will adjust pretty easily… Linux is a lot less painful than powershell.)
As a former Microsoft employee and contractor I can attest to those facts. Microsoft spends a ton of money in its marketing (SMSGR) departments trying to convince CTOs that its software and OSes are not buggy and full of backdoors. Most don’t buy it and go the linux route.
That has literally no bearing on how ‘usable’ it is or how functional it is. You can make claims about someones background too to pull them through the mud, but there was absolutely no point there besides ‘oh it can be run on a tablet’. So?
You mean you either have to manage policies (which I’m sure you can do as a super advanced nix user) or turn off a service? We covered this already. If you can’t figure out how to turn off a service in windows or set a group policy to manage the frequency of your updates, how do you ever run Nix? That’s easy stuff and a quick google search will give you 10 different pages giving you the same answer. And no, you wont 'mine else where after a week. I’m pretty sure there are tons of nix users that neglect their system updates as well. It’s not like nix is this magical place where viruses don’t exist and good security practices are always kept. If someone wants to turn off updates because they don’t want to deal with reboots (on nix or windows) then they will.
It doesn’t matter if it’s Windows server or W8 or W10. W10 is the only one with forced updates which you have to manage through policies or services BTW. Not sure where you’re going with that one or were you doing surface processing because it has ‘Server’ in the name?
Yeah, you pay someone $30,000 a year and hope they decide to never funnel any of your coins away, which I’m sure they couldn’t. Hey look, a new security risk and it has nothing to do with your OS. XD
Enterprise would literally not exist on Windows if their Server variant had the same consumer-focussed update policies as Windows 10.
Windows Server vs. Linux is a decision you might reasonably make for running highly available internet connected services.
Windows 10 vs Linux is a consumer choice, not an enterprise choice.
By all means make the Windows 10 choice, and for home use it is a good fit.
But please, don’t pretend you’re not out of your depth in this conversation. You just look like you’re picking a fight, and anybody with practical working experience of the concerns I am raising knows which one of us is right.
I’ve been using optiminer-zcash on ubuntu 14.04 for a few days without problems. I’ve just upgraded to 16.04 and installed amdgpu-pro drivers and now I get this error:
Did you find a resolution to this? I am getting the same error. It was running for a few days then it stopped yesterday. At most it will run for 30 minutes before it crashes. I am running Ubuntu 16.04 with amdgpu-pro 16.40 and AMDAPPSDK-3.0 with 2 RX 470 8GB cards.
Could you direct some solns to http://zogpool.orgzogpool.org:3357 if you get a chance and check that your miner is reporting waiting for work from pool.
I would take a look into the miner and check if I could see the source, but I will continue to look through the pool code for a solution/hack.
This pool software seems incompatible with your miner and works with all others. It would be nice to have your miner working with this pool software which is currently hosting ~20kH/s.
I tried to install the few dependencies that I didn’t have already and it didn’t help. The system was actually completely unresponsive after about 5 minutes.
