When Rebooting Is Not An Option
from the figuring-out-where-the-problem-is dept
It’s a standard refrain. When anything goes wrong with your computer, the first thing everyone expects you to do is reboot and see if that fixes the problem. However, as computer systems and networks become more ubiquitous and more decentralized what if you can’t reboot? If your entire home is automated, and the phone suddenly stops ringing, do you restart the whole house? What if it’s a problem at your neighbors that’s impacting your house? The article is interview with Larry Rudolph at MIT, looking at some of these issues. Rudolph is trying to work on systems that will help to detect where the problem is, thus making it easier to repair. Right now, when there’s a problem, it’s often difficult to tell what’s causing it – and that only gets worse when you have more points of potential failure. He also makes a good point about how wireless makes this all more difficult. When everything is a wired connection, you can easily disconnect wires to try to isolate the problem. When everything connects automatically, you no longer have that option (or, at least, it’s not as simple to disconnect).
Comments on “When Rebooting Is Not An Option”
rebooting
Reboot the whole world. It happened once (the deluge), and might happen again if the Bomb falls into the wrong hands.
I am astounded
…that this thread isn’t stuffed full of jabs at Windows.
Must be a busy day on Slashdot.
Ever heard of QNX?
check out this interview…
I’m not an expert on OS’s, but it sounds like microkernel OS’s for embedded systems have been around and don’t require “reboots”…
hmmm
even I have a linux box that has been happily going as a firewall for 5 years now without rebooting…
Well, we may have had a power outage or two, but since the linux distro is on a write-protected floppy, it hasn’t meant much trouble.
Not a new situation
From the article:
Yeah, I’ve been getting really tired of the daily reboots of the Internet.