[1973] in SIPB_Linux_Development
Re: update.pl
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Thu Jan 8 17:13:44 1998
Date: Thu, 8 Jan 1998 17:13:14 -0500
To: sit@MIT.EDU
Cc: linux-dev@MIT.EDU
In-Reply-To: <199801071616.LAA29526@harlie.mit.edu> (message from Emil Sit on
Wed, 07 Jan 1998 11:16:14 EST)
From: Salvatore Valente <svalente@MIT.EDU>
Emit wrote:
A friend was asking about it and since we didn't have one, I copied
the 4.0.0 update.pl script into the 4.2 updates directory and changed
the configuration lines at the top so that things should work.
Thanks, I guess. There are a few reasons why I've been reluctant to
copy the update.pl script to the 4.2 directory:
- Now, if people with 4.0 machines try to run the script through the
"current" symlink, they'll get the 4.2 update script, which may be
worse than getting no script at all. The script should make sure it's
running on a 4.2 system before doing anything.
Then again, maybe it won't be bad at all to run it on a 4.0 system.
Maybe it will completely ignore the 4.2 Athena RPMs and be careful
about upgrading the RedHat RPMs.
- The 4.2 updates directory contains kernel 2.0.32. (RedHat 4.2
originally came with 2.0.30, although new installs from small-gods
will get 2.0.32.) It may not be a good idea for the update script to
install a new kernel. Then again, maybe that will work too.
- The RemoveHacks() and AddHacks() stuff may or may not be necessary
with 4.2. We should make sure the script performs the correct hacks
for 4.2.
Someone with more time may want to make sure that the script deals
correctly with the 4.2 packages instead of the 4.0 packages.
Yup. We should do that.
Have a nice day,
Sal.
