From: Eduardo Pereira Habkost <ehabkost@conectiva.com.br>
To: linux-8086@vger.kernel.org
Subject: Re: Vjhc patch
Date: Mon, 19 Jul 2004 16:01:18 -0300 [thread overview]
Message-ID: <20040719190118.GS2830@duckman.distro.conectiva> (raw)
In-Reply-To: <20040719185117.39661.qmail@web51309.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
Things would be easier if you just show which error is occurring on
your system. :)
On Mon, Jul 19, 2004 at 11:51:17AM -0700, Tommy McCabe wrote:
<snip>
>
> 1. What version of ELKS and BCC do you have?
elks from current CVS
bcc from dev86-0.16.16
> 2. Did you turn on SLIP header compression in the ELKS
> kernel config?
No. I can check using CONFIG_CSLIP=y later.
--
Eduardo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-19 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 23:51 Vjhc patch Tommy McCabe
2004-07-19 15:23 ` Eduardo Pereira Habkost
2004-07-19 17:53 ` Tommy McCabe
2004-07-19 18:06 ` Eduardo Pereira Habkost
2004-07-19 18:51 ` Tommy McCabe
2004-07-19 19:01 ` Eduardo Pereira Habkost [this message]
2004-07-19 20:57 ` Tommy McCabe
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=20040719190118.GS2830@duckman.distro.conectiva \
--to=ehabkost@conectiva.com.br \
--cc=linux-8086@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox