Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: C Schuman <k4gbb1@embarqmail.com>
To: Patrick Ouellette <pat@flying-gecko.net>
Cc: Linux-Hams <linux-hams@vger.kernel.org>
Subject: Re: AX25 in /etc/init.d
Date: Fri, 01 May 2009 18:46:05 -0400	[thread overview]
Message-ID: <49FB7BAD.4000506@embarqmail.com> (raw)
In-Reply-To: <20090501214729.GA12084@flying-gecko.net>

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
>
>   
Pat,
 I setup, on the average of two Packet Radio Servers a month. Like you I 
started fiddling with the Startup script back in the days of Knoppix AR 4.?
The script I use evolved from the script generated by ax25config.  I 
couldn't use ax25config for the setup of my servers, but it served as a 
model.
It is prob as close as you can get to a one size fits all solution.

I have been working as a Beta Tester for some of Bernard Pidoux's 
(F6BVP) work on FBB BBS and FPAC.
He has also made contributions to the Kernel's source. As you say it has 
become "close enough for comfort".
That may change shortly. We are on the cusp of change between devfs and 
udev. It has been in the wind for four or five years.
Ubuntu 9.04 dropped the devfs from the compiled kernel. If you can't 
function with udev you have to recompile.

I've been pushing Linux for the HAM Radio population for almost ten 
years and I am beginning to see some progress.
Packet Radio is beginning to come back and Windows support is too 
painful to setup. It's like building a skyscraper to house your dog.

73
    <<Charley>>
         k4gbb

      parent reply	other threads:[~2009-05-01 22:46 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
2009-05-01 22:46       ` C Schuman [this message]

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=49FB7BAD.4000506@embarqmail.com \
    --to=k4gbb1@embarqmail.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=pat@flying-gecko.net \
    /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