The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] pre-more pager?
Date: Wed, 08 Nov 2017 18:01:53 -0800	[thread overview]
Message-ID: <9182d33ee300bdbe18443296cf16364bfb7741f0@webmail.yaccman.com> (raw)
In-Reply-To: <1510168964.1261540.1166077456.49865F48@webmail.messagingengine.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1800 bytes --]

"Well, in the beginning, there was paper. You didn't need to "page"
 because you had actual pages you could hold in your hand (if not the
 manual typeset as an actual book, then the printed output from the
 teletype)." 

Paper indeed...    I had a model 37 teletype at home, and would
bring home boxes of paper and carefully arrange the box so that the
blank paper feeding the terminal did not get tangled up with the
"used" paper spewing out of the teletype.  A second box for the used
paper was handy.

In the early Unix days, the file system had two kinds of tiles --
small files and "large" files.   As a file grew, there was a moment
when the inodes were rewritten to go from small to large.  And if the
system crashed during this process, a lot of stuff could get messed up
or deleted.  It usually took a few minutes for the system to get back
online, so I kept a highlighter by the terminal, and when the system
crashed I would reel back the used paper and highlight those lines
that I needed to reenter.  When the system came back, I copied the
lines that had been lost and pressed on.

One day, I had spent a couple of hours in an intense debugging session
when my wife called me to lunch.  I didn't save my stuff, and was
very unhappy to return an hour later and discover the system had
crashed.   I was even more unhappy to discover that, while I was at
lunch, our cat had found the box of used paper and used it as a litter
box.  After the shock wore off, I picked up my highlighter anyway and
marked the soggy lines I needed to retype...

It was never more true that debugging was a smelly job...

Steve 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171108/a6f9d466/attachment.html>


  parent reply	other threads:[~2017-11-09  2:01 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 18:54 Will Senn
2017-11-08 18:59 ` Clem Cole
2017-11-08 19:06 ` Arthur Krewat
2017-11-08 19:31   ` Jeremy C. Reed
2017-11-08 22:43   ` Dave Horsfall
2017-11-08 22:47     ` Arthur Krewat
2017-11-08 23:21       ` Dave Horsfall
2017-11-09  4:38         ` Will Senn
2017-11-09 13:18           ` Dan Cross
2017-11-09 14:29             ` Will Senn
2017-11-09 20:53           ` Dave Horsfall
2017-11-10  0:15             ` Arthur Krewat
2017-11-10  2:14               ` Ralph Corderoy
2017-11-08 19:12 ` Bakul Shah
2017-11-08 19:22 ` Random832
2017-11-08 21:18   ` Will Senn
2017-11-08 21:59     ` Ron Natalie
2017-11-08 22:00     ` Clem Cole
2017-11-08 22:18       ` Will Senn
2017-11-09  2:01   ` Steve Johnson [this message]
2017-11-09  2:16     ` Lyndon Nerenberg
2017-11-08 19:29 ` Forrest, Jon
2017-11-08 19:43   ` Ron Natalie
2017-11-08 21:03   ` Mark Green
2017-11-08 19:23 Noel Chiappa
2017-11-08 20:02 Noel Chiappa
2017-11-08 20:11 ` Forrest, Jon
2017-11-10  5:26   ` Random832
2017-11-10  7:31     ` Otto Moerbeek
2017-11-08 20:18 ` Clem Cole
2017-11-08 20:28   ` Ron Natalie
2017-11-08 22:47 ` Dave Horsfall
2017-11-08 20:28 Noel Chiappa
2017-11-08 22:02 Paul Ruizendaal
2017-11-08 22:20 ` Will Senn
2017-11-08 22:58 Doug McIlroy
2017-11-09 13:33 Doug McIlroy
2017-11-09 16:19 Norman Wilson
2017-11-09 16:48 ` Arthur Krewat
2017-11-09 17:19   ` Steve Nickolas
2017-11-09 18:15     ` Don Hopkins
2017-11-09 18:26     ` Arthur Krewat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9182d33ee300bdbe18443296cf16364bfb7741f0@webmail.yaccman.com \
    --to=scj@yaccman.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).