From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 211bsd kermit working
Date: Sun, 9 Aug 2020 17:12:34 -0400 [thread overview]
Message-ID: <CAC20D2N7yMsct+LT5rfR0mroSCj6YMFSzo5Lu4joFzhC2kdWVQ@mail.gmail.com> (raw)
In-Reply-To: <40bd6da0-b83d-7963-1bc6-ab562bbde287@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
try this: adb /usr/new/kermit
Then run it and let it crash. You'll get an adb prompt, look at the stack
and see what system call number was pushed.
I suspect it a versioning issue that Warner has been discussing as 2.X
changed over time.
That said, it might just be easier to try to recompile c-kermit.
Clem
On Sun, Aug 9, 2020 at 5:06 PM Will Senn <will.senn@gmail.com> wrote:
> I'm running 211bsd pl 431 in SimH on FreeBSD. I've got networking working
> on a tap interface both inbound and outbound. I still have a few issues
> hanging around that are bugging me, but I'll eventually get to them. One
> that is of concern at the moment is kermit. It is in the system under
> /usr/new/kermit. When I call it, I get:
>
> kermit
> Bad system call - core dumped
>
> I don't see core anywhere and if I did, I'd need to figure out what to do
> with it anyway (mabye adb), but I'm wondering if anyone's used kermit
> successfully who is on pl 431 or knows what's going on?
>
> Thanks,
>
> Will
>
> --
> GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
>
>
[-- Attachment #2: Type: text/html, Size: 2319 bytes --]
next prev parent reply other threads:[~2020-08-09 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 21:05 Will Senn
2020-08-09 21:12 ` Clem Cole [this message]
2020-08-09 21:31 ` Will Senn
2020-08-10 0:53 ` Dave Horsfall
2020-08-10 1:42 ` Will Senn
2020-08-09 23:21 ` Warner Losh
2020-08-10 13:12 Noel Chiappa
2020-08-10 13:24 ` Will Senn
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=CAC20D2N7yMsct+LT5rfR0mroSCj6YMFSzo5Lu4joFzhC2kdWVQ@mail.gmail.com \
--to=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).