I don't think that you could show me any program with 100% perfect code. Yes, OSes get hacked/broken/etc. constantly... so why do you think a hypervisor would be any different? I would have to say I fully agree with Theo on this one. The ability to write perfect code with no exploitable security flaws and no bugs is pretty much beyond what companies are willing to go through in this day and age. The time and money needed to fully test every aspect of every single line of code in a system would delay a product's release so long that the company in question would probably go bankrupt before they ever got to sell it to anyone. Thats why there are updates and patches and new versions that have the exact same functionality as the old...
I'm posting verbatim the entire paragraph because you obviously ditn't read it...
"Third, the additional bugs that external hackers find are commonly found by examining the patches we apply to our software. Look at our vulnerability statistics. Most of our hits center around two main features. Both features came to the attention of hackers after we had released patches for them fixing internally found problems. In both cases we located the vulnerable code and patched. Within a month, three more related holes were found by the hacker community. OK, so we didn't do a great job in ferreting out all the errors in the features. After the last round of fixes, we investigated each feature with a more comprehensive analysis and code review. We even hired an external penetration testing team. We found many more holes and patched them. Then in the next six months, we got hacked again in the same features. There's lots of blame going around, along with better solutions, but it doesn't change the fact if we had kept the original exploits unpatched, we would have avoided three additional, publicly discussed exploits."
At the last company I worked for we had two T1s, and wireless(via microwave) as a back up. The T1s(from AT&T) rarely got the bandwidth they should have.
Not to mention, it took AT&T more than a year to get the lines installed(from time of first contact to actual installation). They gave us the run-around for 3 months right before moving in to the new building where the lines were going saying that they would be unable to install them(after right before that saying it was no problem whatsoever). It took going up three levels in their red-tape littered little world(our salesman's supervisor, their manager, and then finally his boss) to get it resolved, and it still was not completed by the date they gave us. It was several weeks in to the new building when we FINALLY got our T1s and were able to start using our phones(VOIP) and internet at the same time. I told the company president over and over not to go with T1s and not to go with AT&T but he was set on it, as was my boss.... so that is what we did. I learned a very important lesson from that... eff AT&T.
The Desktop Effects and Beryl both use Compiz and from what I understand the two teams are working to bring the code together into a unified program.
Beryl installed in about 20 seconds for me... works great. Looks great. No problems whatsoever.
On another note... the only problem I have with Feisty is that my sound card won't work... which is not Feisty's fault. It is Creative's fault because they suck at supporting Linux.
Slashdot Mirror
So... you're hiring right?
No PCI-E as the board doesn't support it. Two PCI slots. No SATA.
Also... the computers are in stock at zareason.com
You can also buy just the board for $60 if you have a bunch of spare parts laying around. board available here
Maybe I should have said I don't think you can show me any usefull code that is 100% secure/correct and actually would be used by many people.
I don't think that you could show me any program with 100% perfect code. Yes, OSes get hacked/broken/etc. constantly... so why do you think a hypervisor would be any different? I would have to say I fully agree with Theo on this one. The ability to write perfect code with no exploitable security flaws and no bugs is pretty much beyond what companies are willing to go through in this day and age. The time and money needed to fully test every aspect of every single line of code in a system would delay a product's release so long that the company in question would probably go bankrupt before they ever got to sell it to anyone. Thats why there are updates and patches and new versions that have the exact same functionality as the old...
I'm posting verbatim the entire paragraph because you obviously ditn't read it...
"Third, the additional bugs that external hackers find are commonly found by examining the patches we apply to our software. Look at our vulnerability statistics. Most of our hits center around two main features. Both features came to the attention of hackers after we had released patches for them fixing internally found problems. In both cases we located the vulnerable code and patched. Within a month, three more related holes were found by the hacker community. OK, so we didn't do a great job in ferreting out all the errors in the features. After the last round of fixes, we investigated each feature with a more comprehensive analysis and code review. We even hired an external penetration testing team. We found many more holes and patched them. Then in the next six months, we got hacked again in the same features. There's lots of blame going around, along with better solutions, but it doesn't change the fact if we had kept the original exploits unpatched, we would have avoided three additional, publicly discussed exploits."
Are you out of your mind?!
At the last company I worked for we had two T1s, and wireless(via microwave) as a back up. The T1s(from AT&T) rarely got the bandwidth they should have.
Not to mention, it took AT&T more than a year to get the lines installed(from time of first contact to actual installation). They gave us the run-around for 3 months right before moving in to the new building where the lines were going saying that they would be unable to install them(after right before that saying it was no problem whatsoever). It took going up three levels in their red-tape littered little world(our salesman's supervisor, their manager, and then finally his boss) to get it resolved, and it still was not completed by the date they gave us. It was several weeks in to the new building when we FINALLY got our T1s and were able to start using our phones(VOIP) and internet at the same time. I told the company president over and over not to go with T1s and not to go with AT&T but he was set on it, as was my boss.... so that is what we did. I learned a very important lesson from that... eff AT&T.
The Desktop Effects and Beryl both use Compiz and from what I understand the two teams are working to bring the code together into a unified program. Beryl installed in about 20 seconds for me... works great. Looks great. No problems whatsoever. On another note... the only problem I have with Feisty is that my sound card won't work... which is not Feisty's fault. It is Creative's fault because they suck at supporting Linux.