[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RedHat Enterprise Linux Errata
- To: luci-discuss@luci.org
- Subject: RedHat Enterprise Linux Errata
- From: Carlos Pintura <cpintura@gmail.com>
- Date: Fri, 18 Mar 2005 14:08:44 -0600
- DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ILO/cBBi0t12Bavd6dxeYZ2RHqUfDX55gipY8sAFOq8y6xWCaqSFcZF6f5nIA6Fjy2UZptEyHmK/0mbkhfk4SUyby16dLZAbNgBzaIy4j0vonEuPsKBVu0Ub0Z3nZJGJjI8VM8CL041GW7gUnuF0Z41cnxjqNlPMkYeuNhr0BJo=
- Organization: Linux Users of Central Illinois
- Reply-To: Carlos Pintura <cpintura@gmail.com>
- Sender: luci-discuss-owner@luci.org
Hello,
I know that RedHat at times chooses to patch their existing source
code for applications keeping the application revision level the same
and incrementing what I would call their internal/proprietary revision
number. I believe that a major flaw found in OpenSSH was handled this
way...
Getting to my specific scenario, I have a RHEL 3ES machine running the
latest RPMs available from RedHat for this OS, however Apache seems to
be at httpd-2.0.46-44 and php, at php-4.3.2-19. Looking on each
project's website, I see Apache is at 2.0.53 for stable and PHP
4.3.10.
Is there a method available on the Redhat website for understanding
whether or not their RPMs incorporate changes held in these seemingly
more recent releases?
Thank you
-
To unsubscribe, send email to majordomo@luci.org with
"unsubscribe luci-discuss" in the body.