[1737] in Release_7.7_team

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

more patches

daemon@ATHENA.MIT.EDU (Michal N Lusztig)
Wed Mar 31 14:23:43 1999

To: release-team@MIT.EDU
Date: Wed, 31 Mar 1999 14:23:25 EST
From: Michal N Lusztig <miki@MIT.EDU>

   We should be talking in the release team meeting about an optimal time to add
more patches to 8.3, before is out of the alpha.

------- Forwarded Message

Received: from SOUTH-STATION-ANNEX.MIT.EDU by po9.MIT.EDU (5.61/4.7) id AA21442; Wed, 24 Mar 99 12:09:53 EST
Received: from ANTHARIA.MIT.EDU by MIT.EDU with SMTP
	id AA11330; Wed, 24 Mar 99 12:09:42 EST
Received: by antharia.MIT.EDU (8.9.3/) id RAA12086; Wed, 24 Mar 1999 17:09:49 GMT
Date: Wed, 24 Mar 1999 17:09:49 GMT
Message-Id: <199903241709.RAA12086@antharia.MIT.EDU>
From: Dan Winship <danw@MIT.EDU>
To: release-team@MIT.EDU, ops@MIT.EDU, athena-y2k@MIT.EDU
Subject: two new solaris y2k patches

The latest Solaris libc patch (which we do not have) has a new y2k fix
(for "posixgetdst"). There's also a new patch for "at" (trying to
schedule a job to run on 2/29/2000 schedules it for 3/1/2000 instead).

Unfortunately, there's absolutely no indication in the bug report
about the posixgetdst bug about how much of an effect this has on
anything.

I suppose we'll want to grab the latest patches again before putting
8.3 out, but this does bring up some issues for people who were
thinking 8.2 was Y2K-compliant already. There's also the possibility
that Sun (or SGI, or Transarc, etc) will discover further problems
even later in the game.

- -- Dan

------- End of Forwarded Message


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