From: newsham@lava.net (Tim Newsham)
Subject: [Unix-jun72] File ownerships
Date: Tue, 6 May 2008 07:13:21 -1000 (HST) [thread overview]
Message-ID: <Pine.BSI.4.64.0805060712070.20114@malasada.lava.net> (raw)
In-Reply-To: <20080506095920.GA36926@minnie.tuhs.org>
> 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/
next prev parent reply other threads:[~2008-05-06 17:13 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 [this message]
2008-05-06 17:19 ` Michael Kerpan
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=Pine.BSI.4.64.0805060712070.20114@malasada.lava.net \
--to=newsham@lava.net \
/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).