Compiling FBB

Compiling FBB

[f6bvp]

*Hello Miroslav,

It looks like you did not install AX.25 libraries (libax25) before 
installing FBB.
Look at the following link :

http://code.google.com/p/linuxax25/

73 de Bernard, f6bvp


List: linux-hams <http://marc.info/?l=linux-hams&r=1&w=4>
Subject: Compiling FBB
From: Miroslav Skoric <skoric () eunet ! rs> 
<http://marc.info/?a=128974130300001&r=1&w=4>
Date: 2011-10-02 15:41:02 <http://marc.info/?l=linux-hams&r=1&b=201110&w=4>
Message-ID: 4E88860E.3030908 () eunet ! rs 
<http://marc.info/?i=4E88860E.3030908%20%28%29%20eunet%20%21%20rs>
[Download message RAW 
<http://marc.info/?l=linux-hams&m=131758932830913&q=raw>]*

Re: Compiling FBB

[Miroslav Skoric]

On 10/11/2011 10:18 AM, f6bvp wrote:
> *Hello Miroslav,
>
> It looks like you did not install AX.25 libraries (libax25) before
> installing FBB.
> Look at the following link :
>
> http://code.google.com/p/linuxax25/
>
> 73 de Bernard, f6bvp
>

Hi Bernard,

I already had libax25 (as well as ax25-apps and ax25-tools) before 
trying to compile FBB. Btw, in respect to repositories of Ubuntu and 
Debian communities, I installed the version they both provided: libax25 
0.0.11-6.1)

However, I checked the link above, but not sure what their versions 
might help me in regard to the FBB compiling issue. In fact, I would 
like to keep the existing ax25 stuff, provided they bring basic 
functionality (for example, I managed to activate a few Linux nodes in 
Ubuntu and Debian, and now I am in the process of configuring them to 
interact with Win/BPQ32 nodes in the mixed Lin/Win dual-boot environment.)

What else could I eventually try to install/reinstall?

Misko, YT7MPB

Re: Compiling FBB

[Dave Platt]

> I already had libax25 (as well as ax25-apps and ax25-tools) before
> trying to compile FBB. Btw, in respect to repositories of Ubuntu and
> Debian communities, I installed the version they both provided: libax25
> 0.0.11-6.1)

Debian and Ubuntu (and I suspect most other Linux distros) split these
and most libraries into two parts:  the runtime portion, and the
development portion.

You need to have both installed, in order to compile and build
anything which uses the library.  You only need the runtime portion
to run programs that someone else has built.

On Debian, for example, the "libax25" package has the runtime,
and "libax25-dev" has the development portions.

Re: Compiling FBB

[Bernard, f6bvp]

Hello Miroslav,

I now understand the libax25 issue.
Debian and alike libax25 packages are installing AX.25 libraries into 
/usr/lib/ whereas by default xfbb link process is expecting libax25.* in 
/usr/local/lib directory.

You will certainly know how to edit Makefile in order to tell it where 
to find the libraries.

I must say that for many reasons I do prefere to get all hamradio 
applications and libraries in /usr/local subdirectories.
This is more convenient for backups and file search.

Last remark : there have been some updates and bug removals in the 
"unofficial" libax25, tools and apps that I gave you as compared to the 
"old one" you are using (libax25 > 0.0.11-6.1).

This is the result of an intensive work performed by Lee VE7FET with 
FPAC development team. The site I gave you the address has Debian / 
Ubuntu compatible packages. You should consider using them. This will 
not break anything in your application but rather remove some failure 
causes.


73 de Bernard, f6bvp



Le 15/10/2011 00:10, Miroslav Skoric a écrit :
> On 10/11/2011 10:18 AM, f6bvp wrote:
>> *Hello Miroslav,
>>
>> It looks like you did not install AX.25 libraries (libax25) before
>> installing FBB.
>> Look at the following link :
>>
>> http://code.google.com/p/linuxax25/
>>
>> 73 de Bernard, f6bvp
>>
>
> Hi Bernard,
>
> I already had libax25 (as well as ax25-apps and ax25-tools) before
> trying to compile FBB. Btw, in respect to repositories of Ubuntu and
> Debian communities, I installed the version they both provided: libax25
> 0.0.11-6.1)
>
> However, I checked the link above, but not sure what their versions
> might help me in regard to the FBB compiling issue. In fact, I would
> like to keep the existing ax25 stuff, provided they bring basic
> functionality (for example, I managed to activate a few Linux nodes in
> Ubuntu and Debian, and now I am in the process of configuring them to
> interact with Win/BPQ32 nodes in the mixed Lin/Win dual-boot environment.)
>
> What else could I eventually try to install/reinstall?
>
> Misko, YT7MPB
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling FBB

[Marc Coevoet]

Op 15-10-11 09:55, Bernard, f6bvp schreef:
> Hello Miroslav,
>
> I now understand the libax25 issue.
> Debian and alike libax25 packages are installing AX.25 libraries into 
> /usr/lib/ whereas by default xfbb link process is expecting libax25.* 
> in /usr/local/lib directory.
>

No, the link libs are known when compiled (even when different distros 
use different hierarchies).  Everything can be configured in an option 
of "configure".


see here for some options: (you can build for ARM(tablets) eg in the 
/usr/armlib etc)

sh configure -help
`configure' configures this package to adapt to many kinds of systems.

Usage: configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE.  See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
   -h, --help              display this help and exit
       --help=short        display options specific to this package
       --help=recursive    display the short help of all the included 
packages
   -V, --version           display version information and exit
   -q, --quiet, --silent   do not print `checking ...' messages
       --cache-file=FILE   cache test results in FILE [disabled]
   -C, --config-cache      alias for `--cache-file=config.cache'
   -n, --no-create         do not create output files
       --srcdir=DIR        find the sources in DIR [configure dir or `..']

