[799] in Release_7.7_team
notes from 12/12
daemon@ATHENA.MIT.EDU (Mike Barker)
Tue Dec 17 10:56:50 1996
To: release-team@MIT.EDU
Cc: mbarker@MIT.EDU
Date: Tue, 17 Dec 1996 10:56:45 EST
From: Mike Barker <mbarker@MIT.EDU>
1. htmlview
we discussed the question of whether or not this change needs to
be publicized before it happens. Basically, people think it should
be, so Oliver and Kevin are going to change the OLH page to tell
people.
On Jan. 6, they would like the OLH script changed to use htmlview
The dash changes will be handled by dot.
2. changing the default prompt to include the path and other information
we tabled this to wait for Gary. If you have comments, please feel
free to discuss the matter on the list.
3. SGI upgrade difficulties
We already expected to have trouble this year due to O2 (the new
SGI hardware) and the expected dates for IRIX 6.3 (necessary for the
O2) and an AFS version to run with it.
We now have the added complication of Mark leaving. He may be
available for some consulting work, but we need to be aware that the
SGI is going to be lacking support this year.
4. Rumors of a January Patch Release?
There appear to be two sources for this. One is the fact that
there are kernel patches which may be helpful in getting the
kerberized NFS to work, and we may want to go ahead with that.
The other is that Miki would like to upgrade either solar or
solar2. Right now, the installer runs 2.3, with a miniroot of 2.3, to
install a client at 2.4. She would like to upgrade this so that the
installer, miniroot, and client are all at 2.4. This is partially in
preparation for going to 2.5 later this year.
Jonathon and Miki will continue offline.
5. Solaris 2.5.1 - Miki needs input regarding any patches which are
needed for third-party software.
6. The videocam problem on the SGIs has a workaround/fix which has
gone to cfyi and sipb. However, we are still seeing help exchanges
which just say that the SGI cameras don't work and recommend trying
another machine. We should (a) put the information about the fix in
the info locker and (b) publicize the fix through sipb?
