[6283] in Release_7.7_team
Re: Bringing bashrc and cshrc into sync
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Fri Mar 13 08:29:53 2009
Cc: debathena@mit.edu, release-team@mit.edu
Message-Id: <E21B8D46-F6B7-4FE5-A773-23C62663A5ED@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Tim Abbott <tabbott@mit.edu>
In-Reply-To: <alpine.DEB.1.10.0903121748270.22031@vinegar-pot.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: Fri, 13 Mar 2009 08:28:53 -0400
X-Spam-Flag: NO
X-Spam-Score: 0.00
On Mar 12, 2009, at 11:38 PM, Tim Abbott wrote:
> The main question I'm not sure about is this: How do we expect users
> who
> use both Debathena and Athena 9 machines during the transition
> interval to
> configure their dotfiles? Perhaps it's the case that since we're
> simply
> removing idempotent settings, if they want the setting back they can
> simply add them to their dotfiles and it'll work fine on both
> platforms,
> and have the right end result once Athena 9 stops existing...
The sample cshrc.mine and bashrc.mine files I drafted (/mit/jdreed/
debathena/*.mine) conditionalize on the result of "machtype -L | grep -
q debathena" setting $? to 0 or not. So users who use both should be
fine - Athena 9 will continue to work, and if they apply these
customizations, Debathena will emulate Athena 9. I documented each
line in cshrc.mine and bashrc.mine so that users know what they do,
and I included "tips" on how to change their dotfiles too.
I anticipate users either fixing their dotfiles to stop using Athena-
specific hacks, or incorporating the samples we provide, so either
way, they should get the same behavior on Athena 9 and Debathena.
I'll write up a draft of the web page I expect to reference in the
lert message...
-Jon