Installation directories:
   --prefix=PREFIX         install architecture-independent files in PREFIX
                           [/usr/local]
   --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                           [PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc.  You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
   --bindir=DIR            user executables [EPREFIX/bin]
   --sbindir=DIR           system admin executables [EPREFIX/sbin]
   --libexecdir=DIR        program executables [EPREFIX/libexec]
   --sysconfdir=DIR        read-only single-machine data [PREFIX/etc]
   --sharedstatedir=DIR    modifiable architecture-independent data 
[PREFIX/com]
   --localstatedir=DIR     modifiable single-machine data [PREFIX/var]
   --libdir=DIR            object code libraries [EPREFIX/lib]
   --includedir=DIR        C header files [PREFIX/include]
   --oldincludedir=DIR     C header files for non-gcc [/usr/include]
   --datarootdir=DIR       read-only arch.-independent data root 
[PREFIX/share]
   --datadir=DIR           read-only architecture-independent data 
[DATAROOTDIR]
   --infodir=DIR           info documentation [DATAROOTDIR/info]
   --localedir=DIR         locale-dependent data [DATAROOTDIR/locale]
   --mandir=DIR            man documentation [DATAROOTDIR/man]
   --docdir=DIR            documentation root [DATAROOTDIR/doc/PACKAGE]
   --htmldir=DIR           html documentation [DOCDIR]
   --dvidir=DIR            dvi documentation [DOCDIR]
   --pdfdir=DIR            pdf documentation [DOCDIR]
   --psdir=DIR             ps documentation [DOCDIR]

Program names:
   --program-prefix=PREFIX            prepend PREFIX to installed 
program names
   --program-suffix=SUFFIX            append SUFFIX to installed program 
names
   --program-transform-name=PROGRAM   run sed PROGRAM on installed 
program names

System types:
   --build=BUILD     configure for building on BUILD [guessed]
   --host=HOST       cross-compile to build programs to run on HOST [BUILD]

Optional Features:
   --disable-option-checking  ignore unrecognized --enable/--with options
   --disable-FEATURE       do not include FEATURE (same as 
--enable-FEATURE=no)
   --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
   --enable-maintainer-mode  enable make rules and dependencies not useful
                           (and sometimes confusing) to the casual installer
   --disable-dependency-tracking  speeds up one-time build
   --enable-dependency-tracking   do not reject slow dependency extractors
   --disable-nls           do not use Native Language Support
   --enable-threads={posix|solaris|pth|win32}
                           specify multithreading API
   --disable-threads       build without multithread safety
   --disable-rpath         do not hardcode runtime library paths
--disable-osmupload  Disable code to do osm uploads
   --disable-gtktest       do not try to compile and run a test GTK+ program
   --disable-gtktest       Do not try to compile and run a test GTK program

Optional Packages:
   --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
   --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
   --with-gnu-ld           assume the C compiler uses GNU ld default=no
   --with-libpth-prefix[=DIR]  search for libpth in DIR/include and DIR/lib
   --without-libpth-prefix     don't search for libpth in includedir and 
libdir
   --with-libiconv-prefix[=DIR]  search for libiconv in DIR/include and 
DIR/lib
   --without-libiconv-prefix     don't search for libiconv in includedir 
and libdir
   --with-included-gettext use the GNU gettext library included here
   --with-libintl-prefix[=DIR]  search for libintl in DIR/include and 
DIR/lib
   --without-libintl-prefix     don't search for libintl in includedir 
and libdir
--with-oldgtk  Use gtk1.x
   --with-gtk-prefix=PFX   Prefix where GTK is installed (optional)
   --with-gtk-exec-prefix=PFX Exec prefix where GTK is installed (optional)

Some influential environment variables:
   CC          C compiler command
   CFLAGS      C compiler flags
   LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
               nonstandard directory <lib dir>
   LIBS        libraries to pass to the linker, e.g. -l<library>
   CPPFLAGS    (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
               you have headers in a nonstandard directory <include dir>
   CPP         C preprocessor
   YACC        The `Yet Another C Compiler' implementation to use. 
Defaults to
               the first program found out of: `bison -y', `byacc', `yacc'.
   YFLAGS      The list of arguments that will be passed by default to 
$YACC.
               This script will default YFLAGS to the empty string to 
avoid a
               default value of `-d' given by some make applications.
   PKG_CONFIG  path to pkg-config utility
   PKG_CONFIG_PATH
               directories to add to pkg-config's search path
   PKG_CONFIG_LIBDIR
               path overriding pkg-config's built-in search path
   LIBXML2_CFLAGS
               C compiler flags for LIBXML2, overriding pkg-config
   LIBXML2_LIBS
               linker flags for LIBXML2, overriding pkg-config
   LIBCURL_CFLAGS
               C compiler flags for LIBCURL, overriding pkg-config
   LIBCURL_LIBS
               linker flags for LIBCURL, overriding pkg-config

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.


Marc

-- 
The "Penguin" has arrived - and he's not going away - ever.
What's on Shortwave guide: choose an hour, go!
http://shortwave.tk
700+ Radio Stations on SW http://swstations.tk
300+ languages on SW http://radiolanguages.tk

Re: Compiling FBB

[Bernard, f6bvp]

Hello Marc,

Yes I know that ./configure options allow choosing directories for 
compile, install, libs etc..
That is why I was talking about default libax25 install options.
In that case, the sequence "./configure, make make install" used by 
general users, leads to an install of most applications into /usr/local/...
I was deploring that this was not the default Debian (Ubuntu) choice for 
AX.25.

73 de Bernard, f6bvp


Le 15/10/2011 12:00, Marc Coevoet a écrit :
> Op 15-10-11 09:55, Bernard, f6bvp schreef:
>> Hello Miroslav,
>>
>> I now understand the libax25 issue.
>> Debian and alike libax25 packages are installing AX.25 libraries into
>> /usr/lib/ whereas by default xfbb link process is expecting libax25.*
>> in /usr/local/lib directory.
>>
>
> No, the link libs are known when compiled (even when different distros
> use different hierarchies). Everything can be configured in an option of
> "configure".
>
>
> see here for some options: (you can build for ARM(tablets) eg in the
> /usr/armlib etc)
>
> sh configure -help
> `configure' configures this package to adapt to many kinds of systems.
>
> Usage: configure [OPTION]... [VAR=VALUE]...
>
> To assign environment variables (e.g., CC, CFLAGS...), specify them as
> VAR=VALUE. See below for descriptions of some of the useful variables.
>
> Defaults for the options are specified in brackets.
>
> Configuration:
> -h, --help display this help and exit
> --help=short display options specific to this package
> --help=recursive display the short help of all the included packages
> -V, --version display version information and exit
> -q, --quiet, --silent do not print `checking ...' messages
> --cache-file=FILE cache test results in FILE [disabled]
> -C, --config-cache alias for `--cache-file=config.cache'
> -n, --no-create do not create output files
> --srcdir=DIR find the sources in DIR [configure dir or `..']
>
> Installation directories:
> --prefix=PREFIX install architecture-independent files in PREFIX
> [/usr/local]
> --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
> [PREFIX]
>
> By default, `make install' will install all the files in
> `/usr/local/bin', `/usr/local/lib' etc. You can specify
> an installation prefix other than `/usr/local' using `--prefix',
> for instance `--prefix=$HOME'.
>
> For better control, use the options below.
>
> Fine tuning of the installation directories:
> --bindir=DIR user executables [EPREFIX/bin]
> --sbindir=DIR system admin executables [EPREFIX/sbin]
> --libexecdir=DIR program executables [EPREFIX/libexec]
> --sysconfdir=DIR read-only single-machine data [PREFIX/etc]
> --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
> --localstatedir=DIR modifiable single-machine data [PREFIX/var]
> --libdir=DIR object code libraries [EPREFIX/lib]
> --includedir=DIR C header files [PREFIX/include]
> --oldincludedir=DIR C header files for non-gcc [/usr/include]
> --datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
> --datadir=DIR read-only architecture-independent data [DATAROOTDIR]
> --infodir=DIR info documentation [DATAROOTDIR/info]
> --localedir=DIR locale-dependent data [DATAROOTDIR/locale]
> --mandir=DIR man documentation [DATAROOTDIR/man]
> --docdir=DIR documentation root [DATAROOTDIR/doc/PACKAGE]
> --htmldir=DIR html documentation [DOCDIR]
> --dvidir=DIR dvi documentation [DOCDIR]
> --pdfdir=DIR pdf documentation [DOCDIR]
> --psdir=DIR ps documentation [DOCDIR]
>
> Program names:
> --program-prefix=PREFIX prepend PREFIX to installed program names
> --program-suffix=SUFFIX append SUFFIX to installed program names
> --program-transform-name=PROGRAM run sed PROGRAM on installed program names
>
> System types:
> --build=BUILD configure for building on BUILD [guessed]
> --host=HOST cross-compile to build programs to run on HOST [BUILD]
>
> Optional Features:
> --disable-option-checking ignore unrecognized --enable/--with options
> --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
> --enable-FEATURE[=ARG] include FEATURE [ARG=yes]
> --enable-maintainer-mode enable make rules and dependencies not useful
> (and sometimes confusing) to the casual installer
> --disable-dependency-tracking speeds up one-time build
> --enable-dependency-tracking do not reject slow dependency extractors
> --disable-nls do not use Native Language Support
> --enable-threads={posix|solaris|pth|win32}
> specify multithreading API
> --disable-threads build without multithread safety
> --disable-rpath do not hardcode runtime library paths
> --disable-osmupload Disable code to do osm uploads
> --disable-gtktest do not try to compile and run a test GTK+ program
> --disable-gtktest Do not try to compile and run a test GTK program
>
> Optional Packages:
> --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
> --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
> --with-gnu-ld assume the C compiler uses GNU ld default=no
> --with-libpth-prefix[=DIR] search for libpth in DIR/include and DIR/lib
> --without-libpth-prefix don't search for libpth in includedir and libdir
> --with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib
> --without-libiconv-prefix don't search for libiconv in includedir and
> libdir
> --with-included-gettext use the GNU gettext library included here
> --with-libintl-prefix[=DIR] search for libintl in DIR/include and DIR/lib
> --without-libintl-prefix don't search for libintl in includedir and libdir
> --with-oldgtk Use gtk1.x
> --with-gtk-prefix=PFX Prefix where GTK is installed (optional)
> --with-gtk-exec-prefix=PFX Exec prefix where GTK is installed (optional)
>
> Some influential environment variables:
> CC C compiler command
> CFLAGS C compiler flags
> LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
> nonstandard directory <lib dir>
> LIBS libraries to pass to the linker, e.g. -l<library>
> CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
> you have headers in a nonstandard directory <include dir>
> CPP C preprocessor
> YACC The `Yet Another C Compiler' implementation to use. Defaults to
> the first program found out of: `bison -y', `byacc', `yacc'.
> YFLAGS The list of arguments that will be passed by default to $YACC.
> This script will default YFLAGS to the empty string to avoid a
> default value of `-d' given by some make applications.
> PKG_CONFIG path to pkg-config utility
> PKG_CONFIG_PATH
> directories to add to pkg-config's search path
> PKG_CONFIG_LIBDIR
> path overriding pkg-config's built-in search path
> LIBXML2_CFLAGS
> C compiler flags for LIBXML2, overriding pkg-config
> LIBXML2_LIBS
> linker flags for LIBXML2, overriding pkg-config
> LIBCURL_CFLAGS
> C compiler flags for LIBCURL, overriding pkg-config
> LIBCURL_LIBS
> linker flags for LIBCURL, overriding pkg-config
>
> Use these variables to override the choices made by `configure' or to help
> it to find libraries and programs with nonstandard names/locations.
>
>
> Marc
>
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RS232-USB conversion (was: Compiling FBB)

[Miroslav Skoric]

On 10/15/2011 12:00 PM, Marc Coevoet wrote:
> Op 15-10-11 09:55, Bernard, f6bvp schreef:
>> Hello Miroslav,
>>
>> I now understand the libax25 issue.
>> Debian and alike libax25 packages are installing AX.25 libraries into
>> /usr/lib/ whereas by default xfbb link process is expecting libax25.*
>> in /usr/local/lib directory.
>>
>
> No, the link libs are known when compiled (even when different distros
> use different hierarchies). Everything can be configured in an option of
> "configure".
>

OK guys, thank you all for your advices ...will see about compiling FBB 
when I return from a conference trip. Btw, after a long time of 
avoiding to purchase a laptop/notebook comp (and still living well 
without a cellphone :-)), I have been thinking about an inexpensive 
portable comp that could run not only PPT (or similarly formatted) 
scientific presentations, but also to give me an opportunity to run my 
TNC2S (an old German-made TNC), which connects over RS232. I do not know 
if some of you have experience with some of those adapters that convert 
an USB output of a laptop to a RS232 connector of a TNC. I heard that 
some adapters (if not all) come with a kind of software that makes them 
thinking that the computer still has COM1, COM2, etc, but I don't know 
if such software works only in M$ world or/and in Linux too. (In the 
other words, I would like to have a relatively modern machine, but to 
avoid buying an expensive one that is still equipped with RS232.)

Opinions?

Misko

Re: RS232-USB conversion (was: Compiling FBB)

[Gordon JC Pearce]

On Tue, 18 Oct 2011 22:07:07 +0200
Miroslav Skoric <skoric@eunet.rs> wrote:

> thinking that the computer still has COM1, COM2, etc, but I don't know 
> if such software works only in M$ world or/and in Linux too. (In the 
> other words, I would like to have a relatively modern machine, but to 
> avoid buying an expensive one that is still equipped with RS232.)

If you use a USB-to-serial adaptor, it will appear as something like /dev/ttyUSB0 in Linux.  In Windows it's a bit hit-or-miss.

-- 
Gordon JC Pearce MM0YEQ <gordonjcp@gjcp.net>

Re: RS232-USB conversion

[Dave Platt]

> If you use a USB-to-serial adaptor, it will appear as something like /dev/ttyUSB0 in Linux.  In Windows it's a bit hit-or-miss.

Some USB-to-serial adapters (e.g. those from FTDI) come with
individual machine-readable serial numbers scribed into each
individual chip, which can be read out by the host software.

This can be a definite advantage in Linux (and perhaps in Windows
as well) because it's possible to arrange for each specific
physical USB-to-serial adapter, to be assigned the same
device name in /dev each time it is connected.  On modern
Linux distributions you can use the "udev" scripts to
assign a name-alias, if you wish... so, for example, the
adapter you have connected to your TNC might always
be /dev/ttyTNC0.

Without a unique ID in the chip, device-name assignment is much
more hit-or-miss.  If you have two or more such adapters connected,
they may change "names" each time you reboot... it'll depend on just
what order your USB hubs and devices are recognized ("enumerated")
at boot time.  On Linux they'll swap /dev names around, on Windows
they will have different "virtual serial port" COM names.

The Prolific CP2103 USB-to-serial adapter chips (quite popular)
don't generally have IDs in them... I believe this chip *can*
be used with an external (I2C or SPI) EEPROM chip that holds
an ID, but very few manufacturers use this feature.

Interesting note - FTDI now makes a USB-to-serial adapter
which is built into a shell that's the same size as a
DB-9 male or female PC-mount connector, and has the
same pinout.  If you have a device which has a DB-9 RS-232
connector mounted on its PC board, you can unsolder this,
solder in the corresponding FTDI adapter, and your device
now has a USB-serial connection rather than RS-232.

Unfortunately they don't seem to make these to fit the
older DB-25 connector standard.

Re: RS232-USB conversion

[Bruno Tréguier]

Le 18/10/2011 à 22:07, Miroslav Skoric a écrit :

> OK guys, thank you all for your advices ...will see about compiling FBB
> when I return from a conference trip. Btw, after a long time of avoiding
> to purchase a laptop/notebook comp (and still living well without a
> cellphone :-)), I have been thinking about an inexpensive portable comp
> that could run not only PPT (or similarly formatted) scientific
> presentations, but also to give me an opportunity to run my TNC2S (an
> old German-made TNC), which connects over RS232. I do not know if some
> of you have experience with some of those adapters that convert an USB
> output of a laptop to a RS232 connector of a TNC. I heard that some
> adapters (if not all) come with a kind of software that makes them
> thinking that the computer still has COM1, COM2, etc, but I don't know
> if such software works only in M$ world or/and in Linux too. (In the
> other words, I would like to have a relatively modern machine, but to
> avoid buying an expensive one that is still equipped with RS232.)
>
> Opinions?

