[6206] in SIPB bug reports
Re: sipb-nonmem and prospectives with write bits on install volumes in sipb locker
daemon@ATHENA.MIT.EDU (chad brown)
Thu Oct 31 15:07:53 1996
To: "Jacob Morzinski" <jmorzins@MIT.EDU>
Cc: Sam Hartman <hartmans@MIT.EDU>, Salvatore Valente <svalente@MIT.EDU>,
bug-sipb@MIT.EDU, sipb-afsreq@MIT.EDU
In-Reply-To: Your message of "Wed, 30 Oct 1996 14:31:12 EST."
<9610301931.AA02945@m37-332-3.MIT.EDU>
Date: Thu, 31 Oct 1996 15:07:17 EST
From: chad brown <yandros@MIT.EDU>
Jacob points out that the permissions on sipb-new aren't correct for
sipb-nonmem to work the way it was intended. This was an error on my
part. I believe that I've fixed all of these mistakes. I have given
system:gssipbbin all access to all of the volumes and also (for now)
removed sipb-nonmem's permissions to the arch/*/bin directories.
There are still some directories (existing source and build
diorectorieS) that sipb-nonmem doesn't have write access to; ask the
person who created those if you want access.
Now that I've removed sipb-nonmem's access tothe bin directories, I'll
ask two things:
1) Sal, please restore the write access if it's decided that we want to
do that.
2) sipb-afsreq: can anyone help me change the name of the group from
sipb-nonmem to sipb:nonmem? I tried what I believe were the
approriate steps, and it didn't work. I ask for some assistance on
class sipb, but none of the suggestions helped.
thanks,
chad
