Can I buy a linux account 851

On Sun, 09 Apr 2006, in the Usenet newsgroup comp.os.linux.misc, in article

The rule is quite common for a number of reasons. First is that "these are company supplied systems, and we don't want the users installing crap on them". That rule is true no matter what the company supplied hard-software is. Second, there is a follow on - "we only support the $FOO O-S". Same concept. There is also the pointy haired boss syndrome - his kid recommends using $FOO O-S, and that's the way it's going to be. In fact, we're quite similar, expect in our case we don't all any microsoft O-S anywhere in the division - and I'm relatively sure that rule is corporate wide. I know that the "thou shalt not fsck with the software" policy in corporate wide, and rigidly enforced. The users are paid to use the computers as part of their job. They are NOT paid to install software, operating systems, or monitor toys.

I'm not a bean counter, so I don't know how much prices effect this (microsoft does give volume discounts, and support people with clue are more expensive than MSCEs). You also have to balance increased training costs (a two edged sword, as increased training in any tool-software-what-ever improves productivity) verses the costs of anti-malware software, and the cost when an infection or intrusion occurs, and the probability of that occurrence.

Yes, though that is stretching a bit. A large part of malware propagation is human engineering. It is designed to exploit misconfigured or unmaintained systems. The "somewhat immune to infection" is often helped by adequate training and better atbreastude. The "Slammer" worm went through microsoft.com like a dose of salts because they admins there didn't want to install a patch that had been available six months earlier because of compatibility problems. That's but one example.

Just as I would insist that they use the same platform. If IT is going to maintain the systems, it behooves them to know what they are, and how to do so. If they're using something else, they tend to lack that expertise that is needed to get things repaired-returned-to-normal RIGHT NOW. This also goes along with not allowing the users to fsck up the setups. In spite of what you may think, windoze can be maintained in a mode OTHER THAN 'retry-reboot-reinstall-reformat-reinstall' used by MSCEs. But it takes a more trained individual. The guy who knows how to tweaketc-syslog.conf is less likely to know which pulldown menu or registry key needs to be kicked. Just reinstalling can be done by any partially trained chimpanzee, but actually fixing the problem is going to be harder.

That depends on your disaster scenario.

Old guy