6 Aug
2006
6 Aug
'06
7:42 a.m.
Ray Arachelian wrote:
Don wrote:
ssh doesn't seem to follow the standard rules of timeouts. I have left a
ssh session idle once for over 3 days, and it still worked.
--
The real problem with C++ for kernel modules is: the language just sucks.
-- Linus Torvalds
Ray Arachelian wrote:
Exactly. All the *cost* of crossing protection domains
has the implied benefit of *enforcing* those protections.
So, maybe the "wifi server" or "ethernet server" dies and
you lose that *capability* -- but the rest of the system
keeps on ticking.
Even better, you don't lose that functionality, you restart the driver.
So maybe you lose a few packets, or maybe you have to re-establish your
WPA/WEP session to the AP, which shouldn't take all that long. So it's
the equivalent of a network burp. But likely, your applications
(perhaps even ssh sessions) will keep on working, and you don't get owned.