[6219] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: Reminder: Release Team: 1:30 Tuesday 2/24 in W91-250

daemon@ATHENA.MIT.EDU (Jonathan Reed)
Mon Feb 23 19:32:35 2009

Cc: release-team@mit.edu
Message-Id: <97BD264C-1741-46DE-9FE6-101F4D0F7DA6@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: William Cattey <wdc@mit.edu>
In-Reply-To: <BBCD4013-E61E-4E33-94C0-FD1831826711@mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 23 Feb 2009 19:31:51 -0500
X-Spam-Flag: NO
X-Spam-Score: 0.00

I'll get this out of the way now:

> jdreed: Where are we in crafting the merged Athena apt repository
> write access guidelines? jdreed will ping for bullet points. tabbott
> will try and send some.

Blocking on bullet points.

> jdreed: What is status of switching default shell to bash?

Garry says letting him know by the 2nd week in April would be best.  I  
have set an internal deadline of bringing consultants up to speed and  
having stock answers ready by Tuesday, 3/31, in order to give Garry  
the greenlight no later than Friday 4/3.  I'm also inventorying the  
OLH docs to figure out what needs updating, and will coordinate those  
changes with Heather Anne.  Mail should go somewhere advertising the  
change once it actually goes live.  Presumably cfyi and sofa?

> ATN-30 trackerd may break AFS: Need to confirm or reject this.

I reported two workarounds for this.  Someone should test them before  
tomorrow's meeting so we can discuss in more detail.  I absolutely  
will not have time, as I'm already behind on getting the OLC answers  
finished in Hermes, and I really want to have a mock-up of the new  
debathena.mit.edu too.

The second workaround (creating the tracker.cfg file) is probably the  
best choice, since it will only change things for the affected users.   
Disabling trackerd (the first workaround) is fine on -cluster  
machines, but a poor choice on private workstations, since users might  
re-enable it anyway without understanding the implications.

It was unclear from the comment whether the issue can be avoided by  
tweaking afsd args, or if it required a patch. If we can tweak afsd  
args without any side effects, that's fine, but we really do not want  
to be building our own AFS.

-Jon

home help back first fref pref prev next nref lref last post