[1039] in RedHat Linux List
Re: A different approach to RedHat updates
daemon@ATHENA.MIT.EDU (Eric Lee Green)
Fri Oct 25 21:59:23 1996
Date: Fri, 25 Oct 1996 20:56:22 GMT
To: redhat-list@redhat.com
From: Eric Lee Green <exec@prysm.net>
Reply-To: exec@prysm.net
In-reply-to: <199610251522.LAA17385@redhat.com>
(redhat-digest-request@redhat.com)
Resent-From: redhat-list@redhat.com
> RPM is to provide for gradual updates of a system. How feasible would
> it be for new rpms of packages to be released on a continual basis and
> new CD "snapshots" of the current packages released, say, quarterly?
It was not very feasible for RedHat 4.0 because so many of the changes had
to be installed in one big lump. The biggest "lumpishness" was caused by the
fact that the 2.0 kernel broke all the process management code, but there
was also a lot of "lumpishness" dealing with new features that came in with
2.0, like "kerneld".
My policy right now is to not install RedHat 4.0 on any of my client's
systems unless they expressly request it. 3.03 might have had its own
share of bugs, but they were not bugs that would affect my clients (who
generally run their machines in limited-access environments running a
couple of applications). By contrast, RedHat 4.0 won't even *PRINT* right
out of the box.
In perhaps a month, after the last of the major bugs are worked out, I'll
probably reverse this policy. Be a pain installing the upgrades after
installing the CD (40 megabytes worth, eh?), but there's too much good stuff
to overlook forever.
-- Eric Lee Green exec@prysm.net
Executive Consultants
--
PLEASE read the Red Hat FAQ, Tips, HOWTO and the MAILING LIST ARCHIVES!
________________________________________________________________________
http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-HOWTO
http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists
------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