Hi Miroslav,

I guess all those devices come at least with a Windows driver, but 
regarding Linux you shouldn't have any problem either, as most of the 
converters out there are based on FTDI or Prolific chipsets, which have 
been supported out-of-the-box by linux kernels for at least several 
years now. They usually are seen as /dev/ttyACMxx or /dev/ttyUSBxx 
respectively, and flow-control signals are also correctly dealt with.

However, I heard (or rather read) some people stating that though all 
devices seemed to work fine for rig-control purposes, they had problems 
when using Prolific-based converters for FSK, which weren't quick enough 
(the issue seemed to be driver-related). This information is quite old 
now, but if you want to avoid problems, you should probably favour 
FTDI-based converters if you intend to use them with your TNC.

Best regards,

Bruno - F8FIV
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling FBB

[David Ranch]

Hello Bernard, Ralf, Thomas,

I've been meaning to ask this question for a while now:  Do you know why 
the official version of the ax25 apps/libs/tools hasn't been updated in 
ages?  I've been slowly hacking up the legacy "released" versions to 
work around bugs I've found in my personal uses and I'm sure there are 
other issues I haven't hit.. yet:

nrattach.c - non-incrementing nr interfaces (netrom)
http://marc.info/?l=linux-hams&m=125646640011531&w=2

