On Sun, Jan 28, 2018 at 02:31:08PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Changing the subject line to get more people to see this.
>
[...]
>
> It took a while, but I think I found some code that should work (using
> AF_PACKET and
Changing the subject line to get more people to see this.
Max reports that on his linux system the kernel is putting warnings in the
syslog about xastir using deprecated arguments to a socket call. I looked into
it.
The issue was known to Chuck Byam in 2003, but he made a minor error in the
On Sun, Jan 28, 2018 at 02:39:39PM -0600, we recorded a bogon-computron
collision of the flavor, containing:
> On Sun, Jan 28, 2018 at 1:23 PM, Tom Russo wrote:
>
> > Actually, SOCK_PACKET is deprecated, too,
>
> dang kids, changing their APIs every 5
On Sun, Jan 28, 2018 at 1:23 PM, Tom Russo wrote:
> Actually, SOCK_PACKET is deprecated, too,
dang kids, changing their APIs every 5 minutes.
-Jason
kg4wsv
___
Xastir mailing list
Xastir@lists.xastir.org
On Sun, Jan 28, 2018 at 12:14:39PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
>
> I just experimented with fixing the preprocessor symbol so it actually
> detects we're running with a newer GLIBC, and it made Xastir AX.25 connections
> broken,
That's very odd. The only place where PF_INET and SOCK_PACKET are used in i
the code is in one place in interface.c where we're explicitly checking for
an old GLIBC version (prior to 2.3). Only if Xastir was compiled against
such an old glibc are we supposed to be using that combination.
Looking the the file /var/log/syslog, I noticed this...
'Jan 27 07:13:18 Igate kernel: [26779.439570] xastir uses obsolete
(PF_INET,SOCK_PACKET)'
I don't have a clue what it means or if I should even worry about it. Anyone
else see this?
I just did an install a week ago so it's the latest
I am now connecting to an IPv6 javAPRSSrvr by hostname as expected.
This is a great feature. I will leave it running for a bit to see if
there are any issues.
Thanks to Jason!
73
On Fri, 2018-01-26 at 21:34 -0700, Tom Russo wrote:
>
> I'll refrain from merging these fixes until I hear from