> Thanks to all those who replied to my plea for assistance. It turned out
> I hadn't included kiss support when configuring the kernel (I included
> radio network support but missed the kiss option).
>
> Would it be worth including a mention about this in the AX25 HOWTO?
Um, oops. Did I not include this ? I did before the rewrite, did I lose
it somehow ? It should have been in the 'compiling the kernel' section.
Could you do me a favour. Take a look at the new NET-3-HOWTO and tell
me if you'd prefer me to take a similar approach with the AX25-HOWTO.
It's quite difficult to determine what people actually need. I received
some feedback from the previous version of the AX25-HWOTO that people
were confused because it seemed illogical to have the kernel parameters
after the compiling the kernel section, so I moved them all back into
that section, and now you didn't spot them at all :) heh, I can't win :)
> On a different matter, when I was upgrading from 2.0.28 I added patches
> 2.0.29 and 2.0.30 and then tried adding the ax25-module. This produced 3
> errors which I must admit I didn't note down. I then tried again (having
> restored 2.0.28) this time patching to 2.0.29 then adding the
> ax25-module and then patch 2.0.30. This produced 2 errors (again not
> noted) after adding patch 2.0.30.
>
> Does this mean the ax25-modules have to be patched for each kernel
> revision?
It means that 2.0.30 made some changes inside the kernel that were
significant enough to break the module patch. This is unfortunate
but outside of Jonathons control. Jonathon has a new module that
is being alpha tested at the moment that looks like it will work
just fine with 2.0.30. So I suggest you stick with 2.0.29 for a little
while and then upgrade when the new module is announced shortly.
regards
Terry