On 6/11/06, Lawrence 'The Dreamer' Chen <dreamer@xxxxxxxxxxxxxxx> wrote:
> >
As I mentioned, I left 4 RH73 machines at my last job....where they have nobody to support them now, so they just expect them to run forever (though for the short term, my manager could call me back in to help out...since I'm still living across the street from the office). Kind of cost prohibitive to buy some copies of RHEL ES to run on a bunch of lowly machines (a P-II 400, a P-III 450, a dual P-III 500, and a p-III 1.13G)...just because RedHat considers being an NIS server to not be a WS function (the company just uses RHEL WS machines
They can always get Centos-2.1 and use that for their configuration. Red Hat 7.3 hit 4 years old in May of 2006. Even so, Red Hat has put RHEL-2 into deep freeze mode itself. It gets security bug fixes but nothing else.. and the timeframe for those are long because there arent a lot of customers for them. [My guess is that most of the customers are RHN satellite customers.. who have been told to pretty please move to RHEL-4 with RHN-4.10 versus trying to keep the older versions going] Trying to back-port fixes for RHEL-2.1/RHL-7.3 is a very strenuous activity. In many cases, you have no upstream fix because the code has changed drastically that has any patch in it. You then have to spend your time: A) Confirming that the problem exists. B) If it exists, how is it triggered (ususally different from the public exploit) C) How much code fixing does it take to fix. The man-hours for this are the longest of any backport fixes and you are looking at a full-time job tracking and fixing these.. -- Stephen J Smoogen. CSIRT/Linux System Administrator -- fedora-legacy-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-legacy-list
