| |
PA2AGA > PACDIG 24.07.99 00:16l 154 Lines 4547 Bytes #-9786 (0) @ EU
BID : PR_99_170B
Read: GUEST
Subj: PacketRadioDigest 99/170B
Path: DB0AAB<DB0KFB<DB0CZ<DB0GE<DB0ZDF<DB0AIS<DB0NDK<DB0ACH<PI8JOP<PI8ZAA<
PI8HWB<PI8HGL<PI8VNW
Sent: 990723/1939Z @:PI8VNW.#ZH2.NLD.EU #:40736 [HvHolland] FBB7.00g $:PR_99_17
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : PACDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA17790 ; Fri, 23 Jul 99 19:20:41 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00014693 ; Fri, 23 Jul 99 21:01:57 MET
Date: Fri, 23 Jul 99 20:58:21 MET
Message-Id: <pr_99_170B>
From: pa2aga
To: pr_broadcast@pa2aga
Subject: PacketRadioDigest 99/170B
X-BBS-Msg-Type: B
>
> Try to get a life. There's lots more out there than cheapo operating
> systems.
True, that is one of the good things about consumer choice. If you
prefer a different operating system, then you can buy a different
operating system.
>
> 73 DE Charles Brabham,
> N5PVL @ N5PVL.#NTX.TX.USA.NOAM
> http://www.texoma.net/~n5pvl
>
>
>
--
Kirk Job Sluder
Personal Home Page (http://php.ucs.indiana.edu/~csluder/home.html)
Email (csluder@indiana.edu) Radio (KB9TUT)
>.
------------------------------
Date: Wed, 21 Jul 1999 07:40:48 -0500
From: "Charles Brabham" <n5pvl@texoma.net>
Subject: Linuxnet and xfbb?
erik@fornax.nl wrote in message <7n2p8b$8rd$1@nnrp1.deja.com>...
>Dear Om,
>
>We are setting up a bbs/node station. Because of the flexibility we
>want to use linuxnet.
After reading the rest of your post, I got to wondering...
Where is this alleged "flexibility" in LINUX?
After I installed LINUX on one of my machines yesterday, what I got for my
effort was the same old stilted, barren interface I had come to associate
with the mainframe at the local college.. Yuk!
It always amazed me when I was in school that the university's computer was
ten years behind the old Commodore C-128 I was using at the time, as far as
the user interface goes.
Instead of being flexible, LINUX strikes me as being particularly
inflexible. Everything has to be just so, and you end up with the latest in
1970's computing, with lots of archaic commands to memorize because the
interface is so un-intuitive and backward.
I have to admit to being utterly amazed now that some folks see LINUX as
some sort of replacement for more capable operating systems such as DOS or
WinDoze.
Is there ANY advantage in using LINUX instead of DOS or WinDoze? If so,
what might that be? In what way are LINUX users compensated for having to
put up with a 1970's style user interface?
73 DE Charles Brabham,
N5PVL @ N5PVL.#NTX.TX.USA.NOAM
http://www.texoma.net/~n5pvl
>.
------------------------------
Date: Fri, 23 Jul 1999 02:13:59 +0200
From: "Stéphane Bailliez" <bailliez@cybercable.fr>
Subject: Transfer protocols. page/answer and tdma
I don't know if it's the right place to post because there are many
newsgroups about packet radio..so i'm taking the risk..here's my problem.
Let's say I have a network of radios (say 3, one master m , 2 slaves s1 et
s2 )
each radio is plugged on a pc via a rs232.
I would like to implement 2 typical protocols (in software)
One would be a page/answer model, the other one woud be close to a TDMA.
1) Page/Answer.
- master page all slaves at a time
- slave s1 et s2 know their position in the answer cycle. (ie s1 answer t1
seconds after the paging and s2 answers t2 seconds after the paging, t1 and
t2 choosed to avoid collision)
- slaves never send data without the master page.
typically: (## means data send)
M pages S1 and S2 (broadcast)
S1 answers to M (unicast)
S2 answers to M (unicast)
M___##________...._____##_______
S1_____##_____....________##____
S2________##__....___________##____
2)pseudo tdma.
- master page all slaves with a maximum size frame to synchronize all slaves
in a fixed time slot maneer. Then each radio (master and slaves have their
own time slot once for good and will avoid collision). That also means that
each slave do not need a page to send data to the master because they have
their own time slot.
M___##________xx________xx________xx_
S1_____##________##________xx________xx
S2________##________xx________xx________##
I guess this is a pretty good abstract of what I would like to do...so since
I don't want to reinvent the wheel I would like to know if some of you have
any pointers on the internet of where I could find information about similar
protocols implementation. I could certainly benefit from documents floating
around...kind of a design pattern.
Any help is appreciated.
Thanks
Stephane
>.
------------------------------
End of Packet-Radio Digest V99 #170
******************************
You can send in your contribution to this digest by
sending an e-mail to: packet-radio@pa2aga.ampr.org
or (via BBS-net) to: praga@pi8vnw.#zh2.nld.eu
Read previous mail | Read next mail
| |
