Close. In my case, as head of technology and development at a small outfit then using SCO Unix, it was a combination of factors. First, and most important, was gaining some level of control of the underlying software stack. A couple of examples: We installed the SMP package on a customer's system. Random crashes and panics became too common. We replaced the server - no joy. Having a support agreement with SCO ($$$), we called them for assistance and their response was "re-install the SMP package". When I explained that we'd already done that, they said "well, do it again". Another time, we needed their DDE-RPC package to run some CSTA software. When I tried to buy a copy, they said "nope, we discontinued that package". I offered several options: we'll pay for it, but not ask them for support, etc. No, no and no. It was about this time one of my techs who'd been singing the Linux song finally handed me the pack of Yggdrasil floppies and once I finally got it loaded and started looking at the source code for *everything*: kernel, compiler, utilities, etc. my jaw hit the floor and I knew that the world had shifted forever. We started then on a migration project - which took a couple of years - and we've never looked back. Worth every penny that we didn't pay to SCO, but did pay to our engineers.