Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: C Schuman <k4gbb1@embarqmail.com>
To: Ray Wells <vk2tv@exemail.com.au>
Cc: Patrick Ouellette <pat@flying-gecko.net>,
	Linux-Hams <linux-hams@vger.kernel.org>
Subject: Re: AX25 in /etc/init.d
Date: Fri, 01 May 2009 18:57:25 -0400	[thread overview]
Message-ID: <49FB7E55.8070902@embarqmail.com> (raw)
In-Reply-To: <49FB79DA.1080503@exemail.com.au>

Ray Wells wrote:
> Patrick Ouellette wrote:
>> On Fri, May 01, 2009 at 04:40:02PM -0400, C Schuman wrote:
>>  
>>>> FWIW, Debian includes a startup script in the ax25-tools package.  
>>>> It sets up
>>>> the mheardd, ax25d, and netromd.
>>>>
>>>> 73,
>>>>
>>>> Pat
>>>>         
>>> Thanks Pat,
>>> Yes, your assumption is correct.
>>>
>>> I use Ubuntu and Debian.  I have never seen any of the Debian 
>>> Startup  scripts for AX.25.
>>> The problem with with most of the supplied or example start scripts 
>>> is  that they never do what you want them to do.
>>> The Linux HAM Radio community are an assorted lot.  I have approx 
>>> 14  Packet Radio servers and no two are the same.
>>> I have been Elmering a number of individuals who are attempting 
>>> their  first installion of Linux. Some just want a RMS Gate.
>>> Others want a BBS, Node and an assortment of other apps.
>>>
>>> My point was not really "We need to add Header Info", but more 
>>> toward  the "We need a more versatile script"
>>> By pointing our start up script at /etc/ax25/ax25-up & down we can 
>>> use a  common script to transition to an uncommon system 
>>> initialization.
>>>
>>>     
>>
>> Well, I just checked, and the most recent ax25-tools does not install
>> the startup script.  There used to be one in the debian source package.
>>
>> Anyway, I agree in principle that ax25 should have startup scripts - BUT
>> as you point out, each system is different.  Several (> 7) years ago I
>> looked at creating comprehensive set up scripts for Debian's ax25 
>> packages
>> and decided there were just too many variables and not enough 
>> interest to
>> make it worth the time.  It was easier and faster to set up the boxes 
>> individually.
>>
>> The upstream ax25 package has *almost* not changed for a very long time.
>> Either it is completely debugged, there is not a bug that hits anyone's
>> "button," or there are not enough users to push for lots of activity 
>> there.
>> (I'm not saying it is unmaintained, but that there has been little 
>> change
>> in both the ax25 apps/tools and the kernel ax25 code for quite some 
>> time.)
>>
>> There is a wiki at www.linux-ax25.org and a few other efforts around.
>>
>> 73, 
>> Pat
>>
>>   
> I understand that fpac cannot be simply stopped and restarted, it 
> needs a reboot. If that is correct, is there any point in an ax25 
> script for stations who use fpac?
>
> Ray vk2tv
>
Ray,
 AX25, FPAC & FBB can all be restarted w/o rebooting.
It's all in the way you construct your stop shut process.
I'll send you a copy of my fpac.sh and my ax25-down.
I have a couple of systems that have uptimes of over 60 days even though 
I have made changes to the configuration and restarted the service.
Once in awhile ROSE will cause a kernel panic on the Stopping and the 
system will reboot on panic. This occurs mainly on the systems with a co 
located BBS.

73
    <<Charley>>
        k4gbb

  reply	other threads:[~2009-05-01 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01  3:42 AX25 in /etc/init.d C Schuman
2009-05-01 20:06 ` Patrick Ouellette
2009-05-01 20:40   ` C Schuman
2009-05-01 21:47     ` Patrick Ouellette
2009-05-01 22:38       ` Ray Wells
2009-05-01 22:57         ` C Schuman [this message]
2009-05-01 22:46       ` C Schuman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49FB7E55.8070902@embarqmail.com \
    --to=k4gbb1@embarqmail.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=pat@flying-gecko.net \
    --cc=vk2tv@exemail.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox