One more thing. I forgot to mention that you'll be needing fewer IT folks once you move into a Linux-based setup. So expect you can lose 10% and up of your force through attrition or whatever.
Some responders did point you to a few articles describing the TCO. Here's my take: Take the sum of the cost of the commercial software licenses you are intending to replace. Do a 1 year, and a 5 year cost. Then take the salaries of your IT team and add 10%. Linux people are getting more than Windows people these days. Subtract the aggregate salary increase from the cost of the commercial software. That should be a reasonable ballpark figure. Architect what services you want to provide first. If you're not sure, spring for a consultant to architect them for you.
Consider that your IT team are professionals. Professionals don't need to be trained. It is up to them to keep up with the demands of their field. It is not the responsibility of the employer to train their IT professionals. But remember that the entire IT team is there for the purpose of earning money.
Assign individual services (apache, samba, the chosen distribution, firewalling, etc.) each to a lead and a second. This is a much better way to approach things than having a Linux Jack-of-all-Trades (master of none) in every department. People may end up handling more than one service/project. Ask for volunteers for each project, rather than assigning things against somebody's better wishes. Don't let one individual become lead of too many services/projects. Expect them to keep on top of new releases of their service/project, know how to get help, and be on the project's mailing list. Allow them to make contributions to their projects source code free of intrusive IP hackles from their employer.
Let everybody work with and get their individual projects up on a company-supplied test-and-trash server. They can do anything they want on the trash server, and when each project gets certified to go live, then deployed out in the workplace. Give each project up to 6 months max for deployment.
This is how you keep your TCO down to almost nothing.
You're spouting the obsolete Reagen mythos. Look at current politics and it is the Repubs that are for huge centralized government, huge spending and authored this internet tax grab.
Jaguar is a step in the right direction. I remember the olden days when NeXT made the Dimension, with an Intel i960-based card exclusively for the Display PostScript interpreter in 24 bit. I wonder if one can assign the Display PDF to run exclusively on a single CPU in a dual CPU Mac setup. That would provide a speedy and consistent interface not bogged down by the other processes.
I was surprised that even the AMD 8151 chipset didn't have any 64-bit PCI. Surely, AMD has figured out how to do it with their older 760mpx chipset. So that leaves Serial ATA, GigaNics, and anything SCSI being I/O squeezed.
They would have grown into a nice network if they had followed the lead of academics and standardized on BSD in the 80s, followed by any flavor of UNIX followed by Linux. Now they think they are going to make things better by buying licenses for Microsoft products?
Not surprising to see why they need this multi-billion dollar upgrade. The problem is, this type of 'upgrade' for Microsoft corporate is becoming a perpetual nightmare. I'd laugh at their foolishness but I know that I'm helping to pay for it.
Considering the several available opensourced journaling filesystems that don't incur performance penalties, I have to laugh at Apple's latest lock-box attempt.
I have seen no evidence that Apple has been increasing any market share. In fact, if Apple suddenly took the majority of market share away from Microsoft, I don't think we'd be in any better shape. To have one company control both the hardware and the software end would be suffocating.
I don't think Apple is going anywhere because of its high costs and its inability to produce machines with superior value and/or price. IBM's 64-bit PowerPC chip may be priced more like the Itanic than it will be priced like the Hammer. The Apple Tax is for colored, moulded plastic. So if Apple takes up 64-bit, that only means their survival will be extended for 5 or so more years.
I'm looking forward to Hammer machines running Linux, not an overpriced 64-bit Macintosh.
Video on the motherboard is smart. I always get one of those boards now. Figure $75 dollars for a high-end, such as NForce, and sell it a year later on Ebay for $35. What does this really mean? Time=money. Less money, more time to play with the computer.
It is so sad that he's going to jail for duplicating data. I don't give a rat's ass about the position that it is 'stealing'. These people never sold their copies.
The laws have really gone over the line. Copyright violations used to be civil matters, going into criminal if somebody sold copies for financial gain.
It is a sad time when corporate entities have so many more rights than citizens.
I've got an old 1600cc non-turbo VW diesel that constitently gets 52 mpg. It has more than 350,000 miles on the odometer. I'm surprised that none of the hybrids produced so far use diesels. Diesels are even more efficient if they run at a constant rpm. Railroad hybrid locomotives are an excellent example of the system: electric motors to run the vehicle, constant rpm diesels to charge the batteries (when needed). 100 mpg would be practical for a 2,000 lb. car.
The latest non-scientific mindset of the Greens seem to be prohibitive of diesels because they believe they cause CANCER, and that they believe the emissions from gasolene DON'T cause cancer (or they choose to ignore them). They are being played by the oil companies, who know that the quantity of diesel that can be distilled from crude oil is limited.
We assume, of course, that the unnamed sites blocked by the government actually WERE child porn sites. Isn't the US Federal director of the Homeland Security Dept. the former governor of Pennsylvania?
Paranoia? Perhaps, but when censorship happens on the sly, freedom mongers should worry.
Okay, moving right along. CPUs. Those yahoos think that the only option is to start from scratch. Get a clue. The last pre-Jobs big boxes kicked almighty ass. Amelio may not have been a gifted businessman but he was a much better heavy gear guy. As far as I'm concerned your best bet for DIY is to buy an 8600. It'll be $230, tops. You get a great case, big power supply, floppy drive, cables, and so on.
It is a BIG problem that the older Macs run a 50, 45 or even a 40 mhz bus. That just doesn't carry the day for me anymore. I speak from experience because I'm running an ancient PowerCurve at 350mhz G3 with a 50 mhz (overclocked) bus. When I went from a 266mhz to a 350, I hardly noticed the difference. These machines are starved for data. My girlfriend bought a 466mhz G4 running a 133mhz bus and that makes all the difference in the world. Her machine spanks another friend's 450 G4 running a 100mhz bus.
I agree with you about not bothering doing it from scratch. Just get a G4 running with a 133mhz bus and a G4 7410 CPU and you're set for a couple of years.
Overall, the high price of used Apple parts and complete equipment tells us there is a much larger market demand that Apple's stupid, thumbhead, prima-dona, ignorant, ego-puffed leaders aren't able to supply. I believe they could easily take their market share up to 15% if they could get their manufacturing act together.
That's in the US only, where type foundries rely on trademarked names to distinguish their designs. In Europe the actual design is copyright protected. Both the US and Europe protect the 'digital' implementation of the font as copyrighted software.
Get the patch from France. France is one of those "free countries".
" How to use iDVD2 without an internal Apple SuperDrive:
I am unaware how many different version of iDVD2 are circulating, but I have already listed 3 versions. This is why I have provided three different patches to cover at least these 3 versions of iDVD2.
A quick reminder on how to apply one of those patches to iDVD2:
- download the patch file
- Make a copy of the iDVD.app package and open it within MacOS 9.
- Move the file "iDVD" to the desktop. The file can be found in Contents/MacOS
- Doubleclick the patch application and patch that iDVD App.
- Once applied, you'll find the file patched and the original file renamed to "iDVDOld"
- Move the file "iDVD" back into the folder "Contents/MacOS"
- close the (MacOS X) Package again and reboot into MacOS X to try it out "
Those reading the email are given the option of accepting or rejecting the meeting. If accepted the meeting is automagically added to the readers calendar.
Aha. So that's why html enabled email can be useful. The email would have a 'click here' item to add the meeting to the user's calender something like http://mycompany.com/meetings/1235audienceAdd.php? id=JoeWorker
kinda like those email spams that collect info when one clicks. Also, an email reader app would need to support sending a certificate when the email was read. I wonder if there exists an email server in Linux/UNIX that is database-based? An anonymous-coward poster also mentioned that mysql wouldn't be up to the task for use in an Exchange replacement, but there is Postgress and even SAP's database.
So, I guess the process wouldn't be trivial. But I do think it could be put together from what's already out there, to some extent.
I'm having a difficult time trying to figure out what makes a calendering app so much voovoo? Can't everything be done with mysql and a php web app? What's so difficult? What's so friggin great about a calender app, anyway? I'm not much of a developer, but maybe it is the total boredom aspect of calender apps, that make them so unattractive. "Gotta meet the Gurneys and a dozen grey attorneys!"
Also, why is it necesary to copy MS's combination of email, group messaging, and calendaring in a single app?
We already have nntp, many email servers, and probably there are calendering apps on Freshmeat.net.... I just went there and found 5 projects after searching for 'calender'.
Just let thenm go out of business, then, instead of coming up with all sorts of draconian laws and schemes to quash my rights in the pretense of giving them a profit.
Slashdot Mirror
One more thing. I forgot to mention that you'll be needing fewer IT folks once you move into a Linux-based setup. So expect you can lose 10% and up of your force through attrition or whatever.
Consider that your IT team are professionals. Professionals don't need to be trained. It is up to them to keep up with the demands of their field. It is not the responsibility of the employer to train their IT professionals. But remember that the entire IT team is there for the purpose of earning money.
Assign individual services (apache, samba, the chosen distribution, firewalling, etc.) each to a lead and a second. This is a much better way to approach things than having a Linux Jack-of-all-Trades (master of none) in every department. People may end up handling more than one service/project. Ask for volunteers for each project, rather than assigning things against somebody's better wishes. Don't let one individual become lead of too many services/projects. Expect them to keep on top of new releases of their service/project, know how to get help, and be on the project's mailing list. Allow them to make contributions to their projects source code free of intrusive IP hackles from their employer.
Let everybody work with and get their individual projects up on a company-supplied test-and-trash server. They can do anything they want on the trash server, and when each project gets certified to go live, then deployed out in the workplace. Give each project up to 6 months max for deployment.
This is how you keep your TCO down to almost nothing.
It is a little late to wonder: the election is over.
You're spouting the obsolete Reagen mythos. Look at current politics and it is the Repubs that are for huge centralized government, huge spending and authored this internet tax grab.
Tax and spend, tax and spend.
If I could teach someone how to understand man pages in 24 hours, they'd be halfway there.
+1 bonus
I was surprised that even the AMD 8151 chipset didn't have any 64-bit PCI. Surely, AMD has figured out how to do it with their older 760mpx chipset. So that leaves Serial ATA, GigaNics, and anything SCSI being I/O squeezed.
They would have grown into a nice network if they had followed the lead of academics and standardized on BSD in the 80s, followed by any flavor of UNIX followed by Linux. Now they think they are going to make things better by buying licenses for Microsoft products?
Considering the several available opensourced journaling filesystems that don't incur performance penalties, I have to laugh at Apple's latest lock-box attempt.
I don't think Apple is going anywhere because of its high costs and its inability to produce machines with superior value and/or price. IBM's 64-bit PowerPC chip may be priced more like the Itanic than it will be priced like the Hammer. The Apple Tax is for colored, moulded plastic. So if Apple takes up 64-bit, that only means their survival will be extended for 5 or so more years.
I'm looking forward to Hammer machines running Linux, not an overpriced 64-bit Macintosh.
Video on the motherboard is smart. I always get one of those boards now. Figure $75 dollars for a high-end, such as NForce, and sell it a year later on Ebay for $35. What does this really mean? Time=money. Less money, more time to play with the computer.
The laws have really gone over the line. Copyright violations used to be civil matters, going into criminal if somebody sold copies for financial gain.
It is a sad time when corporate entities have so many more rights than citizens.
Good thing for open source software.
The latest non-scientific mindset of the Greens seem to be prohibitive of diesels because they believe they cause CANCER, and that they believe the emissions from gasolene DON'T cause cancer (or they choose to ignore them). They are being played by the oil companies, who know that the quantity of diesel that can be distilled from crude oil is limited.
Paranoia? Perhaps, but when censorship happens on the sly, freedom mongers should worry.
It is a BIG problem that the older Macs run a 50, 45 or even a 40 mhz bus. That just doesn't carry the day for me anymore. I speak from experience because I'm running an ancient PowerCurve at 350mhz G3 with a 50 mhz (overclocked) bus. When I went from a 266mhz to a 350, I hardly noticed the difference. These machines are starved for data. My girlfriend bought a 466mhz G4 running a 133mhz bus and that makes all the difference in the world. Her machine spanks another friend's 450 G4 running a 100mhz bus.
I agree with you about not bothering doing it from scratch. Just get a G4 running with a 133mhz bus and a G4 7410 CPU and you're set for a couple of years.
Overall, the high price of used Apple parts and complete equipment tells us there is a much larger market demand that Apple's stupid, thumbhead, prima-dona, ignorant, ego-puffed leaders aren't able to supply. I believe they could easily take their market share up to 15% if they could get their manufacturing act together.
" How to use iDVD2 without an internal Apple SuperDrive :
I am unaware how many different version of iDVD2 are circulating, but I have already listed 3 versions. This is why I have provided three different patches to cover at least these 3 versions of iDVD2.
A quick reminder on how to apply one of those patches to iDVD2:
- download the patch file
- Make a copy of the iDVD.app package and open it within MacOS 9.
- Move the file "iDVD" to the desktop. The file can be found in Contents/MacOS
- Doubleclick the patch application and patch that iDVD App.
- Once applied, you'll find the file patched and the original file renamed to "iDVDOld"
- Move the file "iDVD" back into the folder "Contents/MacOS"
- close the (MacOS X) Package again and reboot into MacOS X to try it out "
I got these instructions from here.
Aha. So that's why html enabled email can be useful. The email would have a 'click here' item to add the meeting to the user's calender something like http://mycompany.com/meetings/1235audienceAdd.php? id=JoeWorker
kinda like those email spams that collect info when one clicks. Also, an email reader app would need to support sending a certificate when the email was read. I wonder if there exists an email server in Linux/UNIX that is database-based? An anonymous-coward poster also mentioned that mysql wouldn't be up to the task for use in an Exchange replacement, but there is Postgress and even SAP's database.
So, I guess the process wouldn't be trivial. But I do think it could be put together from what's already out there, to some extent.
Also, why is it necesary to copy MS's combination of email, group messaging, and calendaring in a single app?
We already have nntp, many email servers, and probably there are calendering apps on Freshmeat.net. ... I just went there and found 5 projects after searching for 'calender'.
Boring and trivial(?)
Just let thenm go out of business, then, instead of coming up with all sorts of draconian laws and schemes to quash my rights in the pretense of giving them a profit.