[5678] in Release_7.7_team
Can we shut down the cdrecord locker?
daemon@ATHENA.MIT.EDU (William Cattey)
Wed Jan 3 16:25:06 2007
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4123C75A-9A62-4822-8374-9B5D7DD58263@mit.edu>
Cc: Camilla R Fox <cfox@mit.edu>
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@MIT.EDU>
Date: Wed, 3 Jan 2007 16:24:59 -0500
To: release-team@mit.edu
X-Spam-Flag: NO
X-Spam-Score: 0.00
The cdrecord locker has not been updated since 2001. It has been
superseded by other tools that are better documented and better loved.
I have done an extensive review of the cdrecord locker, and confirmed
with Camilla Fox who was the last maintainer of the locker that it is
in fact moribund.
Camilla suggested setting the cdrecord acl unreadable and deleting
the locker 6 months later if nobody complains. Apparently that's the
process alexp uses for moribund lockers.
Then it's just a matter of making sure the Consultants and other
front line helpers know how to handle any inquiries about the
cdrecord locker:
Tell the customer that cdrecord pre-installed is canon now.
Find out where the customer was told use cdrecord and correct the docs.
QUESTION:
Can I set the cdrecord locker to be read-disabled, and email cfyi
that this has been done?
Does anyone see any reason NOT to do this, or any additional work
that should be done?
-wdc
----
William Cattey
Linux Platform Coordinator
MIT Information Services & Technology
W92-157, 617-253-0140, wdc@mit.edu
http://web.mit.edu/wdc/www/
