The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] Early non-Unix filesystems?
Date: Fri, 18 Mar 2016 11:02:23 -0700	[thread overview]
Message-ID: <82f0876de76c486a95d1091c88279546.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <1458323139.767071.553262498.2A8E1982@webmail.messagingengine.com>

> On Fri, Mar 18, 2016, at 13:12, scj at yaccman.com wrote:
>> It may seem strange to us today, but in the context of the day, one of
>> the most radical ideas in Unix was the concept of a file as an array of
>> bytes, with lines separated by newline characters.  Most mainframes had
>> file
>> systems that were more or less decks of cards on disk
>
> Of course, I assume the answer to the question of why everyone didn't do
> that is that there's a trade-off: We take for granted today that you
> can't change a line in the middle of a text file without moving
> everything after it, either by reading the whole thing into memory and
> writing back the changed version, or creating a copy of the file with
> the changes and replacing the original with it afterwards, but I assume
> these "deck of cards" style files had provisions for editing one in the
> middle. You also can't seek to a given line number in a file.
>

At least in my experience, editing the "deck of cards" (and certainly,
editing anything on magnetic tape) was really painful -- there was no way
to move blocks of text around -- you started at the beginning of the file
and had to edit lines in order (one shot per line) until you got to the
end.  You could add lines or delete them, but only when you came to them. 
The editor copied the edited file into an output file, and then you had to
do another step to copy the new version back over the original one.

Shortly after we had a user-writable disc in the Murray Hill computation
center, I (working there as a summer intern) was delighted to copy the
2000 card file I had been lugging around onto disc, and dump the cards. 
As it turns out, my boss also dumped his copy of the card deck.

The first time I tried to edit the deck on disc, I specified the output
file to be equal to the input file.  The program did not check this, and I
ended by nuking about 20% of the card images!  Luckily I had a listing... 
I punched out the trash on the disc and spent an entire weekend
rearranging and repunching the cards to get back to where I had been...

It just goes to show that I should have taken my mother's advice -- before
you throw out a deck of cards, put a rubber band around it!



  reply	other threads:[~2016-03-18 18:02 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  0:48 Warren Toomey
2016-03-18  2:49 ` Greg 'groggy' Lehey
2016-03-18  3:59 ` John Cowan
2016-03-18  5:11   ` Warren Toomey
2016-03-18 17:45     ` John Cowan
2016-03-18  8:00 ` Dave Horsfall
2016-03-18  8:42   ` Peter Jeremy
2016-03-18 13:04     ` Clem Cole
2016-03-18 17:12       ` scj
2016-03-18 17:45         ` Random832
2016-03-18 18:02           ` scj [this message]
2016-03-21 14:11             ` Dave Horsfall
2016-03-21 21:43               ` Greg 'groggy' Lehey
2016-03-21 22:57                 ` scj
2016-03-21 23:05                   ` Lyndon Nerenberg
2016-03-22  0:27                   ` Greg 'groggy' Lehey
2016-03-23 22:46                   ` Dave Horsfall
2016-03-24  0:32                     ` Ron Natalie
2016-03-24  0:43                       ` Milo Velimirovic
2016-03-24  0:47                         ` Ron Natalie
2016-03-24  1:05                     ` Clem Cole
2016-03-23  1:28                 ` Dave Horsfall
2016-03-23  1:51                   ` Milo Velimirovic
2016-03-23  6:49                   ` Greg 'groggy' Lehey
2016-03-23  7:02                     ` Peter Jeremy
2016-03-23  7:12                       ` Greg 'groggy' Lehey
2016-03-23 13:54                       ` Ron Natalie
2016-03-23 16:28                         ` John Cowan
2016-03-23  8:20                     ` Dave Horsfall
2016-03-21 11:07           ` Tony Finch
2016-03-21 12:06             ` John Cowan
2016-03-22  0:13               ` Greg 'groggy' Lehey
2016-03-22  0:48                 ` John Cowan
2016-03-18 17:01 ` Pat Barron
2016-03-22  5:21   ` shawn wilson
2016-03-23  0:54     ` Clem Cole
2016-03-23  1:07       ` Clem Cole
     [not found] <mailman.1.1458266402.23080.tuhs@minnie.tuhs.org>
2016-03-18  2:13 ` Johnny Billquist
2016-03-18  2:36   ` Charles Anthony
2016-03-18  2:26 Noel Chiappa
2016-03-22  0:56 Doug McIlroy
2016-03-23  1:58 Doug McIlroy
     [not found] <mailman.1.1458784801.4499.tuhs@minnie.tuhs.org>
2016-03-24 10:17 ` Johnny Billquist
2016-03-24 11:35   ` Ron Natalie
2016-03-24 11:37     ` Johnny Billquist
2016-03-24 22:50   ` Peter Jeremy
2016-03-24 23:06     ` Johnny Billquist
     [not found]       ` <9CBDF635-2FC9-4855-8419-0413EC0336A7@centurytel.net>
2016-03-25  0:35         ` Johnny Billquist
2016-03-27  0:48       ` Dave Horsfall
2016-03-24 19:13 Nemo
2016-03-24 19:54 ` Milo Velimirović
2016-03-26 21:05   ` Ronald Natalie
2016-03-26 21:34     ` Charles Anthony
2016-03-26 22:09       ` Ronald Natalie
2016-03-28 20:32       ` scj

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=82f0876de76c486a95d1091c88279546.squirrel@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).