🚀 go-pugleaf

In article <1992Sep8.105655.712@macc.wisc.edu> anderson@macc.wisc.edu (Jess Anderson) writes:
   In article <1992Sep7.215151.2517@metrosoft.com> gvh@metrosoft.com (Gordon Van Huizen) writes:
      In article <1992Sep7.041747.10597@ccsun7.csie.nctu.edu.tw> jypai@ccnext.csie.nctu.edu.tw writes:
         (reboot is the last solution I want)

      It's the last solution we ALL want, but alas the only solution
      we have...

   what is so all-fired awful about rebooting a computer?

Even if it's not a server that affects dozens of users, it's
inconvenient to the individual who has lots of windows open.  

   "This thing could stop dead in its tracks at any second, without
   warning.  Am I in the best possible position for this unhappy event
   right now?  If not, get right with the Lord of Silicon!"

Even if none of the applications have unsaved work, their presence
(and even the location, iconification, and overlapping arrangement of
the windows) is a useful state-saver.  When I hang up from a phone
call, I use my window stack to remind myself what I was doing before
the interruption.  If the system reboots, all that state is lost.

   But booting, especially in the standalone or tiny network case,
   takes a couple minutes at most and is a whole lot better than
   sitting and listening to your disk seek its fool heads off while
   you twiddle your toes waiting for a cursor position update.

An ever-growing swap file is a bug that no user should tolerate, and
that any vendor should be embarassed to let out the door, even on its
first limited-circulation alpha prerelease of a new OS version.
Frequent rebooting is not an acceptable solution to an OS bug.

   Besides, there's sysadmin machismo to be considered, right?  We're
   supposed to be the masters of it all, eating disasters for a light
   lunch and all that.

Where's the machismo in rebooting a PC on steroids, with a key labeled
"Power" on the keyboard?  I bump it half the times I go groping for
the "~" or "\" keys.