From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-hams@vger.kernel.org
Subject: Re: callsign limit
Date: Wed, 31 May 2006 19:37:16 +1000 [thread overview]
Message-ID: <20060531093716.GA21395@cloud.net.au> (raw)
In-Reply-To: <200605310927.56706.vk3heg@iinet.net.au>
On Wed, May 31, 2006 at 09:27:56AM +0000, stephen wrote:
> When I enter in vk3fdcs at the bbs prompt I get this error:
>
> VK3HEG BBS>eu vk3fdcs
> *** Error : The callsign is missing.
>
> The windows remote linux program will let me add the vk3fdcs callsign, but
> when listing the users the ending 's' is cut off/missing.
>
> Is it posable to set call sign lengths in fbb or is this going to require a
> re-compile/editing of the source code?
Good question. AX.25 callsigns are at most 6 characters long, so you
won't be able to use those callsigns on the air.
Foundation licensees aren't allowed on packet btw.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2006-05-31 9:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 9:27 callsign limit stephen
2006-05-31 9:37 ` Hamish Moffatt [this message]
2006-05-31 11:03 ` Chuck Hast
2006-05-31 11:19 ` Hamish Moffatt
2006-06-01 1:40 ` Ralf Baechle DL5RB
2006-06-01 12:04 ` David D. Hagood
2006-06-01 13:25 ` Ralf Baechle DL5RB
2006-06-01 14:31 ` Curt, WE7U
2006-06-01 15:08 ` Ralf Baechle DL5RB
2006-06-01 15:15 ` Curt, WE7U
2006-06-01 18:52 ` Ralf Baechle DL5RB
2006-06-01 19:33 ` Thomas Sailer
2006-06-02 2:51 ` Kevin Dawson
2006-06-02 3:47 ` Hamish Moffatt
2006-05-31 13:05 ` Geoff Blake
2006-06-01 10:34 ` stephen
2006-06-01 10:54 ` Chuck Hast
2006-06-01 13:47 ` Hamish Moffatt
2006-06-01 14:00 ` Geoff Blake
2006-05-31 13:02 ` Matti Aarnio
2006-05-31 13:12 ` Thomas Sailer
2006-05-31 14:02 ` Matti Aarnio
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 12:12 IT3 Stuart Blake Tener
2006-05-31 12:41 ` Chuck Hast
2006-05-31 13:15 ` Robert Steinhäußer
2006-05-31 14:57 ` Bob Nielsen
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=20060531093716.GA21395@cloud.net.au \
--to=hamish@cloud.net.au \
--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