Not just quieter, but using just enough acceleration to get the head there in time for the data to come around also reduces power consumption and -- back on topic -- minimizes contributions to environmental vibration.
One of the things you should take away from all these papers is that "enterprise" disks have hardware and software that compensates for this type of thing, while "consumer" disks don't. If you fill a rack full of Seagate Savvio 15K disks and another rack full of Seagate Barracuda XT 2TB disks, you'll find that the latter suffers mightily from neighbor vibration while the former handles crowding much better.
Wrong. Vibration impacts seek times because the head has to settle over the track. If the track pitch is wider, the head has a bigger target and can settle sooner, but the capacity is less. If the tracks are smaller and closer together, the head takes longer to settle, but the capacity is more. In general disks of a given diameter with fewer tracks will be less impacted by environmental vibration.
OK you got me there. That would indeed be worse. Does anyone even do server-side javascript any more? I know you used to be able to do that with Netscape Enterprise Server back in the dark old days but I haven't heard of people doing it lately.
Plain old vncserver had this capability since at least 1998. I remember using it once at a customer site and their staff gathered around gawking. "He's got xterms in Netscape!"
Ah, I should have been more precise and said "assign" instead of "cast". R assigns a 64-bit int to a double, and therefore loses precision in certain cases.
Workarounds like those you mention are what I wound up using. I did more work outside R and less inside R. These days, for many projects I no do almost nothing in R.
What do you expect the RDBMS to do in this case? It returns a 64-bit integer value. Then R reads it and silently casts it to a double, which silently swizzles the low 12 bits.
The point is that when scientists write software they store big numbers in floats because no sane person needs more precision than that. The idea of huge, exact numbers is foreign to physicists and chemists and statisticians. Especially statisticians.
Only computer programmers and cryptographers need huge, exact integers.
A freetard is an uncompromising advocate of the FSF philosophy. R is a FSF project and is therefore by definition a freetard product. Did you have a point you wanted to make regarding R and 64-bit numbers or did you just come here to act offended?
I think you're right, and I see the same kind of thinking when I ask about 64-bit integers in R. The people who use R are statisticians who can't imagine why a double isn't close enough. The people who complain about it are the computer programmers who are trying to use 64-bit exact fields to merge two datasets etc.
FWIW, GNU R, the freetard knockoff of S, also can't do anything with 64-bit numbers. It stores them in a double, which gives you 52 bits of exact integers and beyond that it's approximate. This can really bite you in the ass if you aren't aware of it... and it's not documented anywhere except in code. It can be especially bad if you try to read a BIGINT (64-bit integer) value via RODBC, which silently truncates the value to 52 bits.
Well, you're wrong. Current wifi chips which come loaded with "world" firmware will never broadcast on 5GHz channels unless they first see beacons from an AP on that channel. These channels are marked for passive scanning only. When a device sees a beacon on that channel then it assumes that local regulations allow wifi on that channel, and the chip will enable it. The chips used in access points, by contrast, generally are shipped with locale-specific firmware, or at least locale-specific black box operating systems.
This is why the wifi card out of your laptop can't really be used as a decent access point. You can't get them to ever broadcast beacons on the 5GHz band.
Perhaps not, but the video you're seeing here is significantly degraded from what the gunner sees in the helicopter. For one thing, his TV feed hasn't been ripped and re-encoded. For another he can just look out the freaking window. In an Apache the gunner sits in front.
This is not what war is like, this is what cowardice looks like. If armored infantry are so afraid of 8 photographers walking down the middle of the street that they have to hide inside their armored vehicles waiting for a helicopter to investigate, then those infantrymen are chickenshits. Plain and simple. I'm sure you'll say that the grunts just want to make sure they don't get dead, but the fact is that they're armed to the teeth and in a city crawling primarily with unarmed civilians. They are going to have to be men and not hide behind FLIR gun pods.
"What's wrong with this" is they had mounted infantry 100m away. The gunship crew could have just called in the coordinates and had the eyeballs check it out. They might have seen that the "AK-47" was a tripod and the "RPG" was a camera lens.
And there was no excuse for blowing away the minivan trying to carry off the wounded survivor.
Small group insurance is _much_ better than individual because group policies -- even for just two people -- must be issued. Individuals can be turned away but groups cannot. At least that's the law in California.
Slashdot Mirror
Alternate theory: you're a total fucking idiot.
Not just quieter, but using just enough acceleration to get the head there in time for the data to come around also reduces power consumption and -- back on topic -- minimizes contributions to environmental vibration.
One of the things you should take away from all these papers is that "enterprise" disks have hardware and software that compensates for this type of thing, while "consumer" disks don't. If you fill a rack full of Seagate Savvio 15K disks and another rack full of Seagate Barracuda XT 2TB disks, you'll find that the latter suffers mightily from neighbor vibration while the former handles crowding much better.
Wrong. Vibration impacts seek times because the head has to settle over the track. If the track pitch is wider, the head has a bigger target and can settle sooner, but the capacity is less. If the tracks are smaller and closer together, the head takes longer to settle, but the capacity is more. In general disks of a given diameter with fewer tracks will be less impacted by environmental vibration.
See also: http://www.zazzle.com/css_is_awesome_mug-168716435071981928
Adobe Reader has had byte-range HTTP since ever. It would also have just downloaded the first page and then downloaded the rest on demand.
If you could move on to being completely speechless that would be an improvement.
OK you got me there. That would indeed be worse. Does anyone even do server-side javascript any more? I know you used to be able to do that with Netscape Enterprise Server back in the dark old days but I haven't heard of people doing it lately.
The difference between a 4-digit user ID and a 7-digit user ID becomes increasingly clear.
This piece of crap is a JavaScript/HTML5 hack plus a server-side Java process. The worst of both worlds!
Plain old vncserver had this capability since at least 1998. I remember using it once at a customer site and their staff gathered around gawking. "He's got xterms in Netscape!"
Ah, I should have been more precise and said "assign" instead of "cast". R assigns a 64-bit int to a double, and therefore loses precision in certain cases.
Workarounds like those you mention are what I wound up using. I did more work outside R and less inside R. These days, for many projects I no do almost nothing in R.
What do you expect the RDBMS to do in this case? It returns a 64-bit integer value. Then R reads it and silently casts it to a double, which silently swizzles the low 12 bits.
Since YAAS, should I stand back?
The point is that when scientists write software they store big numbers in floats because no sane person needs more precision than that. The idea of huge, exact numbers is foreign to physicists and chemists and statisticians. Especially statisticians.
Only computer programmers and cryptographers need huge, exact integers.
A freetard is an uncompromising advocate of the FSF philosophy. R is a FSF project and is therefore by definition a freetard product. Did you have a point you wanted to make regarding R and 64-bit numbers or did you just come here to act offended?
I think you're right, and I see the same kind of thinking when I ask about 64-bit integers in R. The people who use R are statisticians who can't imagine why a double isn't close enough. The people who complain about it are the computer programmers who are trying to use 64-bit exact fields to merge two datasets etc.
FWIW, GNU R, the freetard knockoff of S, also can't do anything with 64-bit numbers. It stores them in a double, which gives you 52 bits of exact integers and beyond that it's approximate. This can really bite you in the ass if you aren't aware of it ... and it's not documented anywhere except in code. It can be especially bad if you try to read a BIGINT (64-bit integer) value via RODBC, which silently truncates the value to 52 bits.
Well, you're wrong. Current wifi chips which come loaded with "world" firmware will never broadcast on 5GHz channels unless they first see beacons from an AP on that channel. These channels are marked for passive scanning only. When a device sees a beacon on that channel then it assumes that local regulations allow wifi on that channel, and the chip will enable it. The chips used in access points, by contrast, generally are shipped with locale-specific firmware, or at least locale-specific black box operating systems.
This is why the wifi card out of your laptop can't really be used as a decent access point. You can't get them to ever broadcast beacons on the 5GHz band.
ssh -c arcfour
Or, on certain builds
ssh -c none
Perhaps not, but the video you're seeing here is significantly degraded from what the gunner sees in the helicopter. For one thing, his TV feed hasn't been ripped and re-encoded. For another he can just look out the freaking window. In an Apache the gunner sits in front.
This is not what war is like, this is what cowardice looks like. If armored infantry are so afraid of 8 photographers walking down the middle of the street that they have to hide inside their armored vehicles waiting for a helicopter to investigate, then those infantrymen are chickenshits. Plain and simple. I'm sure you'll say that the grunts just want to make sure they don't get dead, but the fact is that they're armed to the teeth and in a city crawling primarily with unarmed civilians. They are going to have to be men and not hide behind FLIR gun pods.
"Hearts and minds" and all that.
Maybe if you refrain from commenting until after you watch the fucking video, you will not appear to be profoundly ignorant.
Maybe you can make a screen shot that shows the rifles and the RPG. All I see is two men with camera lenses and one with a tripod.
"What's wrong with this" is they had mounted infantry 100m away. The gunship crew could have just called in the coordinates and had the eyeballs check it out. They might have seen that the "AK-47" was a tripod and the "RPG" was a camera lens.
And there was no excuse for blowing away the minivan trying to carry off the wounded survivor.
This isn't really new, and it's not just browsers. Most programs will take anything that can be interpreted by strtoul(3) as an IP address.
# ping 0xdeadbeef
PING 0xdeadbeef (222.173.190.239) 56(84) bytes of data.
From 219.146.113.214 icmp_seq=1 Time to live exceeded
Small group insurance is _much_ better than individual because group policies -- even for just two people -- must be issued. Individuals can be turned away but groups cannot. At least that's the law in California.