From: James Cameron <james.cameron@hp.com>
To: linux-ppp@vger.kernel.org
Subject: Re: 2.4.2 on AMD64 Linux: assumes 4-byte long - FIXED!
Date: Thu, 10 Jun 2004 04:43:46 +0000 [thread overview]
Message-ID: <20040610044346.GK17654@hp.com> (raw)
In-Reply-To: <20040606021936.14c69b54@localhost>
Guy,
Yes, Mandrake's kernel source includes MPPE support, and the kernel.org
sources do not. Other distributions also add MPPE support in this way;
Debian and SUSE included. Red Hat do not.
I know Debian get their kernel-patch-mppe package from PPP CVS. I
suspect Mandrake and SUSE did as well. You should check that the
sources match what is in PPP CVS. To get PPP CVS onto your system,
cd /usr/src # (or some other reasonable directory)
cvs -d :pserver:cvs@pserver.samba.org:/cvsroot co ppp/linux/mppe
If you've made changes to drivers/net/sha1.{c,h} and Mandrake got these
from Frank Cusack's work that is in PPP CVS (directory linux/mppe), then
you could post them here or to Frank.
Matt Domsch, Jan Dubiec, and some others have also been working on the
MPPE patch; they have posted to the PPTP mailing lists.
If you logged a bug report with Mandrake, one would hope that they would
elevate this report back to Frank. ;-) There is a risk that they will
adjust their patch instead.
--
James Cameron http://quozl.netrek.org/
HP Open Source, Volunteer http://opensource.hp.com/
PPTP Client Project, Release Engineer http://pptpclient.sourceforge.net/
next prev parent reply other threads:[~2004-06-10 4:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 6:19 2.4.2 on AMD64 Linux: assumes 4-byte long Guy Rouillier
2004-06-09 5:48 ` 2.4.2 on AMD64 Linux: assumes 4-byte long - FIXED! Guy Rouillier
2004-06-10 4:13 ` Guy Rouillier
2004-06-10 4:43 ` James Cameron [this message]
2004-06-10 5:52 ` Guy Rouillier
2004-06-11 8:12 ` mole
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=20040610044346.GK17654@hp.com \
--to=james.cameron@hp.com \
--cc=linux-ppp@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.