axipd/kiss.c - control byte non-zero when used for axudp tunnels
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606338


It seems that many of these issues are resolved in the official CVS but 
maybe other issues as you pointed out in that Google URL aren't.   It 
would be nice if we could at least get  the current CVS pushed out as 
say a new official version of 0.0.13 and be aligned across all three 
packages.   Even better, have this 0.0.13 version integrate the fixes in 
the Google repo too?

--David



Bernard, f6bvp wrote:
> Hello Miroslav,
>
> I now understand the libax25 issue.
> Debian and alike libax25 packages are installing AX.25 libraries into 
> /usr/lib/ whereas by default xfbb link process is expecting libax25.* 
> in /usr/local/lib directory.
>
> You will certainly know how to edit Makefile in order to tell it where 
> to find the libraries.
>
> I must say that for many reasons I do prefere to get all hamradio 
> applications and libraries in /usr/local subdirectories.
> This is more convenient for backups and file search.
>
> Last remark : there have been some updates and bug removals in the 
> "unofficial" libax25, tools and apps that I gave you as compared to 
> the "old one" you are using (libax25 > 0.0.11-6.1).
>
> This is the result of an intensive work performed by Lee VE7FET with 
> FPAC development team. The site I gave you the address has Debian / 
> Ubuntu compatible packages. You should consider using them. This will 
> not break anything in your application but rather remove some failure 
> causes.
>
>
> 73 de Bernard, f6bvp
>
>
>
> Le 15/10/2011 00:10, Miroslav Skoric a écrit :
>> On 10/11/2011 10:18 AM, f6bvp wrote:
>>> *Hello Miroslav,
>>>
>>> It looks like you did not install AX.25 libraries (libax25) before
>>> installing FBB.
>>> Look at the following link :
>>>
>>> http://code.google.com/p/linuxax25/
>>>
>>> 73 de Bernard, f6bvp
>>>
>>
>> Hi Bernard,
>>
>> I already had libax25 (as well as ax25-apps and ax25-tools) before
>> trying to compile FBB. Btw, in respect to repositories of Ubuntu and
>> Debian communities, I installed the version they both provided: libax25
>> 0.0.11-6.1)
>>
>> However, I checked the link above, but not sure what their versions
>> might help me in regard to the FBB compiling issue. In fact, I would
>> like to keep the existing ax25 stuff, provided they bring basic
>> functionality (for example, I managed to activate a few Linux nodes in
>> Ubuntu and Debian, and now I am in the process of configuring them to
>> interact with Win/BPQ32 nodes in the mixed Lin/Win dual-boot 
>> environment.)
>>
>> What else could I eventually try to install/reinstall?
>>
>> Misko, YT7MPB
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling FBB

