Increasing disk density only solves a handful of problems. Unfortunately it can create more problems as well. As disk size increases, more and more applications will become io bound due to contending for the same piece of metal. For many, if not most, organizations that need large amounts of data, increasing per disk density is pointless unless new technology can be introduced to retrieve it at an exponentially faster rate.
500,000,000 downloads... 300,000,000 minutes... 0.6 minutes played per download?
These numbers must include trials and people re-downloading on new phones. I'd be more interested in the number who have PURCHASED Angry Birds.
Good thing the 300 million minutes of Angry Birds daily..
My guess is that people play the game on days other than that on which it was downloaded.
What the parent said. Implying IPv6 is more secure by default is the type of thing that causes people to be lazy about security. IPv6 does not imply built-in encryption or security of any kind.
With my 2 phones, still camera, mini hd camera, and laptop, where the hell am I going to plug in another daily use device that requires constant charging?
That would make sense if they were building things in space made out of ore. Unfortunately, metallurgy requires space, equipment, materials, manpower, fuel, etc. You would also have to deal with having to transport alloying materials to space unless you had some knowledge of other asteroids with appropriate composition.
ZFS has its own problems with scrubbing. Ever have to replace a Zil? Enjoy scrubbing performance loss hell for days/weeks/months depending on the size of your pool.
The incentive is that when the techie helps the sales team, sales is able to generate revenue to pay the techie's salary. I have been in this position thinking I should receive a cut of the sales person's commission when helping to close a deal. Unfortunately, that is just wishful thinking. If you want to make more money sell your soul and join the sales team.
You already mentioned using Perl in your *NIX environments so you could do the same with your Windows boxes too. You could also use Python. Powershell is probably your best option.
You shouldn't be deploying rogue hardware that is not company owned at any place of business let alone a hospital. Have you even considered the compliance ramifications?
Again, what the parent said. If you have a datacenter that serious you do not need people to three-finger-salute your boxes. Remote management was invented for a reason. Granted, people still have to go in there to rack, cable, and kick boxes with misconfigured IPMI or the like. That doesn't mean you design the DC to be comfortable enough to office out of.
> I really hope it doesn’t catch on. I cringe every time I hear it. It’s not catchy or clever, just irritating. It’s right up there with “blogosphere” and “*gate”.
Not as bad as "To the cloud!".
Ok, so I read the zdnet article and the article does appropriately state that the exploit was discovered in 08. However, the zdnet article linked by OP is also a year old.
Are there any OS restrictions? If using FreeBSD or OpenSolaris is an option, ZFS might be a good choice. It is flexible and you can easily manage shares using multiple protocols.
I would think that you would benefit by dropping all SSH attempts that do not match your crypto ACLs, Sure, the firewall still has to deal with your unwanted SSH attempts, but the connections would never make it to the server which prevents brute force attacks and cuts down on system overhead since you aren't spawning processes every time someone makes an invalid connection attempt.
Slashdot Mirror
You stand on a podium and behind a lectern.
This is only because the flies don't know how to give the alcohol soaked food to the female flies first.
Increasing disk density only solves a handful of problems. Unfortunately it can create more problems as well. As disk size increases, more and more applications will become io bound due to contending for the same piece of metal. For many, if not most, organizations that need large amounts of data, increasing per disk density is pointless unless new technology can be introduced to retrieve it at an exponentially faster rate.
500,000,000 downloads... 300,000,000 minutes... 0.6 minutes played per download? These numbers must include trials and people re-downloading on new phones. I'd be more interested in the number who have PURCHASED Angry Birds.
Good thing the 300 million minutes of Angry Birds daily..
My guess is that people play the game on days other than that on which it was downloaded.
But maybe it's because I'm a Sys Admin.
Are you implying that the Start Menu is for power users?
What the parent said. Implying IPv6 is more secure by default is the type of thing that causes people to be lazy about security. IPv6 does not imply built-in encryption or security of any kind.
With my 2 phones, still camera, mini hd camera, and laptop, where the hell am I going to plug in another daily use device that requires constant charging?
That would make sense if they were building things in space made out of ore. Unfortunately, metallurgy requires space, equipment, materials, manpower, fuel, etc. You would also have to deal with having to transport alloying materials to space unless you had some knowledge of other asteroids with appropriate composition.
And then use the corn to make Cheetos and kill 2 birds.
.. they didn't find the official Anonymous membership roster. Oh wait.
ZFS has its own problems with scrubbing. Ever have to replace a Zil? Enjoy scrubbing performance loss hell for days/weeks/months depending on the size of your pool.
The incentive is that when the techie helps the sales team, sales is able to generate revenue to pay the techie's salary. I have been in this position thinking I should receive a cut of the sales person's commission when helping to close a deal. Unfortunately, that is just wishful thinking. If you want to make more money sell your soul and join the sales team.
Uhh, right, because a poorly written web application won't be able to execute SQL if another DBMS is used.
You already mentioned using Perl in your *NIX environments so you could do the same with your Windows boxes too. You could also use Python. Powershell is probably your best option.
You shouldn't be deploying rogue hardware that is not company owned at any place of business let alone a hospital. Have you even considered the compliance ramifications?
Seems awfully similar to http://science.slashdot.org/story/10/11/05/1441251/Scientists-Overclock-Peoples-Brains.
Again, what the parent said. If you have a datacenter that serious you do not need people to three-finger-salute your boxes. Remote management was invented for a reason. Granted, people still have to go in there to rack, cable, and kick boxes with misconfigured IPMI or the like. That doesn't mean you design the DC to be comfortable enough to office out of.
Yep, the site lists battery life as "Wireless Web" battery time. If this is accurate it seems that the battery life is actually better than it was.
> I really hope it doesn’t catch on. I cringe every time I hear it. It’s not catchy or clever, just irritating. It’s right up there with “blogosphere” and “*gate”. Not as bad as "To the cloud!".
I suppose the article does say "more than a year..." but this is really old news. http://www.argeniss.com/research/TokenKidnapping.pdf was published in the summer of 08.
Ok, so I read the zdnet article and the article does appropriately state that the exploit was discovered in 08. However, the zdnet article linked by OP is also a year old.
I suppose the article does say "more than a year..." but this is really old news. http://www.argeniss.com/research/TokenKidnapping.pdf was published in the summer of 08.
Are there any OS restrictions? If using FreeBSD or OpenSolaris is an option, ZFS might be a good choice. It is flexible and you can easily manage shares using multiple protocols.
At my place of employment, we do something similar to http://www.42u.com/images/great-lakes-exhaust-chimney-diagram.jpg. There is no hot air anywhere outside of the cab.
I would think that you would benefit by dropping all SSH attempts that do not match your crypto ACLs, Sure, the firewall still has to deal with your unwanted SSH attempts, but the connections would never make it to the server which prevents brute force attacks and cuts down on system overhead since you aren't spawning processes every time someone makes an invalid connection attempt.
Should the governing bodies of modern sports begin regulating performance enhancing prosthetics? Imagine what this guy could do in a robot dance-off.