|
|
|
|
|
by zanny
4444 days ago
|
|
1. Size. Standard install takes up almost 20GB of hard drive space. Fresh Lubuntu, Crunchbang, or Debian takes up a gigabyte. 2. Backdoor prone black box. Something like Windows - buy licenses, get support from a 3rd party, be ignorant about product itself due to withheld software freedoms - works for the small to medium business. When you are federal scale, it makes no sense to spend tens or hundreds of millions in MS tax when you could, for a fraction of the price with a small dev team, maintain your own Linux fork. And while the IRS is on the "same side" as the NSA, who puts back doors in Windows, it should be hard to sleep at night knowing Microsoft could be bought off like that, and that China might do the same. Unless they get special source access to inspect it, at that scale they might. 3. No package management. For enterprise deployments, I've dealt with enough small businesses who just sit on half a decade old Firefox or Chrome because they can't enable the auto updater and didn't set up an Active Directory applications server. So the middle road is just having your own package repository of updates with all the machines synced to it pushing whatever new stuff you want available automatically. And you could also throw in that a GNU/Linux distros modularity makes it much more reasonable to deploy to servers, embedded devices, and desktops at once with one maintenance crew. And if the IRS is running Windows Server.... taxpayer dollars at work, all right. |
|
2. Didn't like my response to this, may edit later.
3. Now this is reasonable, software installation on Windows sucks by default. However, there are some good tools out there for handling the distribution of software. I recall using some when I worked in IT at a university. Ghost had a way to do it that was essentially taking a snapshot, installing, then another snapshot. The difference was what got installed onto the rest of the computers. There was also a piece of software we used that let us handle on-demand software installation for things with limited keys (like Matlab), I don't remember (a decade ago now) what this one was. Not baked in, but it was more than serviceable as I recall.
4. IRS probably still has a fair number of mainframes. If they're like other federal agencies they'll have a mixture of Solaris, Windows and Linux servers installed depending on the contract at the time the information system was put together. Again, that modularity would be nice, but it's hardly practical unless the fed establishes one organization to be responsible for making, supporting and distributing this OS. Then you'd get a bunch of folks on the right bitching about government interfering with business, and people on both sides bitching about the security/privacy implications.