OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
PA2AGA > HDDIG    01.11.99 23:12l 198 Lines 6091 Bytes #-9698 (0) @ EU
BID : HD_99_278B
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/278B
Path: DB0AAB<DB0KFB<DB0ZKA<DB0ABH<DB0SRS<DB0ROF<DB0ERF<DB0BRI<PI8DRS<PI8DAZ<
      PI8GCB<PI8HGL<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 991101/1931Z @:PI8VNW.#ZH2.NLD.EU #:12228 [HvHolland] FBB7.00g $:HD_99_27
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To  : HDDIG@EU

Received: from pa2aga by pi1hvh with SMTP
	id AA22379 ; Mon, 01 Nov 99 18:59:40 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
	id AA00016694 ; Mon, 01 Nov 99 19:16:25 MET
Date: Mon, 01 Nov 99 19:13:50 MET
Message-Id: <hd_99_278B>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/278B
X-BBS-Msg-Type: B

From: "Charles Brabham" <n5pvl@texoma.net>
Subject: FCC reallocates Ham Band

Steve Sampson <ssampson@usa-site.net> wrote in message
news:381CDB67.ABACA3B0@usa-site.net...
>
> All the more reason that Hams should be moved completely
> to HF bands, and the commercial interests can take over
> and produce 21st Century products in the vacated VHF, UHF,
> and SHF bands.

Gee, what an ignorant scumbag. This is the same moron who recently crowed
with joy because a BBS in Oklahoma city shut down. That BBS was owned by a
Ham who lost everything he had in the tornadoes last May.  -- And this bag
of dog-doo knew that.

That's the kind of guy Steve is. We've all scraped much better off of our
shoes after walking through the neighbor's yard.

A good TAPR devotee since he's such a great eat ass-kisser for "Geek" Jones,
and a piss-poor excuse for a man. - And of course a good example of the kind
of scum that Ham Radio would be much, much better off without.

Let's all join in letting this moron know how we feel about his ignorant,
nasty, anti-Ham attitudes.

--
73 DE Charles Brabham, N5PVL
N5PVL @ N5PVL.#NTX.TX.USA.NOAM
http://www.texoma.net/~n5pvl






>.

------------------------------

Date: 1 Nov 1999 02:18:09 GMT
From: Hamish Moffatt <hamish@rising.com.au>
Subject: FCC reallocates Ham Band

Steve Sampson <ssampson@usa-site.net> wrote:
> All the more reason that Hams should be moved completely
> to HF bands, and the commercial interests can take over
> and produce 21st Century products in the vacated VHF, UHF,
> and SHF bands.

With friends like this, who needs enemies?


Hamish
-- 
Hamish Moffatt       Mobile: +61 412 011 176     hamish@rising.com.au
Rising Software Australia Pty. Ltd.    http://www.risingsoftware.com/
Phone: +61 3 9894 4788    Fax: +61 3 9894 3362    USA: 1 888 667 7839
>.

------------------------------

Date: Sun, 31 Oct 1999 07:54:38 -0800
From: Chris Nicholson <csnichol@netusa1.net>
Subject: FCC reallocates Ham Band

Mike,
I tuned up an old Lenkurt 1w video transmitter and reciever on 5880.
Worked quite well beaming pictures across the garage. I did not
have enough waveguide untill the other day I helped remove 300'
of flexwell from a tower and took 1/3 of it home. The link given 
to the text of the reallocation did not work for me. So now that I can 
set the things up to go across town I might as well throw them away. I
guess I can use the room in the storage shed.

    Chris
    N9LLO



Mike Hughes wrote:
> 
> I realize that ANY loss of Amateur spectrum is bad, but is anyone actually
doing
> anything on that band?
> 
> Steve Sampson wrote in message ...
> >On October 21st, the FCC released notice:
> >
>
>http://www.fcc.gov/Bureaus/Engineering_Technology/News_Releases/1999/nret900
> >6.html
> >
> >The Amateur and ISM secondary allocation will cease to exist in the 5850 -
> >5925 MHz band.
> >There was also a radio-location allocation, but GPS has replaced most of
> >those functions.
> >
> >
> >
>.

------------------------------

Date: Mon, 01 Nov 1999 06:16:41 -0500
From: no.spam@no.junk.mail
Subject: FCC reallocates Ham Band

On Sun, 31 Oct 1999 19:11:26 -0600, "Charles Brabham" <n5pvl@texoma.net>
wrote:
>
>Steve Sampson <ssampson@usa-site.net> wrote in message
>news:381CDB67.ABACA3B0@usa-site.net...
>>
>> All the more reason that Hams should be moved completely
>> to HF bands, and the commercial interests can take over
>> and produce 21st Century products in the vacated VHF, UHF,
>> and SHF bands.
>
>Gee, what an ig... <rant clipped> much better off without.
>
>Let's all join in letting this moron know how we feel about his ignorant,
>nasty, anti-Ham attitudes.
>

Obvious to most, the aging technology of a bunch of 55+year old men is only
worth preserving if it doesn't cost anything. The spectrum wasted by these
aging, glorified, cb'ers will eventually be reclaimed for more practical use. 

Either set the pace, or get out of the way... 
>.

------------------------------

Date: Sun, 31 Oct 1999 10:30:09 -0800
From: "Hank Oredson" <horedson@att.net>
Subject: Help with RFC

One place it is quoted is RFC-1122:

1.2.2  Robustness Principle

         At every layer of the protocols, there is a general rule whose
         application can lead to enormous benefits in robustness and
         interoperability [IP:1]:

                "Be liberal in what you accept, and
                 conservative in what you send"

         Software should be written to deal with every conceivable
         error, no matter how unlikely; sooner or later a packet will
         come in with that particular combination of errors and
         attributes, and unless the software is prepared, chaos can
         ensue.  In general, it is best to assume that the network is
         filled with malevolent entities that will send in packets
         designed to have the worst possible effect.  This assumption
         will lead to suitable protective design, although the most
         serious problems in the Internet have been caused by
         unenvisaged mechanisms triggered by low-probability events;



Internet Engineering Task Force                                [Page 12]





RFC1122                       INTRODUCTION                  October 1989


         mere human malice would never have taken so devious a course!

         Adaptability to change must be designed into all levels of
         Internet host software.  As a simple example, consider a
         protocol specification that contains an enumeration of values
         for a particular header field -- e.g., a type field, a port
         number, or an error code; this enumeration must be assumed to


To be continued in digest: hd_99_278C




Read previous mail | Read next mail


 22.05.2026 23:44:12lGo back Go up