The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] Bell Labs history question
Date: Tue, 29 Aug 2017 08:29:44 -0600	[thread overview]
Message-ID: <201708291429.v7TETi5e022814@freefriends.org> (raw)
In-Reply-To: <833F5F46-9C8F-4A0C-9EB9-26127CCB31A9@cheswick.com>

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

Thanks!

Any idea what the group names would have been?

Arnold

William Cheswick <ches at cheswick.com> wrote:

> — coma
>
> I happen to have a tar file from coma, one of the main V10 machines I used.  
> A sample file has
>
> UID	115
> GID	20
>
> The tar file is dated April 29 1997
>
> The UID was doubtless “ches”.  
>
> — research
> I have another file from Oct 14, 1992, named ypsnarf.c,
> UID=2009, GUD-2009
>
> This file is probably from research (as in research!ches) and was a MIPS not running V10.
> This was probably ches,ches and not helpful.
>
> — bowell
>
> bowell was the master source machine for V10.  A file (proxy.c, Mar  3  1993) I had tarred up from there has
> UID:	1696
> GID:	4
>
>
> ches
>
>
> > On 29Aug 2017, at 9:07 AM, arnold at skeeve.com wrote:
> > 
> > Hi.
> > 
> > For a project I'm working on, I wonder if the Bell Labs alumni present
> > can tell me what was the default group for files for the researchers?
> > That is, what group did ls -l show?
> > 
> > In particular, in the late 90s - ~ V10 time frame.
> > 
> > Much thanks,
> > 
> > Arnold
>


  reply	other threads:[~2017-08-29 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 13:07 arnold
2017-08-29 14:13 ` William Cheswick
2017-08-29 14:29   ` arnold [this message]
2017-08-30 15:34 ` Ronald Natalie
2017-08-31  0:27   ` Dave Horsfall
2017-08-31  6:20     ` arnold

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=201708291429.v7TETi5e022814@freefriends.org \
    --to=arnold@skeeve.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).