Part II: Corp. Desktop Linux - The Hard Truth
comforteagle writes "I've published Part II of W. McDonald Buck's essay on Linux TCO. In it he looks at the scenario of a company having already moved to Linux in the server room and also to open source software on Windows desktops, but "...now wants to know, how much extra can be saved by the final step of changing the operating system itself? And, what are the other costs, risks and benefits of doing that. To keep the scenario simple, we're assuming too that this will be done at a time when the desktop equipment is also being replaced. The news is good, but not as good as we like to believe." Part I was discussed previously on Slashdot."
I didn't start looking into this recently. But is it really impossible to: (1) encode MP3s and AACs, (2) render text using TrueType kerning tables, or (3) take advantage of subpixel rendering, on Linux desktops, without breaking patent laws? With all the hype surrounding Linux on the desktop, I have trouble believing these common activities could be illegal, but nor have I seen anything indicating otherwise. What's the deal?
(And please, no Stallmanesque rants about how intellectual property should be abolished. I don't have the patience for these ill-conceived prescriptive arguments.)
One way to aproach this situation is to put a large multi-user box in each individual department or workgroup. Keep the windows desktops there, add X-servers, and run some apps centrally.
If the question is licensing, a net-booted corporate (Linux/FreeBSD/NetBSD) desktop wouldn't be too difficult. Run locally what the machine can handle, make sure the network is super fast, and run the apps requiring performance on the workgroup server.
This would reduce the need to upgrade lots of hardware (which will surely be obsolete again soon) and minimize downtime in the process. If need be, some legacy apps could survive under Wine locally or, again, at the workgroup server. Keep storage centralized to facilitate backups across the entire organization (OpenAFS?).
It's an old way of doing things but overlooked far too often. You've obviously got to run the numbers but, surely, "a few good men" handling things on the server (they would handle the app server AND the centralized, consistent-across-the-organization, netboot image(s)) would be much less expensive than the workload on an IT staff required by an office full of people and their problems on Windows machines.
Maybe not *THE* solution, but certainly worth a look for many.
Right now you are not likely to save a huge amount of money dropping Windows. The big savings will come from dropping Office for OpenOffice, dropping Outlook for Thunderbird and IE for Firefox. Once you are not tied to Windows only apps then you are free to move to an other OS easily. Be it Linux or Mac.
It is a matter of freedom.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.