[Bernard, f6bvp]

Hello Misko,

Lee Ve7et is the maintainer of "unofficial" AX.25 suite.
These AX.25 programs are constantly updated, as opposed to the certainly 
too slowly maintained "official" versions.

We are willing to repare all known bugs as soon as possible.

If you have personal solutions to known or unknown bugs, please let us 
know by sending patches to the linux-ham list with copies to Ralf DL5BE.

We will do our best to improve the AX.25 libraries and applications.

73 de Bernard, f6bvp

Le 21/10/2011 06:02, David Ranch a écrit :
>
> Hello Bernard, Ralf, Thomas,
>
> I've been meaning to ask this question for a while now: Do you know why
> the official version of the ax25 apps/libs/tools hasn't been updated in
> ages? I've been slowly hacking up the legacy "released" versions to work
> around bugs I've found in my personal uses and I'm sure there are other
> issues I haven't hit.. yet:
>
> nrattach.c - non-incrementing nr interfaces (netrom)
> http://marc.info/?l=linux-hams&m=125646640011531&w=2
>
> axipd/kiss.c - control byte non-zero when used for axudp tunnels
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606338
>
>
> It seems that many of these issues are resolved in the official CVS but
> maybe other issues as you pointed out in that Google URL aren't. It
> would be nice if we could at least get the current CVS pushed out as say
> a new official version of 0.0.13 and be aligned across all three
> packages. Even better, have this 0.0.13 version integrate the fixes in
> the Google repo too?
>
> --David
>
>
>
> Bernard, f6bvp wrote:
>> Hello Miroslav,
>>
>> I now understand the libax25 issue.
>> Debian and alike libax25 packages are installing AX.25 libraries into
>> /usr/lib/ whereas by default xfbb link process is expecting libax25.*
>> in /usr/local/lib directory.
>>
>> You will certainly know how to edit Makefile in order to tell it where
>> to find the libraries.
>>
>> I must say that for many reasons I do prefere to get all hamradio
>> applications and libraries in /usr/local subdirectories.
>> This is more convenient for backups and file search.
>>
>> Last remark : there have been some updates and bug removals in the
>> "unofficial" libax25, tools and apps that I gave you as compared to
>> the "old one" you are using (libax25 > 0.0.11-6.1).
>>
>> This is the result of an intensive work performed by Lee VE7FET with
>> FPAC development team. The site I gave you the address has Debian /
>> Ubuntu compatible packages. You should consider using them. This will
>> not break anything in your application but rather remove some failure
>> causes.
>>
>>
>> 73 de Bernard, f6bvp
>>
>>
>>
>> Le 15/10/2011 00:10, Miroslav Skoric a écrit :
>>> On 10/11/2011 10:18 AM, f6bvp wrote:
>>>> *Hello Miroslav,
>>>>
>>>> It looks like you did not install AX.25 libraries (libax25) before
>>>> installing FBB.
>>>> Look at the following link :
>>>>
>>>> http://code.google.com/p/linuxax25/
>>>>
>>>> 73 de Bernard, f6bvp
>>>>
>>>
>>> Hi Bernard,
>>>
>>> I already had libax25 (as well as ax25-apps and ax25-tools) before
>>> trying to compile FBB. Btw, in respect to repositories of Ubuntu and
>>> Debian communities, I installed the version they both provided: libax25
>>> 0.0.11-6.1)
>>>
>>> However, I checked the link above, but not sure what their versions
>>> might help me in regard to the FBB compiling issue. In fact, I would
>>> like to keep the existing ax25 stuff, provided they bring basic
>>> functionality (for example, I managed to activate a few Linux nodes in
>>> Ubuntu and Debian, and now I am in the process of configuring them to
>>> interact with Win/BPQ32 nodes in the mixed Lin/Win dual-boot
>>> environment.)
>>>
>>> What else could I eventually try to install/reinstall?
>>>
>>> Misko, YT7MPB
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling FBB

[Lee Woldanski]

As Bernard has eluded to, I am maintaining my own copies of the
official AX.25 suite at http://linuxax25.googlecode.com.

This is a personal project so that I can package up the source for
easier deployment to my embedded systems. If someone else finds it
useful, that's great.

I have taken the CVS source from http://www.linux-ax25.org and
re-organized it a bit, and integrated it with Autotools. It makes it
easier to build and maintain, in my opinion.

I have used the CVS source as my code base, since there are a number
of bug fixes in there that are not present in the current released
version.

I would like all patches and bug fixes to be sent to the official
maintainers, as I pull my changes from there. That said, I wouldn't
mind a heads up on any submitted patches, so I can keep an eye open
for them when they are accepted (since I manually check for diffs
periodically).


Cheers!

Lee
VE7FET


