From: Niall Parker <niall@ve7hex.ampr.org>
To: linux-hams@vger.kernel.org
Subject: Re: ancient history ...
Date: Thu, 08 Jul 2004 09:47:57 -0700 [thread overview]
Message-ID: <40ED7ABD.4010103@ve7hex.ampr.org> (raw)
In-Reply-To: <001a01c464dc$01673420$b1123c0a@magic875>
Willy & Linda Peake wrote:
> ---- Original Message -----
> From: "Niall Parker" <niall@ve7hex.ampr.org>
> To: <linux-hams@vger.kernel.org>
> Sent: Thursday, July 08, 2004 6:53 AM
> Subject: ancient history ...
>
>
>
>>Hello,
>>
>>I'm trying to get an old machine I had running years ago back online and
>
> I'm
>
>>running into problems, maybe someone here with a good memory can help me.
>>
>>The system is running kernel 2.0.37 with ax.25 compiled in (no modules)
>
> and
>
>>using the ax25-utils-2.0.12. I've managed to get the system running and
>
> hearing
>
>>traffic but when I try to connect using call I get
>>
>>---
>>
>>[niall@ve7hexgw /tmp]$ call lsp spr
>>GW4PTS AX.25 Connect v1.11
>>*** Connected to spr
>>Error opening terminal: xterm.
>>[niall@ve7hexgw /tmp]$
>>
>
>
> Looks to me like it couldn't open an x-terminal session at either at your
> box or at spr..
From what I recall of using it before, call was a completely command line app
that didn't do anything fancy with X ... just as I am typing though I'm
wondering if it may be a terminal type issue ... after some more experimentation
I find I can get it to fail similarly with TERM=xterm or vt100 or linux (ie the
"xterm" in the error line above is actually the variable TERM in the shell)
More fiddling ... or perhaps I should update everything a bit ... has anyone
recommendations for minimal boot/rescue distributions using more modern kernels
? (the system above was based on a cramdisk image)
... Niall
next prev parent reply other threads:[~2004-07-08 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 6:53 ancient history Niall Parker
[not found] ` <001a01c464dc$01673420$b1123c0a@magic875>
2004-07-08 16:47 ` Niall Parker [this message]
2004-07-09 11:24 ` Arno Verhoeven
2004-07-09 18:34 ` Niall Parker
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=40ED7ABD.4010103@ve7hex.ampr.org \
--to=niall@ve7hex.ampr.org \
--cc=linux-hams@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.