What? That's patently absurd. It may be available at the office or at home, but anywhere else you're at least as likely to have wireless, and in many, many places, it's your only option.
The hotel I stayed at last week only had wireless.
The restaurants I ate at had only wireless.
My local coffee shop only has wireless.
Remember, the common image of the Apple user is of the screenplay writer sitting at Starbucks. Ethernet does no good in that scenario.
I have a Macbook Air and I bought the USB-to-Ethernet dongle. I never used it. I can see it being essential for some people, but certainly not for everyone. Apple can't be everything to everyone.
The OP was being pretty facetious, but mentioned specific titles (Mario Kart, not Mario in general.) It's pretty unfair to bitch about them producing the same game over and over when it's really just the character appearing over and over.
Quality? Nintendo USED to be about quality back in the NES days. That was 20 years ago. 75% of Wii games since it's inception have been shovelware.
Nintendo allowed plenty of third-party shovelware on the NES and SNES. Nintendo's first-party titles are generally pretty good.
Hell, does the new controller won't even support Dead Space/GTA/etc.
What is this i don't even.
But that said, I think the Wii U is likely to flop. Nintendo was smart with the Wii to sell it for profit from day one (unlike most other console makers), but they got lucky that the gimmicky controls, the hype, and shortages inflated the demand. I'm not sure lightning is going to strike twice. And that controller looks horribly awkward: http://www.viddler.com/v/7d40ebdc?secret=78568394
Could be that someone wants us to think that Black Chamber is implementing SCORPION STARE. Or it could just be trials. Regardless, someone is apparently worried about CASE NIGHTMARE GREEN.
See, I think that email is broken, and that we've been patching it for over a decade to try to maintain usability. All the spam, all the broken clients, all the broken servers, all the phishing...it was built when there was a great deal of trust between providers, and when that trust was broken, email was broken.
There's another debate--whether we can do anything about it at this point, even if it is manmade. The US pollutes a lot, but we've offshored so much of our production that the vast amounts of pollutants are not coming from us anymore. Global warming is a global challenge, and if the US disappeared from the face of the Earth, it wouldn't have much of an effect (whether or not you ascribe to the man-made or cyclical view.)
I don't think I want to live in a world where the cops will only investigate crimes if the financial loss due to the crime is greater than the cost of the investigators time.
Actually, as a supporter of the 2nd amendment, maybe I do want to live in that world.
The truth is, there's a lot of crime and not a lot of money for cops. And for most individuals who are burglarized, there's rarely enough evidence to even begin an investigation. The best you can usually hope for is to have serial numbers for some of your stuff and that when the thief screws up and gets caught, that you'll be able to get your stuff back then. More likely it's already been sold, though.
The other truth is that all jobs have perks. Some people get to read Slashdot during the day. Some people don't have to pay for their own car or cell phone. And some people get more immediate attention from the police. Is it fair? No, but all of these things happen on a daily basis, and there's little sign that they will ever change.
Did you notice that they were using Find My iPhone? It's an Apple service which requires opting-in on the part of the phone's user (pre-losing the phone, of course.)
The joke you should have made has to do with not being able to find ones ass with 10 cops and a map. These guys had GPS from the phone (via consent of the victim or certainly his father) and couldn't find it. That takes a spectacular level of incompetence.
I replied to that post, not focusing on what he said (and what you reiterated) but instead on how so many geeks seem to discount a solution if it's imperfect.
Yeah, I threadjacked. You'll get over it.
But if you read through the comments, lots of people noted that being in sync is more important than accuracy. That said, you still have to worry about transferring patients to other offices, hospitals, etc. and the timing of doses there. Accuracy will still matter to a lot of people, and trading accuracy for consistency might not be the best thing to do.
The fact that the one clock had been allowed to drift so far was user error, which any system can fall victim to.
Per the summary, in four hospitals, on average, medical devices were off by 24 minutes. Per the article, 20% of the 1700 devices checked were off by more than 30 minutes. This is not "one clock [being off]", but it looks like it was one clock (or rather, it was the difference between two clocks which were used during the same procedure) which brought the problem to everyone's attention.
Even if you just reset the clocks at every DST change as a matter of policy, they shouldn't drift that far.
For all of the devices they're talking about, that would be an intense job.
The GGP did make a valid point that it moves from multiple points of failure to a single point of failure that can be manipulated to wreak havoc.... if someone monkeyed with the time server
NTP doesn't work that way. If the server returns a time which is too far from the client's clock, the client won't adjust itself. You could log these failures and find systemic problems (or monkeying) pretty easily.
Alternatively, the NTP server could get slowly out of sync, deliberately or otherwise. As others have pointed out, that's okay.
The really pathological thing that you could do is intentionally return different data for each client. Over time, you could end up with wildly out-of-sync clocks. This could also be verified fairly easily, though, requiring the compromise of multiple systems in order to hide.
if there were bugs with the DST flag
DST flag? NTP doesn't know anything about DST. DST (and time zone for that matter) is the responsibility of the client. This sort of thing is necessarily already accounted for, or we'd have people getting double doses or skipping doses right now.
So the GGP isn't wrong that the potential for harm in the event of a serious failure is much greater; but it doesn't matter because the potential for detection is commensurately greater.
The truth is, this sort of thing probably rarely causes harm in the first place. That doesn't mean that things can't be improved. Harm as a risk over time may still be reduced by using NTP, since as you point oint, detection is greater. Plus, all this talk of using "an NTP server" is really only part of the solution. You'd use multiple NTP servers in disparate locations heavily locked down and taking the time multiple sources so that the voting algorithms can work correctly.
For one simple service like NTP, you can pretty well secure it to the point where I'd be comfortable letting it run my life support system. The risks of tampering by anyone other than the admin who runs it could be minimized to practically zero. And insiders are almost always going to be able to wreak havoc on a system.
I got a Droid about 3 months after they came out. They definitely weren't using Chrome. It was one of my gripes. Chrome for Android was released in Beta 4-5 months ago. Before that, you just had Browser. Both can coexist on a phone.
It's not what most people mean when they say, "Drive failure," and the URE could have happened before the RAID was ever put into degraded mode (it could have been the first failure, just no one noticed it.)
The old wisdom is that "RAID is not a backup." So RAID5, RAID6..doesn't matter, you should be backing up regardless.
Tape is still probably the cheapest medium for backups, though you have to invest in the drives as well (and those can be in the thousands of dollars.)
I use online backups to a remote host along with a large drive which is offline most of the time and rotated with a few others. I'm just getting into ZFS and snapshots, with which I can more easily take frequent backups. Unfortunately, I don't think that helps with the UREs since snapshots still only store the data once. ZFS itself should help with UREs if scrubbed regularly.
The problem with optical is that the density ratios are so poor and the media is very fragile. Bluray discs can get up to about 50GB now, which means you need 20 to back up 1TB. With more discs, the likelihood of at least one of them failing increases, not to mention you need to store them.
Even the high end SAN makers know this and tell people to always use RAID 6 on the backend, just because the window of time that it takes to rebuild a drive is so long these days that it can easily allow for a second drive failure to happen with no protection.
It's not just another drive failing--it's unrecoverable read errors (UREs). You might not know that a sector is unreadable until it's too late--if you discover it during a resliver of a RAID5, you are seriously out of luck. With very high data densities per disk, the chances of a URE are high.
So you're right--I/O speed is important. Also important is resiliency. If these don't scale along with the sizes, I think these will be considerably less useful than most people hope.
I don't know Exchange, but unless the e-mail actually triggers the Outlook dialog which prompts for the password, I don't think it matters. Users will reply with their password to phishing mails. Setting up a system where you are e-mailed when you've screwed up isn't going to help that--it's just going to make spear phishing more viable.
Slashdot Mirror
Ethernet is ubiquitous!
What? That's patently absurd. It may be available at the office or at home, but anywhere else you're at least as likely to have wireless, and in many, many places, it's your only option.
The hotel I stayed at last week only had wireless.
The restaurants I ate at had only wireless.
My local coffee shop only has wireless.
Remember, the common image of the Apple user is of the screenplay writer sitting at Starbucks. Ethernet does no good in that scenario.
I have a Macbook Air and I bought the USB-to-Ethernet dongle. I never used it. I can see it being essential for some people, but certainly not for everyone. Apple can't be everything to everyone.
Want me to keep going?
The OP was being pretty facetious, but mentioned specific titles (Mario Kart, not Mario in general.) It's pretty unfair to bitch about them producing the same game over and over when it's really just the character appearing over and over.
Quality? Nintendo USED to be about quality back in the NES days. That was 20 years ago. 75% of Wii games since it's inception have been shovelware.
Nintendo allowed plenty of third-party shovelware on the NES and SNES. Nintendo's first-party titles are generally pretty good.
Hell, does the new controller won't even support Dead Space/GTA/etc.
What is this i don't even.
But that said, I think the Wii U is likely to flop. Nintendo was smart with the Wii to sell it for profit from day one (unlike most other console makers), but they got lucky that the gimmicky controls, the hype, and shortages inflated the demand. I'm not sure lightning is going to strike twice. And that controller looks horribly awkward: http://www.viddler.com/v/7d40ebdc?secret=78568394
Could be that someone wants us to think that Black Chamber is implementing SCORPION STARE. Or it could just be trials. Regardless, someone is apparently worried about CASE NIGHTMARE GREEN.
The post to which I responded said:
If I say I want to kill somebody, it's a threat, and should not be considered as "free speech" anymore
Uh, if you say you want to kill somebody, I don't think that should be considered a threat. If you say you are going to, sure.
See, I think that email is broken, and that we've been patching it for over a decade to try to maintain usability. All the spam, all the broken clients, all the broken servers, all the phishing...it was built when there was a great deal of trust between providers, and when that trust was broken, email was broken.
There's another debate--whether we can do anything about it at this point, even if it is manmade. The US pollutes a lot, but we've offshored so much of our production that the vast amounts of pollutants are not coming from us anymore. Global warming is a global challenge, and if the US disappeared from the face of the Earth, it wouldn't have much of an effect (whether or not you ascribe to the man-made or cyclical view.)
You could have done so much worse. I've seen hotlinked images replaced with goatse.
If the phone is wiped, it won't work. In this case, though, the phone was broadcasting its location.
I realize that I was ambiguous. The sound is distinctive, not the feature.
And needed was autocorrected from muted somehow....
Don't even has to call it. You can tell the phone to make a noise that can't be needed.
It's distinctive to the find my iPhone feature, and it is pretty damning.
I don't think I want to live in a world where the cops will only investigate crimes if the financial loss due to the crime is greater than the cost of the investigators time.
Actually, as a supporter of the 2nd amendment, maybe I do want to live in that world.
The truth is, there's a lot of crime and not a lot of money for cops. And for most individuals who are burglarized, there's rarely enough evidence to even begin an investigation. The best you can usually hope for is to have serial numbers for some of your stuff and that when the thief screws up and gets caught, that you'll be able to get your stuff back then. More likely it's already been sold, though.
The other truth is that all jobs have perks. Some people get to read Slashdot during the day. Some people don't have to pay for their own car or cell phone. And some people get more immediate attention from the police. Is it fair? No, but all of these things happen on a daily basis, and there's little sign that they will ever change.
Typical anti-LE first-post karma-grabbing reply.
Did you notice that they were using Find My iPhone? It's an Apple service which requires opting-in on the part of the phone's user (pre-losing the phone, of course.)
The joke you should have made has to do with not being able to find ones ass with 10 cops and a map. These guys had GPS from the phone (via consent of the victim or certainly his father) and couldn't find it. That takes a spectacular level of incompetence.
Lots of people actually pointed that out. In fact, two replies up, dgatwood noted it http://slashdot.org/comments.pl?sid=2869687&cid=40090419
I replied to that post, not focusing on what he said (and what you reiterated) but instead on how so many geeks seem to discount a solution if it's imperfect.
Yeah, I threadjacked. You'll get over it.
But if you read through the comments, lots of people noted that being in sync is more important than accuracy. That said, you still have to worry about transferring patients to other offices, hospitals, etc. and the timing of doses there. Accuracy will still matter to a lot of people, and trading accuracy for consistency might not be the best thing to do.
Luckily, with NTP, you can get both.
The fact that the one clock had been allowed to drift so far was user error, which any system can fall victim to.
Per the summary, in four hospitals, on average, medical devices were off by 24 minutes. Per the article, 20% of the 1700 devices checked were off by more than 30 minutes. This is not "one clock [being off]", but it looks like it was one clock (or rather, it was the difference between two clocks which were used during the same procedure) which brought the problem to everyone's attention.
Even if you just reset the clocks at every DST change as a matter of policy, they shouldn't drift that far.
For all of the devices they're talking about, that would be an intense job.
The GGP did make a valid point that it moves from multiple points of failure to a single point of failure that can be manipulated to wreak havoc. ... if someone monkeyed with the time server
NTP doesn't work that way. If the server returns a time which is too far from the client's clock, the client won't adjust itself. You could log these failures and find systemic problems (or monkeying) pretty easily.
Alternatively, the NTP server could get slowly out of sync, deliberately or otherwise. As others have pointed out, that's okay.
The really pathological thing that you could do is intentionally return different data for each client. Over time, you could end up with wildly out-of-sync clocks. This could also be verified fairly easily, though, requiring the compromise of multiple systems in order to hide.
if there were bugs with the DST flag
DST flag? NTP doesn't know anything about DST. DST (and time zone for that matter) is the responsibility of the client. This sort of thing is necessarily already accounted for, or we'd have people getting double doses or skipping doses right now.
So the GGP isn't wrong that the potential for harm in the event of a serious failure is much greater; but it doesn't matter because the potential for detection is commensurately greater.
The truth is, this sort of thing probably rarely causes harm in the first place. That doesn't mean that things can't be improved. Harm as a risk over time may still be reduced by using NTP, since as you point oint, detection is greater. Plus, all this talk of using "an NTP server" is really only part of the solution. You'd use multiple NTP servers in disparate locations heavily locked down and taking the time multiple sources so that the voting algorithms can work correctly.
For one simple service like NTP, you can pretty well secure it to the point where I'd be comfortable letting it run my life support system. The risks of tampering by anyone other than the admin who runs it could be minimized to practically zero. And insiders are almost always going to be able to wreak havoc on a system.
This is correct, but you have masked the real problem with the GP post.
The clocks are wrong now.
Which means that getting them even closer to right is better than nothing at all.
GP is your classic "too smart" idiot geek: if a solution isn't perfect, it's not a solution.
I got a Droid about 3 months after they came out. They definitely weren't using Chrome. It was one of my gripes. Chrome for Android was released in Beta 4-5 months ago. Before that, you just had Browser. Both can coexist on a phone.
The fourth FAQ here indicates that they are different: https://developers.google.com/chrome/mobile/docs/faq
Absolutely true.
It's not what most people mean when they say, "Drive failure," and the URE could have happened before the RAID was ever put into degraded mode (it could have been the first failure, just no one noticed it.)
The old wisdom is that "RAID is not a backup." So RAID5, RAID6..doesn't matter, you should be backing up regardless.
Tape is still probably the cheapest medium for backups, though you have to invest in the drives as well (and those can be in the thousands of dollars.)
I use online backups to a remote host along with a large drive which is offline most of the time and rotated with a few others. I'm just getting into ZFS and snapshots, with which I can more easily take frequent backups. Unfortunately, I don't think that helps with the UREs since snapshots still only store the data once. ZFS itself should help with UREs if scrubbed regularly.
The problem with optical is that the density ratios are so poor and the media is very fragile. Bluray discs can get up to about 50GB now, which means you need 20 to back up 1TB. With more discs, the likelihood of at least one of them failing increases, not to mention you need to store them.
Even the high end SAN makers know this and tell people to always use RAID 6 on the backend, just because the window of time that it takes to rebuild a drive is so long these days that it can easily allow for a second drive failure to happen with no protection.
It's not just another drive failing--it's unrecoverable read errors (UREs). You might not know that a sector is unreadable until it's too late--if you discover it during a resliver of a RAID5, you are seriously out of luck. With very high data densities per disk, the chances of a URE are high.
So you're right--I/O speed is important. Also important is resiliency. If these don't scale along with the sizes, I think these will be considerably less useful than most people hope.
GP was talking about system/network passwords, not some website.
I don't think that's clear, but at this point arguing further is pointless.
I don't know Exchange, but unless the e-mail actually triggers the Outlook dialog which prompts for the password, I don't think it matters. Users will reply with their password to phishing mails. Setting up a system where you are e-mailed when you've screwed up isn't going to help that--it's just going to make spear phishing more viable.