[App_rpt-users] GPIO fan control script now available

Jim Kehler kh2d at bellsouth.net
Mon Jan 30 16:47:49 EST 2012


Look at it this way, Marshal. Let's say you get up on Friday morning and 
your wife
wants to go out to dinner that night. At 6 PM you find out that every 
restaurant
within 500 miles of your house has closed up and gone out of business, 
with the
exception of one; Freddy's Diner.

So you have no choice. You have to take the wife to Freddy's. And the 
only thing
you'll get to eat at Freddy's is whatever Freddy decides to feed you. If 
Freddy
doesn't want you have Apple Pie, you aren't going to get any Apple Pie. 
No matter
how much you beg Freddy.....

I've only been playing with this stuff for about a month. I'd never seen 
Linux. Some
documentation I found assumed that I was proficient with Linux, which 
I'm not. So
banging around in Google finding bits and pieces was a learning 
experience; I don't
like to just make something work, I want to know how it works so that if 
it breaks,
I can fix it.

Documentation at all levels is a good thing. The more the merrier. As 
long as Google
is still in business, it's available to anybody that wants to go find 
it. All the scripts
in one place sounds like a terrific idea to me. Hopefully the guys who 
wrote them
won't assume I know how to use them when I find them.

That being said, does anybody know where I can find the fan script? My 
radio is
hot....

73, Jim KH2D


On 1/30/2012 2:18 PM, Marshall Oldham wrote:
> Scott,
>
> That is a very generous offer on your part, but wouldn't it be better to keep everything all in one place for folks to
> go use as a reference? Especially new allstar node owners?
>
> So, I will state this question again. Am I missing something? Why doesn't anyone want to use
> the official help site?
>
> If you go to the allstar.org webpage and click on the link that says "help" it will take you to the another page.
>
> If you click on "Links To Helpful Things Pertaining to this Technology"
>
> The first thing that comes up is "Asterisk/app_rpt project -- Lots of good documentation on the Asterisk app_rpt application"
>
> You click on that link and it takes you to http://ohnosec.org/drupal/
>
> So why can't documentation, information and scripts be posted on this website which was setup by the app_rpt creators?
>
> After all, isn't this site kind of the "Official" site for support?
>
> I don't think it's a good idea to have several fragmented websites with information when we already have the official one that is
> pretty good.
> Having multiple websites will confuse new users on where to get information.
>
> 73
>
> Marshall - ke6pcv
>
>> -----Original Message-----
>> From: app_rpt-users-bounces at ohnosec.org
>> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Scott
>> Zimmerman
>> Sent: Monday, January 30, 2012 10:01 AM
>> To: app_rpt mailing list
>> Subject: Re: [App_rpt-users] GPIO fan control script now available
>>
>>   >  I'm sure others will chime in (hint, hint...)
>> <-- Since allstarnode.com was designed to be a peer-to-peer
>> BB system for ALL flavors of AllStar builds, I can make
>> public FTP space available on there if it's needed/desired.
>>
>> Scott
>>
>> Scott Zimmerman
>> Amateur Radio Call N3XCC
>> 474 Barnett Road
>> Boswell, PA 15531
>>
>> On 1/30/2012 12:08 PM, Bryan D. Boyle wrote:
>>> On 1/30/12 11:50 AM, Jim Kehler wrote:
>>>> I'm new on the list as of last night. A couple of
>> questions. Where do
>>>> you hide the scripts? And is it OK to post links on the list?
>>> Welcome to the collective. We're a pentium borg. You will be
>>> approximated...;) Seriously, hop on and enjoy the ride.
>>>
>>> Hide as in where it is on your system, or where we're all
>> hiding the juicy stuff we've developed?
>>> The NJPAASTERISK group, of which I'm one of the operators, have
>>> standardized on a scripts directory in the /etc/asterisk hierarchy
>>> (well, most of us have anyway..) to make it easier to backup the
>>> configuration and shorten deployment cycle time. Others put
>> them in /etc or /usr/sbin or ??? Guess it goes where you feel
>> it should be. Just be consistent.
>>> That means that, when you write something, you're pretty
>> sure of where
>>> it should reside, and makes it easier to find 'stuff'
>> that's directly
>>> applicable to your operation. It also means that, if you
>> glom on to a
>>> script or app that someone else has written, you have to do
>> some editing to make it work (pretty much standard when using
>> others' works...) in your operation.
>>> As to the latter question...well, that topic came up
>> yesterday, with
>>> no resolution. I have a repository for my weather scripts that I
>>> hacked/wrote/modified at http://www.wb0yle.com/weather.htm,
>>> Kyle has some stuff on his site...I'm sure others will
>> chime in (hint,
>>> hint...) if they have anything they'd like to make public...
>>>
>>> And, I don't think there is any blanket prohibition against
>> posting links.
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>



More information about the App_rpt-users mailing list