[2022] in SIPB_Linux_Development
How about a new RH-A release for next year?
daemon@ATHENA.MIT.EDU (Emil Sit)
Sun May 31 14:22:37 1998
To: linux-dev@MIT.EDU
Date: Sun, 31 May 1998 14:23:03 EDT
From: Emil Sit <sit@MIT.EDU>
It's summer time. We have lots of free time. (Right.) Do we want
to do a new release of RedHat-Athena for next fall? (Say, with an
intended release in August? :) If so, we ought to start work soon
and probably basing stuff on the newly released RH5.1. But, lots
of stuff has changed since 4.2. Offhand, they've changed:
* Libc. This will probably break loads of things... anyone have any
idea how bad that will be? I haven't touched glibc at all.
* Installation stuff --- kickstart? disk druid? probably not too much
of Derek's stuff will be applicable. I'm interested in looking
at this part of stuff this year.
* Configuration --- linuxconf. Anyone play with this? Could we extend
it to support rc.conf type stuff?
Other things I can think of that needs to be looked at:
* How much of the SIPB-Athena source tree builds on RH5.1 cleanly?
* How out of sync is that source from Athena-8.2? What 8.2 changes do
we want to integrate? (looking at /afs/dev/project/relnotes/rel82.tex)
- ssh? though i seem to recall danw saying that wasn't going to happen.
- krb5. login, r* stuff, keytab/srvtab change
- change from nocreate/noremote to /etc/athena/access.
- perhaps related to all that, libAL?
- new attach
- sendmail cf changes
- code updates: discuss, zephyr, ...
* Other new stuff or old stuff that we didn't quite pull in for 4.2...
- libAL + PAM?
- Disconnected support? (I don't know how well the improved
support jmmikkel and fastcart (I think?) were working on works...)
It seems that linuxconf has some sort of askrunlevel thing
at boot up which may make this nicer.
- auto-updates?
* Fixing AFS cache corruption? (Or just nuke afs cache on boot?)
I don't suppose 2.0.34 might fix it. (Oh. And presumably RH will
release appropriate new kernel rpms when 2.0.34 is actually
released so we have users running a release kernel and not
2.0.34pre6 or something.)
Anything else? Seems like a lot of work to get done for two months
given the pace we normally move at. Why don't we start out seeing
who's around and what stuff people might be interested in working on.
Comments on this mail would be a good start. I'll mention something
at the meeting tomorrow night too.
--
Emil Sit / Bronx Science '95, MIT '99 -- ESG, SIPB, Athena Consulting
PGP KeyID: 0xE63561E9 / Fingerprint: A68FD0693EDABA19 2671EC1F22498F58
