What is meant by "download"? If it is transferring from one computer to another, what about things like proxy caches? Or Internet Explorer's cache on your local machine?
I guess Sweden just went off the net.
They are ejecting features from Longhorn, such as WinFS, to meet deadlines. Now, they're going to integrate virtualization?
Now, I can see a need for virtualization. Why? Well, at our shop, we need multiple Windows servers. Our wonderful Windows support people prattle that "we have never had an unscheduled reboot due to a hardware or OS failure!". But they do have reboots due to "memory leaks" in the major application running on that server. So they need multiple physical servers. With virtualization, if done correctly (no bets on that), they could reboot the virtual server and so have multiple low-use ill mannered applications on a single physical server.
"Better that a thousand should die unjustly, than one should avoid just punishment!"
I don't remember where I read that, likely some SciFi book from the ages before time (1970s).
--
John
I just installed SuSE 9.1 on my IBM ThinkPad R40e. The only problem was that the installation wanted to use the wrong Ethernet driver. Luckily for me, others had noticed this and I was able to override the installation.
I won't say that it was as easy as installing Windows. But, for me, it was not hard at all. For "Joe Sixpack" who doesn't know and doesn't really want to learn, I cannot say.
Germany now has a "copyright" tax on PCs sold in Germany. Why? Because, like a VHS tape or other recordable media, they could possibly be used for piracy!
That's what the Windows Weenies here at work kept calling it. Calling our IBM and Sun systems "proprietary" and their Windows systems "Open". I finally got management, at least, to call the Windows environment the "Distributed" systems. I wanted it called the "just do a control-alt-delete" systems because almost every problem I see in our internal problem system has that as the recommended fix. Followed by "must reinstall" when it fails.
And in a meeing with the Windows people, where they were asking about MS SQL server running on..., my reply was always: "No MS SQL server is proprietary to Microsoft and, unlike IBM's DB2 or Oracle, can only run on a Windows platform." Pissed them off by my constantly saying how open DB2 UDB and Oracle were compared to MS SQL Server.
Most places need to be like the local Fry's. They have ONE checkout queue and multiple checkers. In computer-speech, that is "single queue, multi-server". It works MUCHO better than multi-queue, multi-server where the "servers" are "equivalent".
Execution protection exists all over the zSeries IBM mainframe world. Every zSeries processor has a unique ID. Most software vendor software that runs on a zSeries requires running an administrative job to "activate" the software. This "activation" usually only works for one year after which the vendor (having been paid) gives you a new key for another year.
Take the same software using the same activation key to another zSeries and it won't run. The application will usually complain, then die (ABEND in zSeries terms).
The thing that I like about SMP machines over single processor machines is the fact that a single run-away application cannot hog the entire machine. Most applications that I deal with in business are I/O bound and not CPU bound. So a really fast CPU is not as critical as really fast I/O.
What is meant by "download"? If it is transferring from one computer to another, what about things like proxy caches? Or Internet Explorer's cache on your local machine? I guess Sweden just went off the net.
Now, I can see a need for virtualization. Why? Well, at our shop, we need multiple Windows servers. Our wonderful Windows support people prattle that "we have never had an unscheduled reboot due to a hardware or OS failure!". But they do have reboots due to "memory leaks" in the major application running on that server. So they need multiple physical servers. With virtualization, if done correctly (no bets on that), they could reboot the virtual server and so have multiple low-use ill mannered applications on a single physical server.
"Better that a thousand should die unjustly, than one should avoid just punishment!" I don't remember where I read that, likely some SciFi book from the ages before time (1970s). -- John
I just installed SuSE 9.1 on my IBM ThinkPad R40e. The only problem was that the installation wanted to use the wrong Ethernet driver. Luckily for me, others had noticed this and I was able to override the installation.
I won't say that it was as easy as installing Windows. But, for me, it was not hard at all. For "Joe Sixpack" who doesn't know and doesn't really want to learn, I cannot say.
Germany now has a "copyright" tax on PCs sold in Germany. Why? Because, like a VHS tape or other recordable media, they could possibly be used for piracy!
And in a meeing with the Windows people, where they were asking about MS SQL server running on ..., my reply was always: "No MS SQL server is proprietary to Microsoft and, unlike IBM's DB2 or Oracle, can only run on a Windows platform." Pissed them off by my constantly saying how open DB2 UDB and Oracle were compared to MS SQL Server.
Well, I have to get my jollies somehow.
Most places need to be like the local Fry's. They have ONE checkout queue and multiple checkers. In computer-speech, that is "single queue, multi-server". It works MUCHO better than multi-queue, multi-server where the "servers" are "equivalent".
Execution protection exists all over the zSeries IBM mainframe world. Every zSeries processor has a unique ID. Most software vendor software that runs on a zSeries requires running an administrative job to "activate" the software. This "activation" usually only works for one year after which the vendor (having been paid) gives you a new key for another year.
Take the same software using the same activation key to another zSeries and it won't run. The application will usually complain, then die (ABEND in zSeries terms).
The thing that I like about SMP machines over single processor machines is the fact that a single run-away application cannot hog the entire machine. Most applications that I deal with in business are I/O bound and not CPU bound. So a really fast CPU is not as critical as really fast I/O.