From: madcrow.maxwell@gmail.com (Michael Kerpan)
Subject: [Unix-jun72] File ownerships
Date: Tue, 6 May 2008 13:19:47 -0400 [thread overview]
Message-ID: <8dd2d95c0805061019oe7bd924v22ba96f75e981f85@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.64.0805060712070.20114@malasada.lava.net>
Speaking of assigning some file ownerships to people who were
historcially involved in created Unix back at that point in time, have
we let any of them know about our successful ressurection? Maybe could
get ken or dmr to write a "preface" to the readme file that will
inevitably come into existance once we make together a "turnkey"
distro of this for folks to play with in SIMH or something?
On Tue, May 6, 2008 at 1:13 PM, Tim Newsham <newsham at lava.net> wrote:
> > Now, I know that ken worked on the Fortran compiler, Joe Ossanna (jfo)
> > wrote roff, and in V6 & V7, ken had uid 6 and dmr had uid 7. So I
> > propose the following:
> >
> > - add ken == 6, dmr == 7, jfo == 4 to /etc/passwd and /etc/uids, as
> > new files in fs/new. Thus jfo will own /bin/roff and ken will own
> > /bin/cal
> > - modify the permissions file so that the Fortran files which are
> > uid 28 become uid 6 == ken.
> >
> > Sound reasonable?
>
> I don't mind some files being left "unowned", but if you're fairly
> sure that the new ownership assignments reflected reality I'm not
> opposed to having them changed in our patched system.
>
> > Warren
>
> Tim Newsham
> http://www.thenewsh.com/~newsham/
>
>
> _______________________________________________
> Unix-jun72 mailing list
> Unix-jun72 at tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/unix-jun72
>
next prev parent reply other threads:[~2008-05-06 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 9:59 Warren Toomey
2008-05-06 17:13 ` Tim Newsham
2008-05-06 17:19 ` Michael Kerpan [this message]
2008-05-06 22:37 ` Warren Toomey
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=8dd2d95c0805061019oe7bd924v22ba96f75e981f85@mail.gmail.com \
--to=madcrow.maxwell@gmail.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).