status of misdn again

[Simon Richter]

Hi,

Tzafrir Cohen wrote:

>> The word "sanely" is the crucial point here. We have module packages 
>> that compile on the autobuilders and a -source package that works with 
>> both make-kpkg and m-a (at least to my knowledge)

> However updating it and building it seem like a pain. Why bother
> patching the kernel if you have an external module anyway? If someone
> ever wants to adapt it to his personal kernel, he may have a rough time.

The patch is just an additional option that probably noone uses; "m-a 
build misdn" works fine and produces all the required binaries.

> Making chan_misdn in Asterisk work, mainly. There is now (recent 1.2 and
> 1.4) chan_misdn in Asterisk. I'm not sure how good it is, but people are
> reported to have used it and survived the exeprince.

Indeed, however kernel ABI changed again just a week ago, so compiling 
it as an external module is giving us the advantage of not having to 
synchronise asterisk uploads with mISDN.

chan_misdn as an external package is currently uninstallable as the 
asterisk config package brings a misdn.conf file.

> I packaged a new package mainly as a proof of concept that a simple
> external module package can work. That is not a usable package, indeed.
> It does not even have misdn-init or any alternative properly packaged.

Neither has mine, basically because all of these approaches are wrong.

The right thing to do would be hotplug integration coupled with the 
kernel enforcing sanity.

    Simon