Date: Wed, 23 Sep 1998 14:48:35 +0200 (MET DST) From: Jochen Scharrlach <js@mgm-net.de> To: hm@kts.org Cc: logix@foobar.franken.de, hm@kts.org, freebsd-isdn@FreeBSD.ORG Subject: Re: i'll unsubscribe from isdn-freebsd Message-ID: <199809231248.OAA12281@orion.mgm-net.de> In-Reply-To: <m0zIqIs-000010C@bert.kts.org> (hm@kts.org)
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > The reasons are twofolded - one thing is that most of the private and > commercial users of i4b seem to have a strong consume-only mentality, Ok, this is what I would have to do to debug i4b: * learning the ISDN standard * learning how i4b is structured (ok, that is somehow documented) That's about 20h work until I can start doing anything. I'll probably do something about it (I'll build up my first test-computer with 2 ISDN-cards this afternoon), but without any support from the developers I don't have much hope. I *have* hacked other programs programs like Emacs before, but only because I had an idea where to look at. What I whished from you would have been a hint in which part of i4b my problem is caused and how it may be solved. All I got from you is a nice comment like "I don't have your problem, so I don't care". Sorry, but that's not very satisfying for me. I have a bit experience with the way bugs are handled by the Emacs-, gcc- and Samba-developers and all of them are usually interested in fixing bugs. My question to you: do you want to write an ISDN-package that fits for *your* needs, or do you want to build a general-purpose package? If you don't care for my problems, I would have to do everything on my own and that would be probably way to time consuming for me. Just my 2 cents, Jochen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809231248.OAA12281>