| |
ZL3AI > APRDIG 08.02.03 10:49l 283 Lines 9376 Bytes #999 (0) @ WW
BID : 867-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 05, 1/5
Path: DB0FHN<DB0ZWI<DB0HST<HB9OK<IK6PYS<ON0AR<ZL2BAU<ZL3VML
Sent: 030207/0917Z @:ZL3VML.#80.NZL.OC #:58987 [Chch-NZ] FBB7.00i $:867-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Wednesday, February 05, 2003.
1. Re: A brief explanation
2. WinAPRS Maps - UK?
3. FW: [USA_Skywarn] Shuttle Recovery efforts need volunteers
4. Re: KISS TNC nearly a digipeater...
5. PERL PID
6. xsatir pid autostart
7. Re: PERL PID
8. Temporarily offline
9. Re: xsatir pid autostart
10. Re: xsatir pid autostart
11. Re: PERL PID
12. Re: [ Steve Dimse ] Re: xsatir pid autostart
13. Winter 2003 Packet Status Register Available
14. Re: [ Steve Dimse ] Re: xsatir pid autostart
15. Re: KISS TNC nearly a digipeater...
16. Re: xsatir pid autostart
17. findU changes
18. Re: xsatir pid autostart
19. re: aprs spec/words of warning
20. re: aprs spec/words of warning
21. re: aprs spec/words of warning
22. Re: New spec - working notes
23. Re: A brief explanation
24. Re: KISS TNC nearly a digipeater...
25. Glossy Eyed Readers [was: aprs spec/words of warning]
26. Re: Glossy Eyed Readers [was: aprs spec/words of warning]
27. Re: Glossy Eyed Readers [was: aprs spec/words of warning]
28. Re: Glossy Eyed Readers [was: aprs spec/words of warning]
29. Re: findU changes
30. Re: Glossy Eyed Readers [was: aprs spec/words of wa rning]
31. re: aprs spec/words of warning
32. re: aprs spec/words of warning
33. Re: [aprsspec] re: aprs spec/words of warning
34. FS: Yaesu FT-90R Dual Band XCVR
35. Re: Glossy Eyed Readers [was: aprs spec/words of warning]
36. re: aprs spec/words of warning
37. re: aprs spec/words of warning
38. Re: [RadioModifications] laptop computers
39. Spec discussion move
40. airmobile
----------------------------------------------------------------------
Subject: Re: A brief explanation
From: Adi Linden <adil@adis.on.ca>
Date: Wed, 5 Feb 2003 00:12:29 -0600 (CST)
X-Message-Number: 1
>A number of people have asked for clarification on what exactly I'm trying
>to do with a new protocol spec, so I'll try to explain my goals here, simply
>and briefly.
I am following this thread with great interest. I think it's a pretty neat
and useful idea that has potential. Since I am pretty new to the whole
APRS business I am just a passive observer for now. Still have a number of
things to do before there is a useable igate and digipeater where I live.
Adi
----------------------------------------------------------------------
Subject: WinAPRS Maps - UK?
From: Ken Collins <g4fip@btinternet.com>
Date: Wed, 5 Feb 2003 09:28:52 +0000
X-Message-Number: 2
Does anyone have any good WinAPRS maps for the UK?
I have obtained two maps from the APRSUK site but these don't meet my
requirements.
--
Ken Collins - G4FIP
E-mail:- g4fip@btinternet.com
http://www.g4fip.btinternet.co.uk
----------------------------------------------------------------------
Subject: FW: [USA_Skywarn] Shuttle Recovery efforts need volunteers
From: "Dakota Summerhawk" <dakotas@hotpop.com>
Date: Wed, 5 Feb 2003 06:12:54 -0700
X-Message-Number: 3
-----Original Message-----
From: Sam Barricklow [mailto:k5kj@pulse.net]
Sent: Wednesday, February 05, 2003 6:02 AM
To: SKYWARN USA
Subject: [USA_Skywarn] Shuttle Recovery efforts need volunteers
RACES and ARES trained licensed amateur radio volunteers are needed for
the shuttle recovery efforts underway in East Texas.
The following is the info that has been sent out to the Collin County
ARES and Dallas County RACES Groups. The driving directions are from the
Dallas area. Please read the entire message and send an email and check
with the local contacts prior to departure. Plan on being self sufficent
( ie dressed for weather conditions, own water, drinks, snacks, etc).
Again please check with Kevin Anderson, KD5CCH kevin@andersoft.com to
find out thier current needs as they may change with little notice.
Columbia Shuttle Recovery Request Update 1
Operators are needed to assist with recovery efforts based from
Nacogdoches, TX. It is approximately 173 miles or 3.5 hours by going
east on Interstate 20/80, south on US 259, take the 59 loop on the west
side of town and exit east on Texas 21W into town. Much of the area to
be worked is rugged and outside local repeater coverage. Some operators
may be sent to San Augustine, Lufkin or to Hemphill depending on
requirements.
The forecast for that area of the state for the remainder of the week
includes rain and possible thunderstorms beginning this evening and
persisting through most of Thursday. The area is heavily wooded, with
swampy areas. The woods of the Big Thicket area of East Texas include
thick underbrush with thorny vines. Come prepared with rubber boots
and rain gear.
Equipment COMMUNICATOR RESOURCE TYPE M - MOBILE
Primary operations will be on 147.32 (+) PL:141.3
High Power VHF and good antenna (HT w/rubber duck will not be adequate
for primary radio)
Other VHF frequencies: 146.74 (-) PL 118.8 in San Augustine
145.37 (-) PL 88.5 further out There may be operations on 444.575+ and
possibly on 7285 KHz HF. Four Wheel Drive vehicles will be an advantage,
however, they are not mandatory. Cellphones may be useful but are also
not mandatory.
Civilian GPS coordinates will not be used as an official reference for
debri located. GPS is highly recommended for purposes of personal
navigation. Additionally, laptops with mapping programs may be very
useful to those not familiar with the county.
As you travel to Nacogdoches, monitor 147.32 and check in as soon as you
have a strong signal so they can re-direct you if necessary to a duty
post.
NOTE: All operators must keep track of mileage and times worked to be
turned in to officials.
Our central contact point is Kevin Anderson, KD5CCH. Please contact him
via email if you can't report when expected or if you must cancel and
please copy me as well.
Contact via email is to: kevin@andersoft.com and aa5qx@arrl.net.
For additional information regarding Communicator Resource Types go to
John Galvin's webpage at www.qsl.net/n5tim and select the listing on the
left column of his page or go directly to
http://home.attbi.com/~jrgalvin2/resourcetypeV2.pdf.
----------------------------------------------------------------------
Subject: Re: KISS TNC nearly a digipeater...
From: John Kraus <jfkraus2@cox.net>
Date: Wed, 05 Feb 2003 09:20:59 -0500
X-Message-Number: 4
A much more elegant solution is to use Henk's Amazing Instant Digi Disk
with any old 286 or better PC with that KISS TNC. Works great.
http://www.homepages.hetnet.nl/~remko/software/diginedE_partner.htm#easy
I keep two identical bootable floppies in a plastic case in my jump kit
along with a modem cable and some port adapters. Any PC that still has a
serial port will work. I also have a small terminal program on the disk
and several utilities.
It also dosn't hurt to keep some of the old PC's around either. I grab
them whenever I am offered one. I check them out and set up a minimal dos
system with Digi_Ned and APRSDos.
----------------------------------------------------------------------
Subject: PERL PID
From: Andrew Rich <andrew.rich@bigpond.com>
Date: 06 Feb 2003 00:40:16 +1000
X-Message-Number: 5
I am trying to test for the presence of a PID for a program.
If it is nit running, then start it
How would I do this ?
#!/usr/bin/perl
@andy = `pidof xastir`;
if (xxxxxxxxxx)
etc
----------------------------------------------------------------------
Subject: xsatir pid autostart
From: Andrew Rich <andrew.rich@bigpond.com>
Date: 06 Feb 2003 00:59:33 +1000
X-Message-Number: 6
#!/bin/bash
t=`pidof xastir` # Find pid (process id) of $process.
if [ -z "$t" ] # If process not present, 'pidof' returns null.
then
`DISPLAY=192.168.0.2:0.0`
`export DISPLAY`
`/usr/local/bin/xastir `
fi
exit 0
~
does not work, "can't open display"
ideas ?
----------------------------------------------------------------------
Subject: Re: PERL PID
From: Steve Dimse <k4hg@tapr.org>
Date: Wed, 5 Feb 2003 09:58:17 -0500
X-Message-Number: 7
On 2/6/03 at 12:40 AM andrew.rich@bigpond.com (Andrew Rich) sent:
>I am trying to test for the presence of a PID for a program.
>
>If it is nit running, then start it
>
>How would I do this ?
>
>#!/usr/bin/perl
>@andy = `pidof xastir`;
>if (xxxxxxxxxx)
>
>etc
Sounds like you are trying to do a watchdog. Remember the Perl motto
TIMTOWTDI (there is more than one way to do it)! Here is one way:
----------
#!/usr/bin/perl
while (1)
{
$count = `ps aux | grep xastir | wc -l`; #this gives the number
#of processes containing xastir. One will be the
#"grep xastir", so a count < 2 means xastir is not running
system("nohup xastir &") if ($count < 2);
sleep(15); #No need to check more othen than every few seconds.
}
-------------
Is this what you are after?
Steve K4HG
----------------------------------------------------------------------
Subject: Temporarily offline
From: "Mike Wolthuis" <wolthui3@msu.edu>
Date: Wed, 5 Feb 2003 09:58:04 -0500
X-Message-Number: 8
Attn: Michigan APRS users
Cc: miaprs@yahoogroups.com
The Grand Rapids, Michigan IGATE and SatGate are temporarily offline for
maintence. This includes the full satellite feed on port 10251 and
standard igate operations.
Operations should be restored within 2-3 hours. Sorry for the
interruption,
Mike Wolthuis
Kb8zgl
----------------------------------------------------------------------
Read previous mail | Read next mail
| |