Slashdot Mirror
Windows Drives Company To OpenBSD
Barry Lyndon writes "Computerworld reports that the nightmare of windows is driving PriceWaterhouseCoopers, one of the world's largest accountancy and business consulting companies, to OpenBSD and open source in general." From the article: "'My predecessor spent too much [so] I was told not to spend any money.' When asked what argument he used to convince management to use an open source solution, Uemura said: 'They didn't have an argument because they said don't spend any money.' 'They trusted me,' he said. 'The whole office was relying on one domain controller which was dying.' Uemura said a lot of work was done 'behind the scenes'. 'My experience is that if something has to be done, just do it - don't ask! They will thank you later,' he said."
Hurray!! BSD is alive and kicking again!!
My experience is that if something has to be done, just do it - don't ask! They will thank you later
- Famous last words?
From TFA:
IT managers who want to deploy an open source solution but are worried about company politics should go ahead and do it without asking, according to PricewaterhouseCoopers (PWC) Japan IT manager Mark Uemura.
That sounds like a FANTASTIC idea. Just come in one weekend and change the entire network over to BSD without running it by anyone. Why bother with the pesky work of drawing up a well-structured arguement for what you want, and then run it by the people who sign your check? That would be highly irrational IMO...Screw politics, they'll thank you when it's done - With a nice pink check.
2) This is a firewall in Japan.
3) What PricewaterhouseCoopers uses for tax accounting is not something you want to be doing your taxes with.
What I'm listening to now on Pandora...
Have you ever actually used OpenBSD? If you have, then you would know that it's a massive time and money saver. Why is that? Because it just works. It's a well-engineered product. Your risk of security issues is virtually nil, and the support from the mailing lists often rivals that of anything from Microsoft or Red Hat.
.
Cyric Zndovzny at your service.
I have to agree with the guy quoted in the article. DON'T TELL THE PHBs.
Don't waste your time doing a cost benefit analysis. Don't waste your time trying to educate them. They've got other things on their minds, and they won't really understand it anyway. They have their job, and you have your job.
It's one thing if you want to try linux on the desktop or some other radical solution, but switching to a Samba fileserver or a Linux router/firewall? They don't need to know. As long as their files are where they want them to be, when they want them to be there, you'll be fine.
Was at a business once, where I was trying to talk the CEO into using a Linux solution, an idea to which he was VIOLENTLY opposed, said Windows had worked great for him. So eventually, I gave in and drew up a Windows solution. He wanted to know if it was goign to have all the functions that the current system had, and was leery because I was using a different version of windows.
So we went back into his "server room" (think ventillated broom closet) to look at the machine...Which turned out to be headless, which surprised me a bit, as it was supposed to be an NT box. As it turned out it WAS like an NT box in that it had an NT sticker on it, and NT rhymes with 7.3, as in Redhat 7.3 (uptime 518 days), running on a PIII coppermine with so much dust on the heatsink that I wasn't quite sure what it was at first.
Needless to say, he went with a linux system, and now he brags about it all over the place. I learned my lesson...Don't start talking software with the bosses. You'll only make more problems for yourself. If you don't absolutely HAVE to justify it to someone, don't do it.
ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
Therefore I have been experimenting with other Alternatives, such as Apple's OSX Server. OSX to my surprise is an organized way of working with Unix. So in the past months i have been learning how to use OSX Server and have polished my skills into using it in "Hybrid" Environments, with the most excellent results.
One of my clients was a Windows Shop, It took me several months to convince them to change the server into OSX. The prerogative was simple: Apple offered us the perfect growing up environment for a company of 20 something employees that could get as big as 50 in the next couple of years. How? Well Apple's Xserve and Unlimited Lic. OSX was the key. When I presented them with both investing plan's, which consisted of a Dell Server and Windows, and an Xserve and OSX, it basically came down to a 17k dollar investment to do with the Dell, Windows and all its licencing, and 4 terminal stations. In comparison with the Apple Equipment, the Xserve (2.0Ghz PowerPC, 1gb ECC, 80gb sata hdd (expandable to 3 hdd in sata raid 0)) and OSX Unlimited + Apple Remote (Unlimited), It only went up to $11,075.00. When I presented them both quotes, and told them that with the mac we could have interoperability with Windows XP pc's accessing the server as well, better security, easier configuration and other options, the company decided to take the dive and went the Apple way. Recently they had 20 more employees added, in which this would have meant an increase in licencing of over $2000, the company kept hiring and keeps growing without any problems and the IT Structure is solid. For applications, we Use Quickbooks 2005 for Mac and Quickbooks 2005 for Windows XP, Office for Mac and Office XP for Windows (althought we are going to change to Open Office 2.0 in December 2005). The reason we have a couple windows machines, is for some industry specific applications that we cannot find on mac, so we use them on windows. Everything else is run on the macs with no problems.
I want to add that the Remote Desktop of Macs is an awesome tool. I can make OSX Deployments far more easier than it is in Windows Server Environment. The next client im going to work on this week, Im going to propose the same change, in a bigger scale... I know ill be successfull because the previous client is in love with his system at work.
Nom de dieu de putain de bordel de merde de saloperie de connard d encule de ta mere.
'the boss said "why do you want that?"'
Correct answer: "It will help me do my job more effectively and make the company more competitivein the market"
Wrong answer: "It will help me find another job more effectively and make me more competitive in the job market."
Though on occasion brutal honesty can cause some interesting reactions. But seriously, just sell them the training and get them just as excited about it as you are.
Georgia Tech, the leader in Chia(tm) technology.
Take the place where I'm working for example. Medium sized company in Europe. Four countries and exspansion in more. After some bad moves two years ago by one of our operations the whole company got in trouble. Management decided to fire some 20%, vut back on outside consultants and retire everyone above 60. They also orchestrated a salary freeze and a max overtime cap. So we lost many of ur most experienced people from the downsizing or from people that decided to leave. In my office I'm the only IT guy left. The CEO told us in IT to cut back on new projects and frooze IT spending at x percant of turnover. Since most of our costs are locked in service contracts, licenses and scheduled hardware upgrades it's very hard to replace aging systems. We had some legacy systems that we just HAD to replace and that almost crushed our budget. So at one of our IT-guys meetings we just decided to stop renewing some MS products and went with Debian on some DNS, file and printer-servers.
Some six months later our local management found out that we had deviated from the "Microsoft-shop policy", but what could they do? They complained for a day or so before they realised that it was the only way we could stay withn the budget. In an environment where one can get fired for failing to stay within budget as well as failing to provide "service" to other units sometimes Linux is the only way.
Sorry for the bad English.