| |
PA2AGA > HDDIG 15.10.99 16:41l 210 Lines 7712 Bytes #-9718 (0) @ EU
BID : HD_99_259C
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/259C
Path: DB0AAB<DB0FSG<IN3TRX<OE7XBB<DB0PV<OE2XOM<OE5XBL<OE3XSR<OK0PBX<OK0PHL<
SP6KBL<SP6YCU<SR6DJG<SR6DJC<SR9ZAA<PP5BLU<IW9EXL<SV1AAW<SV1AAW<EA7URC<
PE0MAR<PI8VNW
Sent: 991015/1019Z @:PI8VNW.#ZH2.NLD.EU #:8093 [HvHolland] FBB7.00g $:HD_99_259
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21310 ; Fri, 15 Oct 99 09:40:36 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016397 ; Fri, 15 Oct 99 08:02:57 MET
Date: Fri, 15 Oct 99 08:00:39 MET
Message-Id: <hd_99_259C>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/259C
X-BBS-Msg-Type: B
the
> gateways can be found on the usual Ham software for Linux sites.
I have "internet servers".
They are easy to get, for any operating system.
I have them for DOS, for Win9x, for WinNT, for Linux, etc.
What gateways? I have no idea what you are talking about.
> What else do you need?
I'll try again. I am NOT, repeat NOT, looking for code.
I have code. I can create code. I am looking for ideas.
> >Most hams do not (and will not) have Linux.
> >So Linux is not of interest to me.
>
> My proposal was a method to let them have Linux. Why do you think
> it is not feasible?
I did not say it was unfeasible. I said that most hams do not,
and will not have it, and that I am not interested in it. Someone
else can push Linux to hams. I will not do that. Let them run
whatever operating system they wish on their computers.
It is of no interest to me which OS they use. I notice that most
hams have machines running Windows 9x, or possibly DOS.
So I will write code for those operating systems, so that hams
can use what I write. But what code to write? That is the question.
> Because a HAM will not understand Linux and cannot make changes to the
> system? Trust me, a HAM does not understand Windows either, and can only
> resort to standard tricks to solve problems (like re-installation).
So what? My project has nothing to do with understanding
operating systems. I do not care if hams understand the operating
system they use.
> The situation with Linux is not much different, except that those who WANT
> to get in-depth knowledge of the system have the opportunity to study it.
Nothing to do with my project. Some other project for someone else.
> >But in any case I am not looking for solutions. Those I can create.
>
> Solutions have already been created.
Show them to me. I find none at all, for any operating system.
I do not want to see code, but ideas for what COULD be done.
I will create the code to implement the ideas I find interesting.
> Making them available for everyone is what is missing, when I correctly
> understand your earlier posting.
I think you do not understand my postings on this topic.
> 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 12:31:43 -0700
From: "Cathryn Mataga" <cathryn@junglevision.com>
Subject: The BBS network and tcp/ip.
Hank Oredson wrote in message <7tvj6n$jld$1@bgtnsc03.worldnet.att.net>...
>
>Rob Janssen <nomail@pe1chl.demon.nl> wrote in message
>news:slrn805t5t.835.nomail@linux.pe1chl.ampr.org...
>> 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.
>
>I have Linux.
>Did not find any such software.
>Most hams do not (and will not) have Linux.
>So Linux is not of interest to me.
>
>But in any case I am not looking for solutions. Those I can create.
Yeah, on Linux, to do NNTP/PBBS stuff, you need to install
the News server, INN, and another program called mailgw.
Me, I tried installing INN from the source, and gave up after
a few days. But, then I just tried the rpm that Redhat has
for 6.0, and it came right up, hehe. When linked to FBB
with mailgw, this is a pretty deluxe setup. Though mailgw is
a little bit rough going for people not able to muck with
the source code. If running proper 'nntp' servers is 'the right' thing
to be doing, then I think it's going to be much easier on
some kind of Unix variant. Though I'm not 100% clear
on what the stuff you've been working on does.
If you want to stay in Win32/DOS stuff, I understand that.
>I am looking for ideas about WHAT problems might be solved,
>and how the applications that implement those solutions might
>be structured so they would be of interest to hams.
>
>Your points about installation are well taken, and "simple"
>installation is a part of what I am working on now.
Understood. Okay, just to stir the pot a bit. I'll just toss out some
stuff without too much research into what maybe is being done
already.
What about PBBS/POCSAG integration?
This is something I've been thinking. That PBBS might survive
by shrinking a little bit. I've been thinking it would be cool
to do, a BBS patch, where when a message came
in, the BBS, could beep on the POCSAG frequency, So, like maybe
the message could come in on the pager that you had a message,
or maybe we could stick in little
POCSAG:I'm coming next Tuesday
lines in the top of our PBBS messages. Then, if your homebbs had
this feature, it'd beep in your pocket. It might be as simple as specifying
a forward to a file, and then having this code look at the file, and beep
appropriately. That is somehow decide what to say on the beeper, if
the message is too big.
Maybe it'd be possible to build a new backbone system on the internet
for this, rather than using PBBS, though it seems that PBBS might
be appropriate for this kind of data also.
There might be other ways to make ham packet radio smaller.
That is clients for palmtops and things like this.
.....
My understanding is that there's going to be an improved TCP/IP mode
for the new 2.3 Linux kernels, and it'd be nice to get a Win98 stack that
could talk to these drivers. That is sv2agw style -- the VXd's and all that.
Check out. I think I got it right.
http://dl0td.afthd.tu-darmstadt.de/~dg2fef/ax25.html
I'm not too hip on what's happening with this stuff here so maybe I'm off
base here. Still, if this is what's going in the 2.3 kernel, than
it's likely that people on the Linux side are going to have this, and it'd
be nice to be able to run the same tweaks on Win98. (And, I think you can
get the source code right now -- and run a Linux box as a test
implementation.)
Come to think of it, I wonder if anyone has taken up Robert McGwier's
offer to help with a Win98 version of his code? Me, I think it'd be
nice to have an all software, GPL, substitute for Pactor without the patent
restrictions and all that. And, it looks like this guy has done a lot of the
Phd level stuff already.
......
This is a silly thing, I've been thinking, but watching all the PBBS traffic
come out from N6EEG, I see it send the same message over and over again,
on the same lan, But I wonder if it'd be possible to pick out the PBBS
messages from the connections to other BBS's. Are there enough
sequence bytes and stuff in the ax25 headers to know if any data is
missing? Seems, like if the hub BBS sent out all the data once, then
everyone else could listen in on the frequency and read off what they
could get. And then when the hub BBS connected out, it would only
need to download the messages that were missed.
This kind of thing might also even work on HF, since I see the similar
situation on HF packet frequencies.
I had the idea, which I mean to code at some point, of broadcasting
PBBS messages in the beacon using Pactor FEC mode. That is
To be continued in digest: hd_99_259D
Read previous mail | Read next mail
| |
