* Re: NO such version - ax25-apps 0.0.7 published..
2008-04-01 8:04 ` NO such version - " Thomas Osterried
2008-04-01 8:18 ` Ralf Baechle DL5RB
@ 2008-04-01 9:15 ` Matti Aarnio
2008-05-01 12:36 ` AA6QN
2 siblings, 0 replies; 5+ messages in thread
From: Matti Aarnio @ 2008-04-01 9:15 UTC (permalink / raw)
To: Thomas Osterried; +Cc: linux-hams
On Tue, Apr 01, 2008 at 10:04:10AM +0200, Thomas Osterried wrote:
> Hello,
>
> > libax25-0.0.13
> [...]
>
> Unfortunately, the numbering scheme Matti has choosen is confusing.
> This is, because there is no official version like libax25-0.0.13,
> libax25-0.0.12. The same is also right for ax25-apps or -tools.
As there is no mention at sf.net about development having been
moved elsewere, realizing that ax25 libs/tools/apps have not been
abandoned is not easy thing.
If you could be bothered to update the sf.net web about this move,
it would cut down a lot of the confusion.
> This raised some questions, because other people already use the cvs
> version (see below), and if they'd look at the here claimed "new version
> x.y.", they'd look on an old code base.
>
> libax25-0.0.11 (still downloadable from sf.net) is the latest offical
> relaseed version. ax25-tools is 0.0.8 and libax25 is 0.0.11.
>
> Actually i even do not know exactly what was promised to be changed in
> Matti's packages.
Probably because this is first time you notice them ?
Well, similarly on weekend I was considering taking over the
ax25.sourceforge.net and posted against any hope(*) an email
to you about it -- and for the first time heard of linux-ax25.org.
It really is not that well known.
*) "against any hope" = "that project appears to be abandoned, and
their emails probably will not work and/or they won't answer..."
It looks like you made similar changes to axconfig.c that I did
a few months ago -- except that I didn't make it conditional to some
future kernel fix, and I made similar (practically the same - as my
axconfig.c change) changes on nrconfig.c and on rsconfig.c
Also the new autoconfig machinery is basically same as what I did
independently. I had used a bit newer config.guess, but that is
probably just fine. I picked also newer depcomp and ltmain.sh,
the latter does matter a bit on development package library building.
> After that last official released version, we develloped in the cvs.
> Not at sf.net any more (for various reasons - one was, that it had months
> of trouble), but on linux-ax25.org.
>
> Personaly, i'm a bit disappointed. Nearly nobody sent any patch for fixes
> or features or did a feature request. Nobody asked when the release is
> expected, what is missing and how he could help (i.e. in building packages
> in their wide variety of formats, and for multible architectures. Or by
> managing a preview-release). Neither by developers, nor by the linux
> distributors, nor by users. Silence.
Like I said above, silently moving elsewere without marking it at
previous webs is an excellent way to appear to abandon the project.
(However crappy the sf.net was for a while.)
> On the other hand, i'll get the hope that the ax25 stuff gets a vivid
> revival (people still seem to be interested in).
>
> The CVS access is documented at linux-ax25.org:
> http://www.linux-ax25.org/wiki/CVS
>
> cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs login
> password is "cvs"
> cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co ax25-apps
> cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co ax25-tools
> cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co libax25
Not that your servers are all that excellent (at least yet)
[mea@mea libax25]$ cvs log axconfig.h
cvs [log aborted]: connect to [cvs.linux-ax25.org]:2401 failed: No route to host
It worked 15 minutes ago...
.. and 30 minutes latter it works again.
> After checkout, first do "sh bootstrap" in each directory; this generates
> the make files.
>
> And please do not forget to talk about, when you get into problems,
> a fix is missing, etc..
>
> Give Feedback ;)
Where ? At this list ?
> 73,
> - Thomas dl9sau
73 de Matti, OH2MQK
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: NO such version - ax25-apps 0.0.7 published..
2008-04-01 8:04 ` NO such version - " Thomas Osterried
2008-04-01 8:18 ` Ralf Baechle DL5RB
2008-04-01 9:15 ` Matti Aarnio
@ 2008-05-01 12:36 ` AA6QN
2 siblings, 0 replies; 5+ messages in thread
From: AA6QN @ 2008-05-01 12:36 UTC (permalink / raw)
To: linux-hams
Thomas Osterried wrote:
> Hello,
>
>> libax25-0.0.13
> [...]
>
Maybe that why I had some problems, stated below. With the updates I
lost my xfbb loopback port and could not load the dual port tnc using
mkiss. If there is something that I could read to make the transition
from the old school to the new, please direct me. I have been running
this software for many years now and have not done much in upgrades
other than to transition to the 2.6.25-r1 kernel. I must admit that it
is pretty solid running on a embedded Soekris SBC.
So, If someone is kind enough to point me to the correct documentation
that details the required configuration changes please drop a line.
73, JohnF
------------------
First, I wish to say thank you for all your hard work! I have been
running FBB for many years now and really like the software.
Recently, I have been met with a couple of challenges. When I upgraded
the libax25 to 13-6, I lost my FBB loopback interfaces. Guess I am old
school and during the ax25 startup I defined two loopback interfaces:
# /etc/conf.d/rc.ax25 Create Loopback ports
/usr/local/sbin/kissnetd /dev/ptya3 /dev/ptya4 &
sleep 2
/usr/local/sbin/kissattach -l -m 256 /dev/ttya3 ax3 44.8.0.112
/usr/local/sbin/kissattach -l -m 256 /dev/ttya4 ax4 44.8.0.112
route del -net 44.0.0.0/8 ax3
route del -net 44.0.0.0/8 ax4
# /etc/ax25/axports
# Name Callsign speed paclen window description
ax0 AA6QN-9 115200 256 7 AXIP Link
ax1 AA6QN-12 9600 256 1 1200 bps Port A
DE (pending)
ax2 AA6QN-11 9600 256 2 9600 bps Port B
DE 439.050 MHz
ax3 LOOP1 9600 256 4 Loopback 1
ax4 LOOP2 9600 256 4 Loopback 2
Then in /usr/local/etc/ax25/fbb/port.sys where-as ax4 is the loopback
#TNC NbCh Com MultCh Pacln Maxfr NbFwd MxBloc M/P-Fwd Mode Freq
0 0 0 0 0 0 0 0 00/01 ---- File-fwd.
1 4 1 ax1 250 1 2 10 10/60 XUWY pending
2 4 1 ax2 250 1 2 10 20/60 XUWY 439.050
3 4 1 ax0 250 2 2 10 30/30 XUWY ax0
4 4 1 ax4 250 4 2 10 30/60 XUWY ax4
5 2 1 netbbs 236 1 1 10 30/30 XUWY netrom
6 2 2 0 250 2 1 10 0/60 TUWY telnet
#
This all works great with libax25-0.0.11-4 but not libax25-0.0.13-6
What did I miss? is there a new way to link FBB to the AX25 resources?
I also tried to update to ax25-tools-0.0.9-3 but mkiss did not load my
dual port tnc stating it could not find the CALL. Same axport as above
with ax1 and ax2 being the dual ported tnc. ax25-tools-0.0.8.2 does work:
#/etc/conf.d/rc.ax25# Attach Dual TNC with MKISS COM2
/usr/local/sbin/mkiss -s 9600 /dev/ttyS1 /dev/ptya0 /dev/ptya1
sleep 2
/usr/local/sbin/kissattach -l -m 256 /dev/ttya0 ax1 44.8.0.112
/usr/local/sbin/kissattach -l -m 256 /dev/ttya1 ax2 44.8.0.112
route del -net 44.0.0.0/8 ax1
route del -net 44.0.0.0/8 ax2
kissparms -p ax1 -t 30 -s 100 -r 63
kissparms -p ax2 -t 10 -s 100 -r 63
Once again, did I miss some changes in the configuration? The install
notes were rather vague on syntax changes.
-----------
^ permalink raw reply [flat|nested] 5+ messages in thread