Joshua Dean, a former quality auditor at Boeing supplier Spirit AeroSystems and one of the first whistleblowers to allege Spirit leadership had ignored manufacturing defects on the 737 MAX, died Tuesday morning after a struggle with a sudden, fast-spreading infection.
Known as Josh, Dean lived in Wichita, Kan., where Spirit is based. He was 45, had been in good health and was noted for having a healthy lifestyle.
He died after two weeks in critical condition, his aunt Carol Parsons said.
Spirit spokesperson Joe Buccino said: “Our thoughts are with Josh Dean’s family. This sudden loss is stunning news here and for his loved ones.”
Dean had given a deposition in a Spirit shareholder lawsuit and also filed a complaint with the Federal Aviation Administration alleging “serious and gross misconduct by senior quality management of the 737 production line” at Spirit.
Spirit fired Dean in April 2023, and he had filed a complaint with the Department of Labor alleging his termination was in retaliation for raising concerns related to aviation safety.
Parsons said Dean became ill and went to the hospital because he was having trouble breathing just over two weeks ago. He was intubated and developed pneumonia and then a serious bacterial infection, MRSA.
His condition deteriorated rapidly, and he was airlifted from Wichita to a hospital in Oklahoma City, Parsons said. There he was put on an ECMO machine, which circulates and oxygenates a patient’s blood outside the body, taking over heart and lung function when a patient’s organs don’t work on their own.
His mother posted a message Friday on Facebook relating all those details and saying that Dean was “fighting for his life.”
Well that's technically correct, but if you're so dependent on disk cache for system performance that you can't live without it then you really need to look at doing an upgrade.
When a box swap deaths, it usually struggles to actually fill swap enough to have the kernel still OOM kill it at any point. Generally the massive performance impact of swapping just slows the app down to the point of being useless, along with the entire rest of the box. Disk cache should not be a concern during these abnormal events.
A lot of reasonably competent geeks just never get deep into networking, and VPNs can be overwhelming. It doesn't really help that for a long time it was all IPSec which basically you need to learn voodoo to manage. Thankfully we have much better tools now, but it's still just a tech layer that many people don't touch frequently.
The tailscale client should have created an interface, but I've never used it on a box also running wg. You don't have a tailscale specific interface in ip addr show at all? That's.... odd.
Relay "ams" means you're using tailscales DERP node in amsterdam, this is expected if you don't have direct connectivity through your firewall. Since you opened the ports that's unusual and worth looking into, but I'd worry about that after you get basic connectivity.
So to confirm your behavior, you can tailscale ping each other fine and tailscale ping to the internal network. You cannot however ping from the OS to the remote internal network?
Have you checked your routing tables to make sure the tailscale client added the route properly?
Also have you checked your firewall rules? If you're using ipfw or something, try just turning off iptables briefly and see if that lets you ping through.
I can't tell what this does from the site linked, but I said the apps name out loud and my cat came running.