| |
PA2AGA > HDDIG 22.10.99 10:18l 189 Lines 7641 Bytes #-9710 (0) @ EU
BID : HD_99_266D
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/266D
Path: DB0AAB<DB0ZKA<DB0CRL<DB0TTM<DB0FP<DB0SRS<DB0ROF<DB0MW<DB0NHM<DB0SHG<
DB0SM<DB0PKE<PI8DRS<PI8DAZ<PI8GCB<PI8HGL<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 991022/0426Z @:PI8VNW.#ZH2.NLD.EU #:9632 [HvHolland] FBB7.00g $:HD_99_266
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21811 ; Fri, 22 Oct 99 03:26:13 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016532 ; Thu, 21 Oct 99 18:20:39 MET
Date: Thu, 21 Oct 99 18:17:10 MET
Message-Id: <hd_99_266D>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/266D
X-BBS-Msg-Type: B
Perhaps someone edited your post before I saw it on the local newsserver?
However, in answering how to do that under windows, good luck. I know of no
programs that do the conversion, and even then, you'll probably have to move
to
Windows NT because some of the features you're looking for are available only
as servers and '95 just doesn't have server utilities. I don't use NT because
I need my data to be stored and manipulated reliably.
BTW, in the mid 1980's, I was already bitching about the Micro$oft
shortcomings
in their programs (including certain bugs in MS-DOS 3.1), LONG BEFORE Linux
was
even created. It's not that I'm pro-Linux; I'm anti-incompetence and
incompetence == Micro$oft.
The only reason why Micro$oft is the business powerhorse it is today is
because
of the original licensing agreement with IBM back in 1981, and with the
PC-clone makers in 1985, requiring them to distribute the OS with every
computer. With that, and everyone else writing software for that platform
(and
thus no alternative platforms), there was simply nothing to stop their poor
quality control.
The computer software industry is the only industry where a defective product
can be sold without liability attaching to the manufacturer - and furthermore,
the only one where the end-customer is charged for fixing the defects. Try
that with any other industry and the manufacturer would be bankrupt from all
the claims. 25 years ago, such wasn't the standard. Bug fixes were usually
required to be provided free of charge since the program never met the
"original specification" with the side effects. That changed when the
industry
moved to "licensing software" instead of contract-on-demand authorship.
Why do you think Bill Gates is afraid of the word "Linux?" It's because he
realizes that a viable alternative OS has surfaced that could end his
monopoly of fact.
> I'm quite certain of this since I started the thread.
>
> Linux did not enter in until certain Linux Bigots took over the thread.
>
> In any case Linux will not help with the project at hand, since it is
> being done in Windows. You (all the Linux Bigots) don't like that,
> do it in Linux. Ain't been done yet, even though the Linux Bigots
> claim it has. A good deal of progress in Windows, by several
> different authors.
>
> 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.
>
> 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.
Interesting, considering this is coming from someone who recently CLOSED his
packet BBS (at least per the "WestNet" listing). Is that because you wanted
to
experiment, or some other reason?
>.
------------------------------
Date: Tue, 19 Oct 1999 09:09:58 GMT
From: nomail@pe1chl.demon.nl (Rob Janssen)
Subject: The BBS network and tcp/ip.
Hank Oredson <horedson@att.net> wrote:
>My point holds (about Linux Bigots).
>This Windows 98 system is in fact "doing that" under windows.
>Can't "do that" in Linux, the software does not exist.
Hank Oredson could not find it. It does exist.
>Those two facts seem to be the sole and only things one can
>learn from this thread: that the Linux Bigots think everything
>can be done in Linux (when it cannot), and think nothing can
>be done in Windows (when almost everything can).
What we also learn is that Hank Oredson will not acknowledge the
existance of software that has been seen running by several other
posters on the group, just because he has been unable to find it
himself.
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: Tue, 19 Oct 1999 09:22:17 GMT
From: nomail@pe1chl.demon.nl (Rob Janssen)
Subject: The BBS network and tcp/ip.
Hank Oredson <horedson@att.net> wrote:
>> It's worth checking, but I believe that the "using Windows" wasn't stated
>as
>> part of it. You were asking for the simplist way to gate mail and
>newsgroups.
>> Perhaps someone edited your post before I saw it on the local newsserver?
>Perhaps your memory is faulty.
Ok, I have fetched your original article from www.deja.com.
You know, one of those nice search tools we have available on the Internet
to find things we are not sure they exit.
Oh, wait... you don't know about those. Maybe you should try to have
a look there, you might find some things there you claimed do not exist!
Well, here it goes:
------------------------------------------------------------------------------
A couple folks asked that I repost my specific suggestions
on how to migrate the existing BBS network to the model in
current use on the internet. Here they are again. Not well
organized, a bit of babble, but specific ideas. Would they
work in practice? I don't know (yet) but may implement some
of them and find out.
Each BBS network message type has an equivalent internet
application and protocol. For the BBS network to interoperate
with these applications and protocols we need some number
of "gateway" systems which do the appropriate translations.
1) Bulletins map to net news and the nntp protocol.
We need a set of newsgroups defined to map to/from the common BBS
network topics. One solution would be to use newsgroups
of the form alt.hamradio.<topic> where <topic> is the To: field of the BBS
message. Thus we would have, for example,
alt.hamradio.keps, alt.hamradio.sysop, alt.hamradio.all
The "gateway" servers would move messages both directions using the
obvious and simple mapping.
2) Personal messages map to standard email and the pop3/smtp protocols.
We can use the obvious address mapping. I've run this kind
of "gateway" server for years, using a version of JNOS. It works fine, and
is
already available.
3) NTS messages are an intersting case. They probably need to map to net
news and the nntp protocol. We might use a newsgroup
such as alt.hamradio.nts-traffic for this purpose. In this
case the same "gateway" servers which handle 1) will suffice. Ideas
welcome
from the NTS folks on how we might handle this.
Note that we do not need "permission" from NIS or anyone else to begin to
implement this capability. Everything exists within the ham radio network and
not within the internet per se. The model
is designed to be compatible with internet standards for the obvious reason:
those standards exist and are well tested. We should use them.
For some of the standards, file transfer protocols also exist. For example
email
has pop3 and smtp as network data transfer standards, and RFC-822 (and it's
To be continued in digest: hd_99_266E
Read previous mail | Read next mail
| |
