From: Stuart Longland <stuartl@longlandclan.yi.org>
To: linux-hams@vger.kernel.org
Subject: Re: Packet BBSes on ax25d
Date: Mon, 24 Mar 2014 21:27:28 +1000 [thread overview]
Message-ID: <0eh50b-t7c.ln1@atomos.longlandclan.yi.org> (raw)
In-Reply-To: 532EB3C2.5090803@exemail.com.au
On Sun, 23 Mar 2014 21:13:22 +1100, Ray Wells wrote:
>> I was looking for some too, but couldn't find any and couldn't even
>> get the old software working well enough to try and characterise how
>> it worked.
>>
>> Maybe it's time to start from scratch. What should a packet BBS do?
>
> The xfbb mailing list is still active and might be a good place to ask
> questions. The maintainer of xfbb is Bernard, F6BVP, who frequents this
> list, but many xfbb users do not.
Interesting, I've tried again but last time I submitted my email address
via their subscribe form (Mailman) nothing arrived.
I've tried again, maybe this time it'll work.
> Reflecting back to when I ran xfbb the only configuration for ax25d was
> for Netrom calls to connect to fpacnode. xfbb did it's own listening
> for ax25 traffic via kernel ax25 ports.
That's what I figured, but could never get to work. I could at best get
it to answer, but then typing commands did absolutely nothing.
xfbbC -c, as per the instructions, just did a poor emulation of /bin/cat,
and I couldn't figure out how to kill it. Telnet would talk to me: it'd
tell me my callsign wasn't registered.
(Not registered with whom I wonder, did it check the ACMA or its own
password file?)
next prev parent reply other threads:[~2014-03-24 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 8:02 Packet BBSes on ax25d Stuart Longland VK4MSL
2014-03-23 8:08 ` Gordon JC Pearce
2014-03-23 10:13 ` Ray Wells
2014-03-24 11:27 ` Stuart Longland [this message]
2014-03-23 12:40 ` Brian
2014-03-24 11:29 ` Stuart Longland
2014-03-24 12:54 ` Brian
2014-03-23 18:00 ` David Ranch
2014-03-24 11:35 ` Stuart Longland
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=0eh50b-t7c.ln1@atomos.longlandclan.yi.org \
--to=stuartl@longlandclan.yi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox