I think it's fair to say, society has changed since then. Maybe not as much as we'd all like but the world simply isn't the same place it was when your forefathers wrote the constitution. If GWB has shown the world anything it's that the US citizens are now so diverse in their opinions that I don't think it's possible for a militia to grow strong enough, fast enough, in the US, to overthrow the government.
The same is almost certainly true of all the other westernized nations too. So with that said, really what does gun ownership get you? If it doesn't give you the power to overthrow the government, which as far as I know was the reason it was in the constitution, then it's just a dangerous weapon waiting to hurt someone.
But, if it really is all virtualized, you could then move the VM of your OS(s) to your new phone without ever having to worry about where your phone book is stored again
It wouldn't eliminate the SATA problem at all. The OS still has to have a driver to talk to the "disk". If it's not SATA then what? I suppose you could use SAS but that doesn't really buy you anymore speed at this point.
The problem with this benchmark overall seems to be that their SATA controllers (both the one on the motherboard and the one in the drive) can't do anything like it's ~300MB/sec per port. This is glaringly obvious in the file copy tests where the extra port gives you a boost but nothing like twice the speed and even on one port they are still a long way from ~300MB/sec.
Of course in everyone's defense they haven't really ever been able to test this in the past without some custom hardware.
Even if they do have power problems, they are being paid taxes to, among other things, provide adequate infrastructure. They are failing to do that because they are presumably spending the money on other stuff that's less important (I'm assuming most people would put power above pretty much every other infrastructure provided).
If they have to regulate the power industry to get the capacity that's required then that's what they should be doing, not regulating what can and can't be sold because of it's usage
Uhh, so what happens if there is a fire/earthquake/hurricane or any other disaster that wipes out your site? You've got data thats 3 months old? While thats better than nothing I'd be surprised if your company survived that.
Between different vendors is actually quite hard. Live migration requires saving the CPU state exactly, including all registers. Going to a different vendors CPU means all this saved state may not match up and then you have to do something so the VM won't just crash. This is actually becoming _harder_ as more and more virtualization technology is being put into the CPU silicon (Intel VT, AMD-V etc). Each new series has a few more features to make virtualization simpler, and you have to deal with making sure what was available to the VM on one CPU is identical to whats available on the new CPU without destroying performance (which is what will happen if you start emulating).
In saying that, VMWare are very very VERY careful with the tech they introduce, to give you an example round robin network teaming is still "experimental". I'm fairly sure they have played with this internally already and not done it either because it would make support harder or because of the changing CPU landscape with regard to the integrated virtualization features on new CPU's they would need to release a new version for each new CPU release for this to continue working.
Make no mistake, this is big news for KVM and well done to them, but if they can make it work reliably so can anyone else, and that includes VMWare
You also have to factor in that Reactor Meltdowns don't just kill people, they destroy the ecosystem and environment completely and for a LONG time, well depending on the meltdown but I'm using Chernobyl as an example.
Nuclear weapons, are very VERY clean by comparison. At least those currently capable of launch.
He's not talking about idle, when engine braking the wheels are turning the engine so no fuel is required to do so, thus no fuel needs to be burnt. As was said this ony happens over a certain RPM (which when engine braking you will exceed this value).
Below this rev value, you aren't engine braking and so fuel must be burnt to stop the engine stalling
The backups note here is the best advise, and if you do use VMWare or something, make sure it supports snapshots. When testing they are the single most useful tool you will have to save from screw ups.
Sure it won't teach you how to fix the mess you just created, but it'll teach you how not to create it in the first place since you can undo/redo until you get it right. This is also one of the powers of using VM's in production. A full VM snapshot is better than any Windows system restore point or remove will ever be.
They hardly need to connect a fibre cable to any particular country. Hell they could anchor on top of one of the undersea cables and just tap straight in and rent the bandwidth directly from the people that own the cable. Hell it's google, they could lay their own damn cable.
What more os a concern is if you're using sea water to cool your server you need to filter that water VERY well unless you want the try dealing with the corrosion inside your water blocks.
Or you could setup Excel to trust that spreadsheet (or it's location) so that you don't get prompted with warnings etc everytime. Very easy to do and would remove, what seems to be your biggest gripe.
And just to add to the nitpicking, the PhysX cards were only PCI as far as I ever saw. Maybe they didn't need the bandwidth of anything more, but that always struck me as silly to make a PCI card when PCI-E was already available on new motherboards
AMD _is_ a memory company, last time I looked (and I admit it was a few years ago) they made WAY more money from their flash division than from their CPU division
Router != Switch. No typical "office" needs a 40 port router
Poster specifically says router. Even a 40 port switch on a linux box would be an interesting experiment to behold. Assuming you were using PCI-E (which is the only way you'd get even remotely decent speed) I still don't think you could get 40 ports into a box You'd have to find a board with exactly the right PCI-E bus layout.
As everyone else has mentioned. You just can't make a router that would have enough bus bandwidth or processing power to do this
Slashdot Mirror
I think it's fair to say, society has changed since then. Maybe not as much as we'd all like but the world simply isn't the same place it was when your forefathers wrote the constitution. If GWB has shown the world anything it's that the US citizens are now so diverse in their opinions that I don't think it's possible for a militia to grow strong enough, fast enough, in the US, to overthrow the government. The same is almost certainly true of all the other westernized nations too. So with that said, really what does gun ownership get you? If it doesn't give you the power to overthrow the government, which as far as I know was the reason it was in the constitution, then it's just a dangerous weapon waiting to hurt someone.
But, if it really is all virtualized, you could then move the VM of your OS(s) to your new phone without ever having to worry about where your phone book is stored again
Do they actually have ECC memory in them yet? Last time I looked ECC wasn't even an option. Of course, that was a few years back now.
It wouldn't eliminate the SATA problem at all. The OS still has to have a driver to talk to the "disk". If it's not SATA then what? I suppose you could use SAS but that doesn't really buy you anymore speed at this point.
The problem with this benchmark overall seems to be that their SATA controllers (both the one on the motherboard and the one in the drive) can't do anything like it's ~300MB/sec per port. This is glaringly obvious in the file copy tests where the extra port gives you a boost but nothing like twice the speed and even on one port they are still a long way from ~300MB/sec.
Of course in everyone's defense they haven't really ever been able to test this in the past without some custom hardware.
Even if they do have power problems, they are being paid taxes to, among other things, provide adequate infrastructure. They are failing to do that because they are presumably spending the money on other stuff that's less important (I'm assuming most people would put power above pretty much every other infrastructure provided). If they have to regulate the power industry to get the capacity that's required then that's what they should be doing, not regulating what can and can't be sold because of it's usage
Uhh, so what happens if there is a fire/earthquake/hurricane or any other disaster that wipes out your site? You've got data thats 3 months old? While thats better than nothing I'd be surprised if your company survived that.
No one mentioned 64bit, 32bit Vista you can just say install anyway, which is what Apple wouldn't allow you to do if they implemented such a system
Internally we are all 37 Degrees C. When someone takes your temperature, that's what they'll get as a result if you're not sick
Between different vendors is actually quite hard. Live migration requires saving the CPU state exactly, including all registers. Going to a different vendors CPU means all this saved state may not match up and then you have to do something so the VM won't just crash. This is actually becoming _harder_ as more and more virtualization technology is being put into the CPU silicon (Intel VT, AMD-V etc). Each new series has a few more features to make virtualization simpler, and you have to deal with making sure what was available to the VM on one CPU is identical to whats available on the new CPU without destroying performance (which is what will happen if you start emulating).
In saying that, VMWare are very very VERY careful with the tech they introduce, to give you an example round robin network teaming is still "experimental". I'm fairly sure they have played with this internally already and not done it either because it would make support harder or because of the changing CPU landscape with regard to the integrated virtualization features on new CPU's they would need to release a new version for each new CPU release for this to continue working.
Make no mistake, this is big news for KVM and well done to them, but if they can make it work reliably so can anyone else, and that includes VMWare
You also have to factor in that Reactor Meltdowns don't just kill people, they destroy the ecosystem and environment completely and for a LONG time, well depending on the meltdown but I'm using Chernobyl as an example. Nuclear weapons, are very VERY clean by comparison. At least those currently capable of launch.
He's not talking about idle, when engine braking the wheels are turning the engine so no fuel is required to do so, thus no fuel needs to be burnt. As was said this ony happens over a certain RPM (which when engine braking you will exceed this value). Below this rev value, you aren't engine braking and so fuel must be burnt to stop the engine stalling
The backups note here is the best advise, and if you do use VMWare or something, make sure it supports snapshots. When testing they are the single most useful tool you will have to save from screw ups.
Sure it won't teach you how to fix the mess you just created, but it'll teach you how not to create it in the first place since you can undo/redo until you get it right. This is also one of the powers of using VM's in production. A full VM snapshot is better than any Windows system restore point or remove will ever be.
They hardly need to connect a fibre cable to any particular country. Hell they could anchor on top of one of the undersea cables and just tap straight in and rent the bandwidth directly from the people that own the cable. Hell it's google, they could lay their own damn cable. What more os a concern is if you're using sea water to cool your server you need to filter that water VERY well unless you want the try dealing with the corrosion inside your water blocks.
Or you could setup Excel to trust that spreadsheet (or it's location) so that you don't get prompted with warnings etc everytime. Very easy to do and would remove, what seems to be your biggest gripe.
Trees?
And just to add to the nitpicking, the PhysX cards were only PCI as far as I ever saw. Maybe they didn't need the bandwidth of anything more, but that always struck me as silly to make a PCI card when PCI-E was already available on new motherboards
AMD _is_ a memory company, last time I looked (and I admit it was a few years ago) they made WAY more money from their flash division than from their CPU division
I agree completely, alas while you seem to understand this, the US government seems to willfully ignore it with regard to Iraq. Such a shame.
I'm fairly sure it still is considered bad form ;)
If these rights are self evident, and not man made, could you explain to me why the slaves of your fore-fathers didn't have these rights?
Router != Switch. No typical "office" needs a 40 port router Poster specifically says router. Even a 40 port switch on a linux box would be an interesting experiment to behold. Assuming you were using PCI-E (which is the only way you'd get even remotely decent speed) I still don't think you could get 40 ports into a box You'd have to find a board with exactly the right PCI-E bus layout. As everyone else has mentioned. You just can't make a router that would have enough bus bandwidth or processing power to do this
Short version is, unsurprisingly, it's good at some things and very very bad at others http://tortoisesvn.net/node/41
Put a freeware FTP server on one of them and FTP everything. Windows file copy is TERRIBLE if you want speed
And you would, because thats the "basic" version. Fire up IE and load it on that and see what you're missing out on
I suspect he was talking about laptop CPU's. In which case he's right, very very right.