On Fri, Oct 21, 2011 at 3:15 AM, Bernard, f6bvp <f6bvp@free.fr> wrote:
> Hello Misko,
>
> Lee Ve7fet is the maintainer of "unofficial" AX.25 suite.
> These AX.25 programs are constantly updated, as opposed to the certainly too
> slowly maintained "official" versions.
>
> We are willing to repare all known bugs as soon as possible.
>
> If you have personal solutions to known or unknown bugs, please let us know
> by sending patches to the linux-ham list with copies to Ralf DL5BE.
>
> We will do our best to improve the AX.25 libraries and applications.
>
> 73 de Bernard, f6bvp
>
> Le 21/10/2011 06:02, David Ranch a écrit :
>>
>> Hello Bernard, Ralf, Thomas,
>>
>> I've been meaning to ask this question for a while now: Do you know why
>> the official version of the ax25 apps/libs/tools hasn't been updated in
>> ages? I've been slowly hacking up the legacy "released" versions to work
>> around bugs I've found in my personal uses and I'm sure there are other
>> issues I haven't hit.. yet:
>>
>> nrattach.c - non-incrementing nr interfaces (netrom)
>> http://marc.info/?l=linux-hams&m=125646640011531&w=2
>>
>> axipd/kiss.c - control byte non-zero when used for axudp tunnels
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606338
>>
>>
>> It seems that many of these issues are resolved in the official CVS but
>> maybe other issues as you pointed out in that Google URL aren't. It
>> would be nice if we could at least get the current CVS pushed out as say
>> a new official version of 0.0.13 and be aligned across all three
>> packages. Even better, have this 0.0.13 version integrate the fixes in
>> the Google repo too?
>>
>> --David
>>
>>
>>
>> Bernard, f6bvp wrote:
>>>
>>> Hello Miroslav,
>>>
>>> I now understand the libax25 issue.
>>> Debian and alike libax25 packages are installing AX.25 libraries into
>>> /usr/lib/ whereas by default xfbb link process is expecting libax25.*
>>> in /usr/local/lib directory.
>>>
>>> You will certainly know how to edit Makefile in order to tell it where
>>> to find the libraries.
>>>
>>> I must say that for many reasons I do prefere to get all hamradio
>>> applications and libraries in /usr/local subdirectories.
>>> This is more convenient for backups and file search.
>>>
>>> Last remark : there have been some updates and bug removals in the
>>> "unofficial" libax25, tools and apps that I gave you as compared to
>>> the "old one" you are using (libax25 > 0.0.11-6.1).
>>>
>>> This is the result of an intensive work performed by Lee VE7FET with
>>> FPAC development team. The site I gave you the address has Debian /
>>> Ubuntu compatible packages. You should consider using them. This will
>>> not break anything in your application but rather remove some failure
>>> causes.
>>>
>>>
>>> 73 de Bernard, f6bvp
>>>
>>>
>>>
>>> Le 15/10/2011 00:10, Miroslav Skoric a écrit :
>>>>
>>>> On 10/11/2011 10:18 AM, f6bvp wrote:
>>>>>
>>>>> *Hello Miroslav,
>>>>>
>>>>> It looks like you did not install AX.25 libraries (libax25) before
>>>>> installing FBB.
>>>>> Look at the following link :
>>>>>
>>>>> http://code.google.com/p/linuxax25/
>>>>>
>>>>> 73 de Bernard, f6bvp
>>>>>
>>>>
>>>> Hi Bernard,
>>>>
>>>> I already had libax25 (as well as ax25-apps and ax25-tools) before
>>>> trying to compile FBB. Btw, in respect to repositories of Ubuntu and
>>>> Debian communities, I installed the version they both provided: libax25
>>>> 0.0.11-6.1)
>>>>
>>>> However, I checked the link above, but not sure what their versions
>>>> might help me in regard to the FBB compiling issue. In fact, I would
>>>> like to keep the existing ax25 stuff, provided they bring basic
>>>> functionality (for example, I managed to activate a few Linux nodes in
>>>> Ubuntu and Debian, and now I am in the process of configuring them to
>>>> interact with Win/BPQ32 nodes in the mixed Lin/Win dual-boot
>>>> environment.)
>>>>
>>>> What else could I eventually try to install/reinstall?
>>>>
>>>> Misko, YT7MPB
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>



-- 
Lee Woldanski, AScT
VE7FET
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling FBB

[Thomas Osterried]

Hello,

On 2011-10-20 21:02:44 -0700, David Ranch <linux-hams@trinnet.net>
wrote in <4EA0EEE4.7050502@trinnet.net>:
> 
> Hello Bernard, Ralf, Thomas,
> 
> I've been meaning to ask this question for a while now:  Do you know
> why the official version of the ax25 apps/libs/tools hasn't been
> updated in ages?

Unfortunately, there's no debian-developer who regulary builds new
packages from the CVS head of ax25-apps, -tools and libax25.

> I've been slowly hacking up the legacy "released"
> versions to work around bugs I've found in my personal uses and I'm
> sure there are other issues I haven't hit.. yet:

We're trying to fix bugs we're aware of.

> nrattach.c - non-incrementing nr interfaces (netrom)
> http://marc.info/?l=linux-hams&m=125646640011531&w=2

http://www.linux-ax25.org/cvsweb/ax25-tools/netrom/nrattach.c.diff?r1=1.3;r2=1.4;f=h

I was guilty. I have fixed it 2009/11/02.
> 
> axipd/kiss.c - control byte non-zero when used for axudp tunnels
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606338

It has been a long thread.

We rejected the patch because it leads kiss-commands to be converted
to normal data packets.

If there really come data packets with the wrong kiss header (i.E.
slottime+DATA), the software (or kernel-driver) which sends false data
has to be fixed.

> It seems that many of these issues are resolved in the official CVS
> but maybe other issues as you pointed out in that Google URL aren't.

Again: We're trying to fix bugs get aware of.

> It would be nice if we could at least get  the current CVS pushed
> out as say a new official version of 0.0.13 and be aligned across
> all three packages.   Even better, have this 0.0.13 version
> integrate the fixes in the Google repo too?

What google repo?

The ax25-apps, -tools and libax25 are homed at linux-ax25.org.

vy 73,
	- Thomas  dl9sau

Re: Compiling FBB

[Patrick Ouellette]

On Fri, Oct 21, 2011 at 02:04:00PM +0200, Thomas Osterried wrote:
> 
> On 2011-10-20 21:02:44 -0700, David Ranch <linux-hams@trinnet.net>
> wrote in <4EA0EEE4.7050502@trinnet.net>:
> > 
> > Hello Bernard, Ralf, Thomas,
> > 
> > I've been meaning to ask this question for a while now:  Do you know
> > why the official version of the ax25 apps/libs/tools hasn't been
> > updated in ages?
> 
> Unfortunately, there's no debian-developer who regulary builds new
> packages from the CVS head of ax25-apps, -tools and libax25.

