| |
PA2AGA > HDDIG 22.10.99 11:31l 204 Lines 7501 Bytes #-9710 (0) @ EU
BID : HD_99_266E
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/266E
Path: DB0AAB<DB0ZKA<DB0CRL<DB0TTM<DB0FP<DB0SRS<DB0AIS<DB0NDK<DB0ACH<DB0ACC<
PI8DRS<PI8DAZ<PI8GCB<PI8HGL<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 991022/0503Z @:PI8VNW.#ZH2.NLD.EU #:9643 [HvHolland] FBB7.00g $:HD_99_266
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21817 ; Fri, 22 Oct 99 04:29:49 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016535 ; Thu, 21 Oct 99 18:20:50 MET
Date: Thu, 21 Oct 99 18:17:13 MET
Message-Id: <hd_99_266E>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/266E
X-BBS-Msg-Type: B
various updates) provide a guide to the
construction of a bulk transfer protocol. We already use this protocol as
import/export between BBS systems of various kinds. The needed extensions to
the standard set of headers are documented in the
BBS specification. For net news two standard transports exist. One is a bulk
file
transport using the "ihave/iwant" scheme similar to what is called "X
forwarding"
in the BBS network. The needed mappings are obvious and should be simple to
implement.
All the above would require only a small amount of fairly simple programming
effort on the part of the authors of the ham radio
tcp/ip programs, and very little effort on the part of the authors of the ham
radio
BBS programs. The hard work is deciding on the
details of how the mappings will work, and setting up enough
gateway servers to attract users.
One advantage of this scheme is that we could use it to link
existing news groups in the internet directly to the ham radio
BBS network, with bidirectional exchange of messages. Some might consider
this a disadvantage because of the obvious possibility
of abuse by both hams and non-hams. This possibility should not
get in the way of creating and testing the technology.
There is an interesting technique we could use to do this integration. If each
"gateway" server ran a web server with a standard middleware API to a local
database, then the task of programming the needed applications would be fairly
simple. What applications are needed? Those required for the administration of
the "gateway" server itself, for example, to maintain mappings, deal with
exceptions, and all the other "sysop" type of activities.
One could even consider creating a "regular ham radio BBS" using the
capabilities of the web server. This has in fact been done, several times, by
various hams. Perhaps those hams might consider making their work available
to others in the ham radio network as well as on the internet. Doing so might
help move the digital networking facet of our hobby forward. i.e. "The folks
using
html on ham radio are headed in the right direction."
Disclaimer: Yes, I know the above sounds a lot like the integration of ham
radio
networking with the internet. That is exactly what it is. I hope everyone can
understand the difference between taking ideas and techniques from the
internet
for use in ham radio, and replacing ham radio with the internet itself. I
propose
the former, and not the later.
------------------------------------------------------------------------------
As we all can see, it does not mention Windows. It does not even mention
any operating system or environment.
So it is clearly YOUR memory that is faulty. Please have it checked before
you accuse others.
Rob
--
+----------------------------------+--------------------------------------+
| Rob Janssen pe1chl@amsat.org | WWWhome: http://www.pe1chl.demon.nl/ |
| AMPRnet: rob@pe1chl.ampr.org | AX.25 BBS: PE1CHL@PI8WNO.#UTR.NLD.EU |
+----------------------------------+--------------------------------------+
>.
------------------------------
Date: Sun, 17 Oct 1999 09:43:38 -0500
From: "Steve Sampson" <ssampson@usa-site.net>
Subject: The BBS network and tcp/ip.
Charles Brabham wrote
>I gave LINUX a fair trial, and it turned out to be garbage. I'll give
>it another try later on, but not until the problem I mentioned has been
>resolved.
You want us to believe you are an authority on packet radio, with all
the right opinions.... Then you want us to believe that you are an
expert on Operating Systems, with all the right opinions.
I've been employed as a Unix administrator for years, and Linux
represents what most modern Unix systems use as state of the art.
I only run the stable versions, not the development versions. There
is no truth to the fact that Linux is unstable. Even IBM ships Linux
now with their Netfinity servers (high-end NT server base machine).
The only bad thing about Linux, is that it is harder than IBM AIX to
administer. But with AIX I have to wait 3 years to afford the next
update.
My opinion, is that RedHat Linux (I run 5.2) is more stable than
Sun Solaris 2.7 on a dual Pentium motherboard I run. My other
opinion is that Charles doesn't understand Packet radio, and he
doesn't understand Operating Systems. Just my opinion...
That leaves us with a question: why the hell do you even subscribe
to this newsgroup? DOS and GUI-DOS pro-arguments belong
in the fringe alt.* groups...
If you are going to do TCP/IP, and everyone will; then you need to
use a good platform to develop on. Linux is good, DOS would be
the third choice after some of the single-board microcontrollers
that are available now to TCP/IP anything.
Steve Sampson, K5OKC
>.
------------------------------
Date: Mon, 18 Oct 1999 07:27:37 -0500
From: "Steve Sampson" <ssampson@usa-site.net>
Subject: The BBS network and tcp/ip.
Hank Oredson wrote
>Yes, I looked at all the web sites, RPMs, and other references
>provided by the Linux Bigots (and those provided by everyone else
>as well). Not much there. Nothing there that will do what I am already
>doing, much less what I actually want to do.
Use UUCP, it's built-in. Transfers news and email just fine, although
dated. Use JNOS. If it really offends you, call it SNOS and say you
designed it (no source code though). You can probably run it on
Clover.
>But the original issues remain, and have not been addressed by any
>but two posters to this thread. Pretty useless newsgroup. Plenty
>of babblers, very few doers. Got some radios to install and antennas
>to put up, and a bit of new software capability to try out. Anyone
>interested in actually DOING something? Give it a try.
Pot calling the kettle black.
The bottom line, is we (Hams) do not need monolith programs anymore.
Programs that duplicate the stuff built-in to the OS used. Since Unix was
designed, the object has been to build function in modules. Modules that
interact and communicate using pipes, sockets, or even files. Microsoft
even uses this model in their office suite. Office is not a monolith, it
uses
process communication between modules.
JNOS, SNOS, PKNOS, JIMMY-NOS, NOSNOS, they're all monoliths.
They will all do something, and perform work, but who really cares about
an addition to the monolith.
Break the program down, and use the fork/exec, and some inter-process
communication. Don't keep copying/modifying JNOS.
Steve
>.
------------------------------
Date: Sun, 17 Oct 1999 14:25:53 +0100
From: tersigni@usa.net (D. Tersigni)
Subject: Wanted ICOM 207H Cloaning Cable pinout (ocp-646)
I am looking for cloning cable for the the Icom IC-207H I think ICOM's
designator for it is the OCP-646.
Is it just a cable or does it have electronics in it as well?
Does anyone have the pinout?
de Dave Tersigni
K66DUN
>.
------------------------------
End of Ham-Digital Digest V99 #266
******************************
You can send in your contribution to this digest by
sending an e-mail to: hd-group@pa2aga.ampr.org
or (via BBS-net) to: hdaga@pi8vnw.#zh2.nld.eu
Read previous mail | Read next mail
| |
