On Tue, 7 Dec 1999, Tomi Manninen wrote:
On Tue, 16 Nov 1999, Jorge Matias wrote:
I don't know if anyone of you has this problem, but I found that
everytime ax25d answers a call and spawns a connection to a service it
opens "ax25" module for use. The problem is that when the
On Tue, 7 Dec 1999, Richard Adams wrote:
I presume you have seen that 2.2.14pre12 is out and part of the patch is
incorperated, however only the first line has been deleted, is that correct.?
No, that was an oversight from Alan and he already promised to fix that.
2.2.14pre11 has been
On Wed, 08 Dec 1999, Tomi Manninen wrote about, Re: ax25d with probs in mem
cleaning!:
On Tue, 7 Dec 1999, Richard Adams wrote:
I presume you have seen that 2.2.14pre12 is out and part of the patch is
incorperated, however only the first line has been deleted, is that correct
On Tue, 16 Nov 1999, Jorge Matias wrote:
I don't know if anyone of you has this problem, but I found that
everytime ax25d answers a call and spawns a connection to a service it
opens "ax25" module for use. The problem is that when the connection is
closed we still have the "ax25" module
On Tue, 07 Dec 1999, you wrote:
I investigated this last week and was able to come up with a possible
solution to the problem, which seems to be an oversight in the kernel
code.
Would people please test the attached patch to linux/net/ax25/af_ax25.c
(even if you haven't noticed any
On Tue, 16 Nov 1999, Jorge Matias wrote:
I don't know if anyone of you has this problem, but I found that
everytime ax25d answers a call and spawns a connection to a service it
opens "ax25" module for use. The problem is that when the connection is
closed we still have the "ax25" module opened.
On Tue, 16 Nov 1999, Richard Adams wrote:
On Tue, 16 Nov 1999, Jorge Matias wrote:
I don't know if anyone of you has this problem, but I found that
everytime ax25d answers a call and spawns a connection to a service it
opens "ax25" module for use. The problem is that when the connection is
On Tue, 16 Nov 1999, Jorge Matias wrote:
I don't know if anyone of you has this problem, but I found that
everytime ax25d answers a call and spawns a connection to a service it
opens "ax25" module for use. The problem is that when the connection is
closed we still have the "ax25" module
