Conference smurf::buildhelp

140.0. "re: bco for Henry_Pau" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Mon Jun 14 1993 15:10

Date Of Receipt: 	14-JUN-1993 14:17:33.02
From: 	WASTED::jmf "Joshua M. Friedman ULTRIX SDE  14-Jun-1993 1418"
To: 	henrypau@zk3.dec.com
CC: 	odehelp@wasted:zko.dec
Subj: 	re: bco for Henry_Pau

Henry, your principal entry does not give you automatic access to the source
control system.  You need to have your supervisor or manager send mail to
one of the project teams for OSF/1 development, and have them confirm to 
release engineering (reng@zk3.dec.com) that you should be in the access list
(specify base os or x11 pool).  The project leaders for the various streams
are all in the mail alias "jproj@zk3.dec.com". 

-josh

------- Forwarded Message

Return-Path: henrypau@zk3.dec.com
Received: by abyss.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
	id AA24916; Thu, 10 Jun 1993 12:01:40 -0400
Date: Thu, 10 Jun 1993 12:01:40 -0400
From: henrypau@zk3.dec.com (Henry Pau ISE/Hong Kong)
Message-Id: <9306101601.AA24916@abyss.zk3.dec.com>
To: odehelp@zk3.dec.com
Subject: bco fails

Hi,
  I did a "kinit", it works fine. I then do a "bco" in my sandbox which is
backed by a shared sandbox, it fails with "co: access denied by ACL".

  This is the first time I do a "bco" since I got my principal name, which is
"Henry_Pau". Anything I missed?

Thanks,
Henry

------- End of Forwarded Message