public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: paulus@samba.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: libz, libbz2, ramfs and cramfs
Date: Wed, 17 Oct 2001 20:25:41 -0700	[thread overview]
Message-ID: <3BCE4BB5.8060603@zytor.com> (raw)
In-Reply-To: <19978.1003206943@kao2.melbourne.sgi.com>	<3BCBE29D.CFEC1F05@alacritech.com>	<9qjfki$ob5$1@cesium.transmeta.com> <15310.18125.367838.562789@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:

> 
> PPP uses a variant of zlib with some extensions.  I believe that I
> didn't break zlib for normal use when I added the extensions but I
> would have to check that to be 100% sure.  The PPP zlib.c is based on
> zlib-1.0.4, which is no longer the most recent version.
> 


What kind of extensions?


> I think it would be possible to make PPP use the standard zlib but
> with decreased performance.  It's a long time since I looked at that
> stuff though.

 >

>>A major problem is that the module name "deflate" is used by PPP,
>>despite it being a nonstandard format...
>>
> 
> No, the module name is "ppp_deflate".
> 


Oh.  Well, then ...

	-hpa



  reply	other threads:[~2001-10-18  3:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-15 13:06 libz, libbz2, ramfs and cramfs Cristiano Paris
2001-10-15 22:53 ` H. Peter Anvin
2001-10-16  4:35 ` Keith Owens
2001-10-16  7:32   ` Matt D. Robinson
2001-10-17  8:31     ` H. Peter Anvin
2001-10-18  3:04       ` Paul Mackerras
2001-10-18  3:25         ` H. Peter Anvin [this message]
2001-10-18  7:15           ` Paul Mackerras
2001-10-18 12:15             ` Paul Mackerras
2001-10-18 17:33               ` H. Peter Anvin
2001-10-17  8:45     ` David Woodhouse
2001-10-16 17:36   ` David Woodhouse

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=3BCE4BB5.8060603@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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