From: Dave Lee <davel@canuck.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Linux 1.0 released
Date: Sun, 31 Mar 2002 22:31:35 -0700 [thread overview]
Message-ID: <Pine.SGI.4.21.0203312218080.14976718-100000@the-gimp> (raw)
In-Reply-To: <1017616746.6158.29.camel@inventor.gentoo.org>
Daniel Robbins wrote:
> New kernel:
> "2.4.19": 2.4.19-pre2-ac4-XFS
> Includes up-to-the-minute XFS support,
> O(1) scheduler,
> Rik van Riel's reverse-mapping patch,
> Andre Hedrick's IDE updates,
> Andrew Morton's disk IO fixes,
> and the usual Alan Cox goodness
can anybody tell me about the new "Library routines" section of the kernel
config. It has (undocumented, at least thru menuconfig) options for zlib
compression and decompression. First, what do these options do for the
kernel, and second, is the zlib library that the kernel uses up-to-date
with regards to the recent zlib vulnarabiliy? The kernel.org CHANGELOG
says the zlib bug was fixed in -pre4.
Any info on this is much appreciated, thx. Should I post this on the
gentoo-user ML?
Dave
parent reply other threads:[~2002-04-01 5:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1017616746.6158.29.camel@inventor.gentoo.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SGI.4.21.0203312218080.14976718-100000@the-gimp \
--to=davel@canuck.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox