by I am faced with the problem of installing Red hat 7.0 plus the
updates from the Red Hat update site. Attempting, logically,
to install the fixes in date order, I am faced with the
following problem:
When Red Hat updates a module for bug fixes or security more
than once, they go back to the older problem(s) for which
the module had to be updated for, and change the rpm involved
to the newest rpm for the module. This makes sense in that
you would not have to update the module twice. However, it
also results in dependency problems after many fixes have
occurred.
Example: The 2nd and 23rd problems required updating rpm
"larry". When you try to install larry-*.rpm and the other
rpms needed to fix problem #2, you find that larry-*.rpm
requires the new version of the "moe" rpm that was updated
for problem #17. When you try to add moe-*.rpm into the rpm
command, you find that moe fails because "shemp" isn't
installed. Try to install "shemp" and you find out it
multiply defines the routine "__eyepokeclient" along with the
installed version of the curly rpm. Curly was updated along
with to fix problem #12 (at which point larry and moe could
be installed without curly but now required shemp). And so
on...
Of course,the Red Hat Network will solve this problem for
you with up2date if you buy a subscription from them, but I
feel it should be possible to create a fully updated system
in some sort of systematic manner. Has anyone come up with
one that works without a payment or subscription service?
--
Norm (This message does not constitute an endor*t of the
news service which inserted the adverti*t below).