We are running Slack v10.2, and I am satisfied with this version
but try to keep it up-to-date by applying security ugrades from the
/patch/ directory. There is an upgrade to glibc in that directory
that is not mentioned in the security advisories. Please tell me
if there is any compelling reason 'to' or 'not to' upgrade glibc.

Thank You
swede


----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

On Sat, 23 Dec 2006 10:57:19 -0700, swede <not_my_sig@4email.adr> wrote:

....
>/patch/ directory. There is an upgrade to glibc in that directory
>that is not mentioned in the security advisories. Please tell me
>if there is any compelling reason 'to' or 'not to' upgrade glibc.

In order to run the latest 2.4 series kernels, for example 2.4.33.6,
you need the patched glibc in slack-10.2.

Grant.
--
http://bugsplatter.mine.nu/

On 2006-12-23, Grant <g_r_a_n_t_@dodo.com.au> wrote:
> On Sat, 23 Dec 2006 10:57:19 -0700, swede <not_my_sig@4email.adr> wrote:
>
> ...
>>/patch/ directory. There is an upgrade to glibc in that directory
>>that is not mentioned in the security advisories. Please tell me
>>if there is any compelling reason 'to' or 'not to' upgrade glibc.
>
> In order to run the latest 2.4 series kernels, for example 2.4.33.6,
> you need the patched glibc in slack-10.2.
>

2.4.31 seems to be working fine, so I don't guess there is any need to
fix it.

Thanks,
swede


----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

On Sun, 24 Dec 2006 08:16:36 -0700, swede
<not_my_sig@4email.adr> appears to have said:

> On 2006-12-23, Grant <g_r_a_n_t_@dodo.com.au> wrote:
>>
>> In order to run the latest 2.4 series kernels, for example 2.4.33.6,
>> you need the patched glibc in slack-10.2.
>>
>
> 2.4.31 seems to be working fine, so I don't guess there is any need to
> fix it.
>

2.4.31 doesn't have the "problem" that propmted the upgrade. The
ChangeLog says:


patches/packages/glibc-2.3.5-i486-6_slack10.2.tgz:
Patched an issue with kernel version parsing in ld-2.3.5.so that was
leading glibc to treat 2.4 kernels with 4 version parts (such as
2.4.33.1) as if they supported NPTL, leading to a crash at boot.


So, for instance, the kernel I compiled last night (2.4.33.7) would be
affected. There's actually no real need to upgrade glibc, though. You
only need edit the Makefile for the "four part" kernels. Instead of:

EXTRAVERSION = .7

Do:

EXTRAVERSION = -7

Now the kernel is version "2.4.33-7" instead of "2.4.33.7" and
the "problem" goes away.

HTH,
Jonathan

--
Don't just hit reply. Email address is broken. Thank
your friendly neighborhood spammer. Email replies to:
user: daboid domain: suddenlink<dot>net