Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!pasteur!jwz@teak.Berkeley.EDU
From: jwz@teak.Berkeley.EDU (Jamie Zawinski)
Newsgroups: comp.sys.ti.explorer
Subject: warm booting
Message-ID: <18448@pasteur.Berkeley.EDU>
Date: 17 Oct 89 01:40:13 GMT
Sender: news@pasteur.Berkeley.EDU
Lines: 12

Ok, WHY is it that warm booting boots the file system and resets the network?
Usually when I warm boot, it's because I've done something stupid and crashed
the machine.  That does NOT mean that I want all of my open files to abort, or
that I want all of my telnet connections to wedge.  If I was of that mindset,
I'd probably be off in the corner right now flagelating myself in search of 
enlightenment.

It may be that warm-booting hardware-resets the ethernet board, making open
connections invalid (?) but the filesystem is just this big tree-structure in
memory.  I can't see any reason to re-read that other than plain spitefulness.

(Ok I'm done ranting now.)			-- Jamie