From: "Douglas Cole" <n7bfs@qwest.net>
To: linux-hams@vger.kernel.org
Subject: FBB for linux and internet forwarding
Date: Sun, 8 Dec 2002 09:32:03 -0800 [thread overview]
Message-ID: <200212080932.03464.n7bfs@qwest.net> (raw)
A question for the list that hopefully will not be too open ended .
Our local packet crew (two guys)is considering changing from DOS based FBB BBS
to a Linux based machine but are concerned about ease of setup and stability.
They wish to use internet forwarding (through a cable modem) and coming out on
VHF node freq'.
My concern is , since I subscribe to this list for other reasons not related
to packet and am not a packet person, I see alot of posts recently about
troubles with the kernel and lockup problems , so my question is , is this
only for folks who are doing non-standard things or is this an issue with any
amateur trying to setup a Linux based FBB BBS with internet forwarding?
I don't want to have given them the wrong impression about Linux stability (I
use it on a daily basis for my desktop), only to have it be a troublesome and
failure prone system , as they are very happy with their DOS based machine ,
they just want to move into the TCP/IP internet based way of forwarding ,
which apparently the dos based one is hard to make so ...
Any input or links/pointers on what not to do would be appreciated , they will
just be starting out with Linux and I am not knowledgable with Linux packet
at all...
tia
--
Douglas Cole N7BFS
Spokane IRLP node owner
AMSAT#26182 , K2 # 544
http://www.users.qwest.net/~cdoug3
Registered Linux user # 188922
next reply other threads:[~2002-12-08 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 17:32 Douglas Cole [this message]
2002-12-08 21:25 ` FBB for linux and internet forwarding Chuck Gelm
2002-12-08 23:25 ` Douglas Cole
2002-12-08 23:34 ` w9ya
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=200212080932.03464.n7bfs@qwest.net \
--to=n7bfs@qwest.net \
--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.