From: Clem Cole <clemc@ccc.com>
To: Aharon Robbins <arnold@skeeve.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Scratch files in csh
Date: Wed, 5 Jun 2019 09:31:14 -0400 [thread overview]
Message-ID: <CAC20D2NoBXgKw5DRPjmOV4rXX5M_dx4oUzUCE32Wur46HUmc_A@mail.gmail.com> (raw)
In-Reply-To: <201906051250.x55CoSxK005467@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
Indeed - that's how UCB Systems worked. /tmp was a small scratch disk and
anything there was suspect. Scratch files were not a CShell feature, they
were a UNIX feature, very much needed on the 16-bit address PDP-11 where it
was developed.
The idea originally became popular with Dennis's C Compiler which used
it for the intermediate files between the passes on the PDP-11. On a
large public system like a University, /tmp would fill with cruft. It was
traditionally removed on reboot. But that was not good enough for
production systems that did not reboot.
My memory is that there was a script that was similar to what Aharon
suggested that ran in the early hours of the day, although before it ran it
created a time_stamp_file with touch(1) set to be 6 hours previous so the
script let anything under 6 hours survive using a negation on the -newer
time_stamp_file clause.
Clem
On Wed, Jun 5, 2019 at 8:51 AM <arnold@skeeve.com> wrote:
> Edouard Klein <edouardklein@gmail.com> wrote:
>
> > Hi all,
> >
> > I saw this on https://old.reddit.com/r/unix :
> >
> > http://blog.snailtext.com/posts/no-itch-to-scratch.html
> >
> > It's about (the lack of) scratch files in csh. Maybe somebody here know
> > what happened to the feature ?
> >
> > Cheers,
> >
> > Edouard.
>
> From the phraseology in the paper ("The system will remove ....") it sounds
> to me like it was not a csh feature at all, but rather that the UCB
> systems had a cron job to run something like
>
> find / -name '#*' -mtime +7 -exec rm {} \;
>
> It's easy enough to research this in the archives, if you have the energy.
> :-)
>
> HTH,
>
> Arnold
>
[-- Attachment #2: Type: text/html, Size: 3352 bytes --]
next prev parent reply other threads:[~2019-06-05 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 12:38 Edouard Klein
2019-06-05 12:50 ` arnold
2019-06-05 13:05 ` Thomas Paulsen
2019-06-05 13:31 ` Clem Cole [this message]
2019-06-05 13:34 ` Clem Cole
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=CAC20D2NoBXgKw5DRPjmOV4rXX5M_dx4oUzUCE32Wur46HUmc_A@mail.gmail.com \
--to=clemc@ccc.com \
--cc=arnold@skeeve.com \
--cc=tuhs@tuhs.org \
/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).