Matti Aarnio a écrit :
> And recently people have observed kernel panics with ROSE traffic..
> Permanently avoiding using some machinery because it breaks for some
> users is not a good thing in my mind .. those broken things will never
> get fixed if we don't find them, and report them.
> /Matti Aarnio - OH2MQK
I agree with Matti.
Not reporting problems (that often mean bugs in the code) with AX25 or
ROSE or any application is the best mean to prevent any progress.
We are lucky with Linux to have an open source operating system and most
application programs are also open source.
So we must use this opportunity to help improving the code.
The result is that when a bug is identified and published there is much
chance that it will be corrected fast.
Where to report such problems ? Well, on a list, such as linux-hams.
Then, if it is really a bug, then the report will be directed to the
maintainer of the software and to a list of developers.
For example, I have been recently exchanging a lot of observations on
Linux netdev list that allowed, together with reports from others, to
correct bugs in AX25 code and ROSE.
The last corrected bug is actually only two days old. And it concerned
an important although probably very old bug in ROSE module.
This means that progress is still running on the bleeding edge of AX25
packet, that is in Linux kernel.
Doing that, we can get a much more stable Linux with AX25 applications.
Next kernel releases, 2.6.25 and 2.6.26 will certainly provide a major
step for AX25 support, as it will hopefully integrate those vital patches.
However this does not preclude to continue the adaptative work for AX25
libraries, tools and applications available for everybody.