| |
PA2AGA > HDDIG 15.10.99 15:21l 206 Lines 6967 Bytes #-9718 (0) @ EU
BID : HD_99_258D
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/258D
Path: DB0AAB<DB0ZKA<DB0ABH<DB0BOX<DB0MAK<OK0PKL<OK0PPR<OK0PPL<OK0POK<9A0YRB<
PP5BLU<IW9EXL<SV1AAW<SV1AAW<EA7URC<PE0MAR<PI8VNW
Sent: 991015/0853Z @:PI8VNW.#ZH2.NLD.EU #:8019 [HvHolland] FBB7.00g $:HD_99_258
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21304 ; Fri, 15 Oct 99 08:23:20 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016388 ; Fri, 15 Oct 99 08:02:25 MET
Date: Fri, 15 Oct 99 08:00:34 MET
Message-Id: <hd_99_258D>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/258D
X-BBS-Msg-Type: B
> >experimenting with something, and the adoption of this "somthing"
> >into general use in the network.
>
> "the network" is just a bunch of people experimenting with whatever
> they find interesting. This also varies from location to location,
> as some of these experiments are only useful when more than one
> station is involved.
> When do you call it "general use"?
>
> >> My own bi-directonal mail forwarder has been working since Feb 1990.
>
> >I've put what I have done onto my web site so anyone can
> >look at it and make suggestions. Where do I find information
> >about yours?
>
> It has been on my website for years...
I saw nothing about bbs message <-> smtp/pop and bbs bulletin <-> nntp.
Perhaps this information is buried somewhere in the documentation?
--
... Hank
http://horedson.home.att.net
>.
------------------------------
Date: Tue, 12 Oct 1999 06:13:19 GMT
From: nomail@pe1chl.demon.nl (Rob Janssen)
Subject: The BBS network and tcp/ip.
Hank Oredson <horedson@att.net> wrote:
>> It has been on my website for years...
>I saw nothing about bbs message <-> smtp/pop and bbs bulletin <-> nntp.
>Perhaps this information is buried somewhere in the documentation?
Yes, it is. There is no bulletin <-> nntp support in this program.
The documentation is no discussion about forwarding in general, but a
description how it is to be setup when using the software on the site.
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, 12 Oct 1999 08:43:41 GMT
From: nomail@pe1chl.demon.nl (Rob Janssen)
Subject: The BBS network and tcp/ip.
Hank Oredson <horedson@att.net> wrote:
>> Then what do you want?
>Ideas.
Ok here is an idea:
What you want already exists. Under Linux. So, the problem is not how to
write the software itself.
But the installation of this stuff is too complicated for the average HAM
(tell me something that is *not* too complicated for the average HAM...),
so what you need to do is write a foolproof installation wizard.
There is good documentation, but the average computer user just not wants
to bother to read documentation. They want to plug and play. Therefore
you need the wizard.
Just start with a recent Linux distribution, create an installation list
for it (a list of packages to be installed), and write a program or a
module for the distribution's system administration tool to configure the
hamradio stuff after asking such simple information as:
- callsign
- hardware you want to use (tnc's on what ports, soundcard, scc card etc)
- do you want to be a BBS?
- do you want to be a NODE?
etc.
Put everything on a bootable CD, and distribute the ISO image.
The installation list will take care of installing the packages required
for the purpose, you can put other optional packages on the CD for the
experienced user.
After installation, your wizard will run (you have put it in a package
and have arranged for it to run after the first boot), and the user enters
all his configuration info.
Make all user-entered info saveable on a floppy disk.
Then, the system behaves as specified (as a BBS, a NODE, a user station,
whatever) with all the features you would like to have.
(forwarding and gatewaying, smtp/pop/nntp/http/ftp/etc server, browser...)
Now you should have a system that is easily installed by the average HAM
(and probably even easier by those who have some experience sysopping a BBS
or NODE), and that can be treated just like they would treat a DOS or
Windows system: when it fails for some reason the operator does not
understand, just re-install.
To help the somewhat more experienced, you can make two different images:
one containing everything including the Linux distribution, and one
containing only the material you have added. The latter could be installed
as an add-on to an existing installation, or could be used by a HAM
who can run a Linux installer by himself and wants to save on download
cost.
Maybe you'll even include some mechanism to carry-over existing
configuration data and/or messages from a legacy DOS or Windows system.
That would allow painless migration of existing systems into the new world.
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: Mon, 11 Oct 1999 19:07:42 +0000
From: "D. Stussy" <kd6lvw@bde-arc.ampr.org>
Subject: The BBS network and tcp/ip. (Web page graphics)
On Sun, 10 Oct 1999, Charles Brabham wrote:
D. Stussy <kd6lvw@bde-arc.ampr.org> wrote in message
> news:Pine.LNX.4.10.9910100416200.671-100000@dns.bde-arc.ampr.org...
> .
> > - Web pages: Only text-only pages of probably no more than 4k should
> > be allowed - all others should probably be banned. (size could be
> adjusted)
>
> See the article "HTML and Packet Radio" at my web-site. Just push the
> "Articles" button, and go from there.
>
> It describes an effective method (currently in use) to allow use of graphics
> on low speed links for HTML/Packet Radio.
>
> It works. There's a demo included. Check it out.
Well, like I said, that's my personal view.
I feel that web page size should be restricted and text only, just because I
don't feel it's appropriate for a station to wait 15 minutes for a 300Kb
graphics image on a page to appear via a 1200 baud link.
Of course, where higher speeds exist, higher limits should exist too. (...And
maybe at 56Kbaud/s, no limit?) Remember that this is HALF-DUPLEX in most
cases, so that telco modem speeds aren't the same (in comparison).
>.
------------------------------
Date: Tue, 12 Oct 1999 00:22:02 -0500
From: "Dave Covert" <davecove@thecoverts.com>
Subject: WEFAX format...
Can anyone provide me (or point me to) a detailed description of the HF
Wefax format? I feel like writing some code... <g>
Dave KB5GOG
>.
------------------------------
End of Ham-Digital Digest V99 #258
******************************
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
| |
