From: Paulo Schreiner <paulo@bewnet.com.br>
To: J Sloan <jjs@lexus.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
tux-list <tux-list@redhat.com>
Subject: Re: TUX 2
Date: Thu, 13 Dec 2001 17:48:56 -0200 [thread overview]
Message-ID: <3C190628.7010802@bewnet.com.br> (raw)
In-Reply-To: <1008246475.874.11.camel@gandalf> <3C18F50D.2D3452F@lexus.com> <3C18FD45.1000508@bewnet.com.br> <3C1903FB.80E880A5@lexus.com>
Hey, i managed to isolate the problem. It's a conflict with the PPP
Deflate option.
I don't think that (from what I read from the help) that this option is
so importanto, but notheless, i think this is a bug with the TUX's
patches. My guess is that just changing the struct names that conflict
would solve the problem. I might even try to do it myself if no one else
does until the weekend.
Thanks for the help,
Paulo S.
J Sloan wrote:
>Paulo Schreiner wrote:
>
>>Well, well, just managed to reproduce the error here in my mandrake system.
>>
>
>Well, I attach my config for your enjoyment -
>
>At first glance, the only thing that strikes
>me about your config is that you don't
>like modules, and it also seems to be a
>laptop config -
>
>BTW not compiling tux as a module
>must suck - instead of stopping tux
>and unloading the module, you must
>reboot as with a windoze pee cee, if
>major config changes are made -
>
>BTW I'm using Red Hat 7.1 & 7.2, gcc-2.96 -
>
>(Please oblige the following sanity check)
>
>After applying patches, be sure there are
>no rejects - and then after saving your config,
>do a "make mrproper", then after restoring
>your .config, do a "make oldconfig", then do
>the normal compile steps -
>
>cu
>
>jjs
>
next prev parent reply other threads:[~2001-12-13 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 12:27 TUX 2 Paulo Schreiner
2001-12-13 18:35 ` J Sloan
[not found] ` <3C18FD45.1000508@bewnet.com.br>
2001-12-13 19:39 ` J Sloan
2001-12-13 19:48 ` Paulo Schreiner [this message]
2001-12-14 14:25 ` Ingo Molnar
2001-12-14 14:30 ` [-D5] " Ingo Molnar
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=3C190628.7010802@bewnet.com.br \
--to=paulo@bewnet.com.br \
--cc=jjs@lexus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tux-list@redhat.com \
/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.