public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Harry Kalogirou <harkal@gmx.net>
To: jb1@btstream.com
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: bug in (linux) slattach
Date: 26 Sep 2002 12:31:08 +0300	[thread overview]
Message-ID: <1033032591.2787.47.camel@cool> (raw)
In-Reply-To: <Pine.LNX.4.33.0209260125350.32735-200000@olympus.btstream.com>

Την Πεμ, 26-09-2002 στις 11:49, ο/η jb1@btstream.com έγραψε:
> If you can't ping ELKS from Linux *AT ALL*, it may be a bug in your Linux
> installation rather than in ELKS; slattach 1.21 (1999-11-21), which comes
> in net-tools 1.56, doesn't seem to set the serial port speed (at least
> under Red Hat 7.0). It seems to be necessary to issue the appropriate stty
> command *before* the slattach command. Apparently slattach won't *set* the
> speed, but does *lock* it! I've attached a script that seems to work.
> 
> There's still a problem in ELKS: it responds to each ping, but with a 
> "CHECKSUM ERROR", and telnet, ftp, etc. don't connect.
> 

Hi!
 The "CHECKSUM ERROR" problem is something of a mystery. I stumpled on
it when I tried to connect ELKS to a REDHAT 6.x. The weird thing is that
everything else worked fine... telnet, ftp, http...

 This CHECKSUM ERROR doen't show up on debian machines...


Harry



-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2002-09-26  9:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26  8:49 bug in (linux) slattach jb1
2002-09-26  9:31 ` Harry Kalogirou [this message]
2002-09-26  9:33 ` Harry Kalogirou
2002-09-26 16:37 ` gabucino
2002-09-27 11:06   ` jb1
     [not found] <1034621946.3293.92.camel@cool>
2002-10-15 10:13 ` jb1

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=1033032591.2787.47.camel@cool \
    --to=harkal@gmx.net \
    --cc=jb1@btstream.com \
    --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