In message , T i m writes
I find that interesting because I ran Windows Home Server as a backup server here on the suggestion of my son. He then had a disk crash on his system and had a major job recovering the data in readable format (don't know any details beyond that). Soon after that I had a problem and decided to retreat by installing CentOS and backing up to it in formats that I knew I could read on any machine here. Suggestions from Mike Tomlinson here, and a friend in the USA were really helpful in getting it going. Then the power supply on my HP server died and while I was doing the metal bodging to get a standard psu to fit, I decided I'd better have a second backup server, so put one together and discovered that Centos7 was very different from Centos6. I had to be helped again.
I just don't know about any of this these days.
CentOS 6 has been reliable, CentOS 7 less so, but maybe that's because I haven't bothered to understand the differences. The problem remains that there are Windows programs that don't have equivalents in Linux and, for example, audio still seems to be a mishmash of mediocre programs even when compared with ancient Windows audio (which itself isn't that brilliant). (Maybe it's time to give Harrison Mixbus another go).
On the other hand it just isn't acceptable to have Wndows7 programs switching from "Don't update" to "Automatic" or W10 pushing in different drivers under the radar. I caught it breaking my touchscreen drivers because it was an obvious thing to have stopped working, but how do I know what other obscure drivers might have changed without being discovered until some critical moment.
The W7 rolled up drivers seem to still come with some hints about what is being addressed, but W10's updates as far as I can see are still done blind.
End of rant. Sorry.