The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: <ron@ronnatalie.com>
To: "'Angelo Papenhoff'" <aap@papnet.eu>, <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] /crp
Date: Tue, 6 Nov 2018 14:25:29 -0500	[thread overview]
Message-ID: <04db01d47606$7b003700$7100a500$@ronnatalie.com> (raw)
In-Reply-To: <20181106170955.GA4087@indra.papnet.eu>

An early UNIX paper shows the system had four RK05's (4872 512-byte blocks
on UNIX, for some reason only 4800 used on the DEC OSs ... remember we had
to poke ROLLIN to copy the full UNIX partition standalone).
/dev/rk0 - available for user packs.
/dev/rk1 - root
/dev/rk2 - /usr
/dev/rk3 - /crp

I think it was just additional storage of "crap".

> -----Original Message-----
> From: TUHS <tuhs-bounces@minnie.tuhs.org> On Behalf Of Angelo
> Papenhoff
> Sent: Tuesday, November 6, 2018 12:10 PM
> To: tuhs@minnie.tuhs.org
> Subject: [TUHS] /crp
> 
> I was wondering, what was the /crp mount point in early UNIX used for?
> And what does "crp" mean? Does it mean what I think it does?
> It is only mentioned in V3 it seems:
> ./v4man/manx/unspk.8:unspk lives in /crp/vs   (v4/manx means pre-v4)
> ./v3man/man6/yacc.6:SYNOPSIS /crp/scj/yacc  [ <grammar ]
> ./v3man/man4/rk.4:/dev/rk3      /crp file system
> 
> I suppose scj, doug or ken can help out.
> 
> aap


  parent reply	other threads:[~2018-11-06 21:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 17:09 Angelo Papenhoff
2018-11-06 19:22 ` ron
2018-11-06 19:25 ` ron [this message]
2018-11-06 21:51   ` Dave Horsfall
2018-11-07 12:18     ` ron
2018-11-07 15:14       ` Clem Cole
2018-11-07 23:40         ` Greg 'groggy' Lehey
2018-11-08  3:04           ` Warner Losh
2018-11-07 16:43     ` Paul Winalski
2018-11-08 16:55   ` Mary Ann Horton
2018-11-09  5:30     ` Lars Brinkhoff
2018-11-06 23:31 Norman Wilson
2018-11-07 15:08 ` Clem Cole
2018-11-07 23:30   ` Rob Pike

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='04db01d47606$7b003700$7100a500$@ronnatalie.com' \
    --to=ron@ronnatalie.com \
    --cc=aap@papnet.eu \
    --cc=tuhs@minnie.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).