From owner-freebsd-hackers  Tue Sep 22 16:25:42 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA27203
          for freebsd-hackers-outgoing; Tue, 22 Sep 1998 16:25:42 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27192
          for <hackers@freebsd.org>; Tue, 22 Sep 1998 16:25:26 -0700 (PDT)
          (envelope-from ziggy@wopr.inetu.net)
Received: from localhost (ziggy@localhost)
	by wopr.inetu.net (8.8.8/8.8.5) with SMTP id TAA22088
	for <hackers@freebsd.org>; Tue, 22 Sep 1998 19:22:19 -0400 (EDT)
Date: Tue, 22 Sep 1998 19:22:19 -0400 (EDT)
From: Ryan Ziegler <ziggy@wopr.inetu.net>
To: hackers@FreeBSD.ORG
Subject: ufs_access behavior
Message-ID: <Pine.BSF.3.95q.980922191112.21915A-100000@wopr.inetu.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I am currently writing a kernel modification which allows the superuser
to configure a user to have access to other users' files. I modify, among
other things, ufs_access() in ufs/ufs/ufs_vnops.c, and am trying to decide
on the proper behavior of the function. Is there a reason for a user to
not always have read/write access to his files (perm 000), as root does
(for any file)?

-Ryan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message