I used maintain ax25 for Debian to a long time ago.  Apparently I will be 
picking up support in Debian again since no one else seems to want to and the
"team maintainer" concept has fallen apart.  

The first order of business I have to attend to is the apparent need to rename
the node package and binary to ax25-node.

www.linux-ax25.org is apparently down right now?

(the Google repo mentioned is: http://code.google.com/p/linuxax25/ )

73,

Pat
-- 

Patrick Ouellette                 pat@flying-gecko.net
ne4po (at) arrl (dot) net         Amateur Radio: NE4PO 

What kind of change have you been in the world today?

Re: Compiling FBB

[Thomas Osterried]

Am Dienstag, den 08. November 2011 um 21:05:24 Uhr, schrieb Patrick Ouellette <pouelle@debian.org> in <20111108200524.GE30829@flying-gecko.net>:
> On Fri, Oct 21, 2011 at 02:04:00PM +0200, Thomas Osterried wrote:
> > 
> > On 2011-10-20 21:02:44 -0700, David Ranch <linux-hams@trinnet.net>
> > wrote in <4EA0EEE4.7050502@trinnet.net>:
> > > 
> > > Hello Bernard, Ralf, Thomas,
> > > 
> > > I've been meaning to ask this question for a while now:  Do you know
> > > why the official version of the ax25 apps/libs/tools hasn't been
> > > updated in ages?
> > 
> > Unfortunately, there's no debian-developer who regulary builds new
> > packages from the CVS head of ax25-apps, -tools and libax25.
> 
> I used maintain ax25 for Debian to a long time ago.  Apparently I will be 
> picking up support in Debian again since no one else seems to want to and the
> "team maintainer" concept has fallen apart.  
> 
> The first order of business I have to attend to is the apparent need to rename
> the node package and binary to ax25-node.
> 
> www.linux-ax25.org is apparently down right now?

yes, it's currently under maintainance:

** PROBLEM Service Alert: linux-ax25/FTP is CRITICAL **
Von: 
root@mail-smt.osterried.it
  An: 
thomas@x-berg.in-berlin.de
  Datum: 
Tue Nov  8 21:00:04 2011
   
***** Nagios *****

Notification Type: PROBLEM

Service: FTP
Host: linux-ax25
Address: 81.2.74.12
State: CRITICAL

Date/Time: Tue Nov 8 21:00:04 CET 2011

Additional Info:

Connection refused

> 
> (the Google repo mentioned is: http://code.google.com/p/linuxax25/ )
> 
> 73,
> 
> Pat
> 

Re: Compiling FBB

[Ralf Baechle DL5RB]

On Tue, Nov 08, 2011 at 03:05:24PM -0500, Patrick Ouellette wrote:

> I used maintain ax25 for Debian to a long time ago.  Apparently I will be 
> picking up support in Debian again since no one else seems to want to and the
> "team maintainer" concept has fallen apart.  
> 
> The first order of business I have to attend to is the apparent need to rename
> the node package and binary to ax25-node.
> 
> www.linux-ax25.org is apparently down right now?

I'm upgrading the VM.  All services are running again but there might be
a few more brief outages to the ftp service while I'm doing nasty things
to systemd.

  Ralf

Re: Compiling FBB

[Bill Vodall]

>> > I've been meaning to ask this question for a while now:  Do you know
>> > why the official version of the ax25 apps/libs/tools hasn't been
>> > updated in ages?
>>
>> Unfortunately, there's no debian-developer who regulary builds new
>> packages from the CVS head of ax25-apps, -tools and libax25.
>
> I used maintain ax25 for Debian to a long time ago.  Apparently I will be
> picking up support in Debian again since no one else seems to want to and the
> "team maintainer" concept has fallen apart.


Does this have any relationship to the ax25-* packages in the Ubuntu
LTS releases?   I had a frustrating experience last week getting ax25
going again on a system and was wondering what could be done to make
it work out of the box for the next user.

Thanks,
Bill - WA7NWP
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling FBB

[Patrick Ouellette]

On Tue, Nov 08, 2011 at 01:39:39PM -0800, Bill Vodall wrote:
> 
> Does this have any relationship to the ax25-* packages in the Ubuntu
> LTS releases?   I had a frustrating experience last week getting ax25
> going again on a system and was wondering what could be done to make
> it work out of the box for the next user.
> 

If Ubuntu does not have their own version of the ax25-* packages 
(usually they have -ubuntu- in the package name), then yes it does.

Pat
-- 

Patrick Ouellette                 pat@flying-gecko.net
ne4po (at) arrl (dot) net         Amateur Radio: NE4PO 

What kind of change have you been in the world today?

Re: Compiling FBB

[David Ranch]

Hello Patrick,

Thanks for willing to take this back on!  One thing to regarding the 
node binary. The old "Linux Node" software evidently has several major 
security vulnerabilities in it that were resolved in a fork called 
Uronode.  See the Unode release nodes below for more details.

The HAM that wrote Uronode  has seemingly dropped of the map as all his 
domains no longer work, etc.  A different HAM (KD1ZD) has reposted that 
work as a new fork called Unode.   I would argue that the original Linux 
node software should be patched to be secure or better yet, be DROPPED 
from the ax25 suite in favor of this new Unode software which is "more" 
secure, has some additional features, etc.

    https://github.com/kd1zd/Unode

Just my $0.02

--David
KI6ZHD


Patrick Ouellette wrote:
> On Fri, Oct 21, 2011 at 02:04:00PM +0200, Thomas Osterried wrote:
>> On 2011-10-20 21:02:44 -0700, David Ranch <linux-hams@trinnet.net>
>> wrote in <4EA0EEE4.7050502@trinnet.net>:
>>> Hello Bernard, Ralf, Thomas,
>>>
>>> I've been meaning to ask this question for a while now:  Do you know
>>> why the official version of the ax25 apps/libs/tools hasn't been
>>> updated in ages?
>> Unfortunately, there's no debian-developer who regulary builds new
>> packages from the CVS head of ax25-apps, -tools and libax25.
> 
> I used maintain ax25 for Debian to a long time ago.  Apparently I will be 
> picking up support in Debian again since no one else seems to want to and the
> "team maintainer" concept has fallen apart.  
> 
> The first order of business I have to attend to is the apparent need to rename
> the node package and binary to ax25-node.
> 
> www.linux-ax25.org is apparently down right now?
> 
> (the Google repo mentioned is: http://code.google.com/p/linuxax25/ )
> 
> 73,
> 
> Pat

Re: Compiling FBB

[Marc Coevoet]

Op 09-11-11 02:22, David Ranch schreef:
> The old "Linux Node" software evidently has several major security 
> vulnerabilities in it 

Whoooh!  Security vulnerabilities.  What kind of?  What web site?


Marc

-- 
The "Penguin" has arrived - and he's not going away - ever.
What's on Shortwave guide: choose an hour, go!
http://shortwave.tk
700+ Radio Stations on SW http://swstations.tk
300+ languages on SW http://radiolanguages.tk

Re: Compiling FBB

[Thomas Osterried]

Am Mittwoch, den 09. November 2011 um 02:22:30 Uhr, schrieb David Ranch <linux-hams@trinnet.net> in <4EB9D5D6.50509@trinnet.net>:
> 
> Hello Patrick,
> 
> Thanks for willing to take this back on!  One thing to regarding the 
> node binary. The old "Linux Node" software evidently has several major 
> security vulnerabilities in it that were resolved in a fork called 
> Uronode.  See the Unode release nodes below for more details.
> 
> The HAM that wrote Uronode  has seemingly dropped of the map as all his 
> domains no longer work, etc.  A different HAM (KD1ZD) has reposted that 
> work as a new fork called Unode.   I would argue that the original Linux 
> node software should be patched to be secure or better yet, be DROPPED 
> from the ax25 suite in favor of this new Unode software which is "more" 
> secure, has some additional features, etc.

The software project Node is not part or ax25-apps/-tools.


>     https://github.com/kd1zd/Unode
> 
> Just my $0.02
> 
> --David
> KI6ZHD
> 
> 
> Patrick Ouellette wrote:
> > On Fri, Oct 21, 2011 at 02:04:00PM +0200, Thomas Osterried wrote:
> >> On 2011-10-20 21:02:44 -0700, David Ranch <linux-hams@trinnet.net>
> >> wrote in <4EA0EEE4.7050502@trinnet.net>:
> >>> Hello Bernard, Ralf, Thomas,
> >>>
> >>> I've been meaning to ask this question for a while now:  Do you know
> >>> why the official version of the ax25 apps/libs/tools hasn't been
> >>> updated in ages?
> >> Unfortunately, there's no debian-developer who regulary builds new
> >> packages from the CVS head of ax25-apps, -tools and libax25.
> > 
> > I used maintain ax25 for Debian to a long time ago.  Apparently I will be 
> > picking up support in Debian again since no one else seems to want to and the
> > "team maintainer" concept has fallen apart.  
> > 
> > The first order of business I have to attend to is the apparent need to rename
> > the node package and binary to ax25-node.
> > 
> > www.linux-ax25.org is apparently down right now?
> > 
> > (the Google repo mentioned is: http://code.google.com/p/linuxax25/ )
> > 
> > 73,
> > 
> > Pat
> 

Re: Compiling FBB

[Marco Di Martino (IW2OHX)]

Hi David,

thanks for the info.
I'm going to test unode at iw2ohx.ampr.org (telnet iw2ohx.ampr.org).
I searched for years a replacement of node. A part security issues, I had
problem with process node that sometimes eat a lot of CPU expecially 
when someone
doesn't close connection with "B" command. I hope this problem was fixed 
in Unode.

I appreciated flexd implementation, I teste it years ago with AWZNode.

I hope to post feedback here after configuring unode in my ham linux box.

Bye
Marco
iw2ohx

On 11/09/2011 02:22 AM, David Ranch wrote:
>
> Hello Patrick,
>
> Thanks for willing to take this back on!  One thing to regarding the 
> node binary. The old "Linux Node" software evidently has several major 
> security vulnerabilities in it that were resolved in a fork called 
> Uronode.  See the Unode release nodes below for more details.
>
> The HAM that wrote Uronode  has seemingly dropped of the map as all 
> his domains no longer work, etc.  A different HAM (KD1ZD) has reposted 
> that work as a new fork called Unode.   I would argue that the 
> original Linux node software should be patched to be secure or better 
> yet, be DROPPED from the ax25 suite in favor of this new Unode 
> software which is "more" secure, has some additional features, etc.
>
>    https://github.com/kd1zd/Unode
>
> Just my $0.02
>
> --David
> KI6ZHD
>
>
> Patrick Ouellette wrote:
>> On Fri, Oct 21, 2011 at 02:04:00PM +0200, Thomas Osterried wrote:
>>> On 2011-10-20 21:02:44 -0700, David Ranch <linux-hams@trinnet.net>
>>> wrote in <4EA0EEE4.7050502@trinnet.net>:
>>>> Hello Bernard, Ralf, Thomas,
>>>>
>>>> I've been meaning to ask this question for a while now:  Do you know
>>>> why the official version of the ax25 apps/libs/tools hasn't been
>>>> updated in ages?
>>> Unfortunately, there's no debian-developer who regulary builds new
>>> packages from the CVS head of ax25-apps, -tools and libax25.
>>
>> I used maintain ax25 for Debian to a long time ago.  Apparently I 
>> will be picking up support in Debian again since no one else seems to 
>> want to and the
>> "team maintainer" concept has fallen apart.
>> The first order of business I have to attend to is the apparent need 
>> to rename
>> the node package and binary to ax25-node.
>>
>> www.linux-ax25.org is apparently down right now?
>>
>> (the Google repo mentioned is: http://code.google.com/p/linuxax25/ )
>>
>> 73,
>>
>> Pat
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-- 
---
Marco Di Martino
Via Attimo, 18 - Bollate (MI)
Mobile: +393285373364
e-mail: iw2ohx@iw2ohx.net
-
Amateur Radio: I W 2 O H X
Homepage Inet: www.iw2ohx.net
Homepage Ampr: iw2ohx.ampr.org
LinuxNode: telnet://iw2ohx.ampr.org/
(X)net: telnet://iw2ohx-2.ampr.org/
Packet Mail : IW2OHX @ IW2OHX.ILOM.ITA.EU
Ampr Mail: iw2ohx@iw2ohx.ampr.org
---