Mailinglist Archive: opensuse-ham (15 mails)
| < Previous | Next > |
Re: [suse-ham-e] Installing and configuring AX25
- From: Hans-Peter Zorn <hpz@xxxxxxx>
- Date: Mon, 16 Oct 2000 10:27:25 +0000 (UTC)
- Message-id: <20001016122729.A756@xxxxxxxxxxxxxxx>
On Mon, Oct 16, 2000 at 11:49:44AM +0200, Joerg Reuter wrote:
> There is a start of a configuration script on
> http://www.1409.org/projects/ax25-config.html
> The problem is, however, that the script for the user interface
> also writes the startup script instead of just dumping the
> configuration variables to a file. I'd like to see a more
> flexible solution.
>
This is true, however the configuration is also dumped into
a configuration file /etc/ax25-config.conf which can be sourced
by a shell-script (using . /etc/ax25-config.conf). Actually once I
had a generic start/stop script which used this file. It is definitely
possible to write such a script without having to change ax25-config
itself.
Mirko favored the hardcoded up/down scripts because people can
tweak them if they have special needs.
The main problem with ax25-config is that it is written as shell
script which results in rather unreadable code. I would like
to rewrite it in python and give it (optionally) a graphical
interface. But currently a have no spare time to do so.
> > Please help me because I am ignorant in this case: How do you autodetect
> > a TNC connected to the serial port?
>
> It's tricky due to the great number of different firmware implementations
> and you have to take care not to accidently send UI frames while probing
> the hardware. Worse, there's one case you cannot detect: pure KISS TNCs.
>
par96, serial baycom, yam etc aren't easy to detect either. Even worse,
yam and flexepp can be programmed and I don't know if probing could
damage these devices.
> > My dream is to call YaST/2, install the hardware drivers and configure
> > them within one step and off you go. This would be really smooth!
>
> Indeed!
I would prefer a distribution independend approach. I is great that
SuSE is supporting ham radio in its distribution but I don't think
that _all_ hams will switch to SuSE (i am in love with debian, sorry
;) and as (ham-) developer resources are limited it would be better
to collaborate and to come up with a distibution independent solution.
-hp
--
Hans-Peter Zorn, Karlsruhe, Germany
http://www.stud.uni-karlsruhe.de/~uhsm/ hpz@xxxxxxx (preferred)
http://1409.org/people/hp/ hp@xxxxxxxx (hamradio stuff)
> There is a start of a configuration script on
> http://www.1409.org/projects/ax25-config.html
> The problem is, however, that the script for the user interface
> also writes the startup script instead of just dumping the
> configuration variables to a file. I'd like to see a more
> flexible solution.
>
This is true, however the configuration is also dumped into
a configuration file /etc/ax25-config.conf which can be sourced
by a shell-script (using . /etc/ax25-config.conf). Actually once I
had a generic start/stop script which used this file. It is definitely
possible to write such a script without having to change ax25-config
itself.
Mirko favored the hardcoded up/down scripts because people can
tweak them if they have special needs.
The main problem with ax25-config is that it is written as shell
script which results in rather unreadable code. I would like
to rewrite it in python and give it (optionally) a graphical
interface. But currently a have no spare time to do so.
> > Please help me because I am ignorant in this case: How do you autodetect
> > a TNC connected to the serial port?
>
> It's tricky due to the great number of different firmware implementations
> and you have to take care not to accidently send UI frames while probing
> the hardware. Worse, there's one case you cannot detect: pure KISS TNCs.
>
par96, serial baycom, yam etc aren't easy to detect either. Even worse,
yam and flexepp can be programmed and I don't know if probing could
damage these devices.
> > My dream is to call YaST/2, install the hardware drivers and configure
> > them within one step and off you go. This would be really smooth!
>
> Indeed!
I would prefer a distribution independend approach. I is great that
SuSE is supporting ham radio in its distribution but I don't think
that _all_ hams will switch to SuSE (i am in love with debian, sorry
;) and as (ham-) developer resources are limited it would be better
to collaborate and to come up with a distibution independent solution.
-hp
--
Hans-Peter Zorn, Karlsruhe, Germany
http://www.stud.uni-karlsruhe.de/~uhsm/ hpz@xxxxxxx (preferred)
http://1409.org/people/hp/ hp@xxxxxxxx (hamradio stuff)
| < Previous | Next > |