🚀 go-pugleaf

In article <4gik4v$d1m@cville-srv.wam.umd.edu>, veakblad@Glue.umd.edu
(David T. Wang) wrote:

    Gregory L Hansen (ghansen@isc.sjsu.edu) wrote:
    : In article <3129FECE.513A53A6@mindspring.com>,
    : Damir Smitlener  <damir@mindspring.com> wrote:
    
    : >Oh, yeah, cleaning up a core dump is so much more trouble than
having to reboot
    : >after a MacOS crash. Yep, typing "rm core" is such a hassle compared to
    : >restarting the computer and restarting the other applications that
were running
    : >and redoing whatever was lost in those other apps because of the crash.
    
    : Is that how you clean it up?  I was not aware of that.  I'll have to
try to 
    : remember that, for the next time UNIX crashes on me.
    
    huh? core dumps in general refer to the "dump" of the memory image of the 
    program after the OS kills the program.  If Unix, the OS, actually 
    crashes, I don't hink that you'd end up with a core dump.  Then again, 
    I've never had Unix crash on me, only errant programs, which leave a 
    "core" after they die.
    
    : I know, it's right there in man with everything else.  Somewhere.  And 
    : easy enough to find if you read the whole friggin' database starting from 
    : page 1!

This certainly does not reflect my experience with unix machines. Just
today, my X-terminal crashed while trying to run a 3270 emulator. In my
experience, the ratio of Mac reboots to Sun reboots is no better than two
or three to one. Unix may not crash in the Mac sense of the word, but they
become unusable fairly often. The only solution seems to be a shutdown and
restart. Many times they can be taken down somewhat gracefully, but still
they must be rebooted. And they take a _lot_ longer to boot than MacOS.

Tom