That's still once too many.
And still one more than I've ever seen of VxFS. I've managed many, many petabytes of VxFS file systems, and never lost so much as a single file to FS corruption.
(even when I had a coworker manage to import the same VxVM disk group on 2 cluster nodes simultaneously and mount the FS in both places...). A little private region editing and I was able to correct the damage.
Seriously, if you have coaxial jacks, get MoCA bridges. They're awesome.
Welcome to 1992.
The revenge of Taligent.
What's next? Microsoft CyberDog?
... and you think dropping a check off in person will help?
My (previous) mortgage company deposited my mortgage check... and I have no idea whose account got credited for it, but it wasn't mine.
The check cleared, I marked it as such in my bank book, and the only clue something was wrong was when I went from 0 bill collector calls (since I pay all my bills on time) to 4 in one day all about my mortgage. Even after I opened a case, and they started investigating, AND finally credited me back, they STILL had the hounds calling me.
I had to tell them the next call was going to my attorney before they stopped.
So, even dropping that check off in person won't necessarily help. Mistakes can (and do) happen.
Cabletron token-ring 16mbps!
Godspeed, Endeavour. It's a real shame to retire these workhorses. Are they expensive? Yes. Are they exactly what was envisioned in the 70's? No. But, so what? They're still incredible machines that do things mankind has NEVER been able to do before.
The ISS? Wouldn't be possible without the Shuttle.
Hubble? Impossible without Shuttle.
They're workhorses, and it's a damned shame that we, as Americans, have gotten ourselves into such a political quagmire that we can't figure out how to keep man in space. Depressing.
UNLOAD NOVELL.NLM
System halted Wednesday, April 27, 2011 4:30:00 pm EDT
Abend: Page Fault Processor Exception (Error code 00000002)
OS version: Novell NetWare 4.10 November 8, 1994
Running Process: SCRSAVER.NLM
Stack: AC 1F 65 01 E7 66 03 F1 50 CA 65 01 03 00 00 00
D0 1F 65 01 09 00 00 00 B0 81 01 F9 54 CE 65 01
39 67 03 F1 0B CB 65 01 B4 D0 65 01 B0 81 01 F9
Press "Y" to copy diagnostic image to disk.
Otherwise press "X" to exit.
Is that you Vaclav? How many hectares to a tank of kerosene?
Why, oh WHY don't I have moderator points today ?????
You realize that the Apple Airport line supports RADIUS authentication, right?
All that said... The way I'd do it - to make support easy AND keep things secure - is a completely open WiFi access point. No encryption, no passwords required.
The trick is, the access points would only have one destination available - the VPN concentrator. Simple. Enable AES-256 on the VPN concentrator, and you're in business.
Sniff all you want - we'll make more. End users would connect to the VPN the same way from home or from the office WiFi. Easy, cheesy, and keeps the distinction between working at the office and remotely that much smaller.
... then it's between him & Apple. If Apple chose to put his picture up on their website with a huge "DON'T HIRE THIS MAN" banner, then that's between this gentleman & Apple.
By calling him out - publishing his name, social network information, pictures, birthday, etc - Gizmodo is really piling it in. They're making sure - in no uncertain terms - that he is completely & thoroughly embarrassed, humiliated and blackballed from Silicon Valley.
Why? I'm not saying it's illegal, I'm just saying that all it does is make a bad situation worse for this guy.
Yeah, he left the phone behind (if the story's 100% accurate..) Yeah, he works for Apple. But there's no reason to call it out other than just to be mean.
You know, I find that completely over-the-top.
If the story is accurate, then what's the point of exposing the poor sod's name?
What purpose does that serve? The guy's obviously had a rough week; why pile on and make it worse?
It's likely that he's going to be terminated (from his employment, not physically), if he hasn't been already. I'm sure there's some "handling company materials" guideline or somesuch on the books at Apple that will be enforced.
So why expose him publicly?
I don't get it. This just seems like nonsense to me.
Thank you for backing me up. This was absolutely a problem, and I spent many, many, many nights with the engineers replacing the "bad" CPUs with Sombra modules. p/n 501-6009's.... over a thousand of 'em.
The "cosmic rays" thing sounds like a joke, but the Sun engineers really explained it well (once they admitted something was going on) - it makes perfect sense and described the problem to a T.
Sounds a whole lot like the e-cache parity errors in the Sun UltraSPARC-II processors.
If you were never affected by that, consider yourself a lucky person.
particle-caused bitflips are very much real.
Suggest you just sit there and wait till life gets easier.
