From: Chuck Hast <wchast@gmail.com>
To: Linux-hams List <linux-hams@vger.kernel.org>
Subject: FPAC Linux routing question
Date: Thu, 11 Nov 2004 20:32:34 -0800 [thread overview]
Message-ID: <620c905704111120322eb0c5dc@mail.gmail.com> (raw)
Do any of you on the list run FPAC Linux? I am trying to figure out how to
set up alternate routing, we are moving our DOS FPAC systems to Linux
but I have not been able to find a clear example of how to set up alternate
routing in the Linux version.
In the DOS version the line
Route to Nodes a4bcd a4efg
would cause the routing the first try to route down the first call, if it failed
it would try the second and any following, but I do not see how that is
set up under Linux FPAC.
--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."
reply other threads:[~2004-11-12 4:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=620c905704111120322eb0c5dc@mail.gmail.com \
--to=wchast@gmail.com \
--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.