Date: Wed, 06 Aug 1997 01:16:10 +0200 From: "Julian H. Stacey" <jhs@FreeBSD.ORG> To: current@FreeBSD.ORG, isdn@muc.ditec.de Subject: Re: ISDN drivers/cards Message-ID: <199708052316.BAA01266@wall.jhs.no_domain> In-Reply-To: Your message of "Tue, 05 Aug 1997 17:20:39 %2B0200." <9708051520.AA25084@cssmuc.frt.dec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> steve@visint.co.uk writes: > > I tried using bisdn, both with -current and 2.2.2, without much luck, Works fine for me on 2.2.1, used to be fine too on an ancient current, (but I got tired of the volatile nature of current & went to releases). > I'm > in europe (england) I'm in Germany, FWIW a friend of mine (Barry S) who has developed a number of isdn PC cards ( not supported by bisdn, far as I know, but described on http://www.freebsd.org/~jhs/lion/ ) says nasty things about British Telecom's isdn service implementation, in comparison with Deutsche Telekom's implementation... maybe there is something different for you in the UK (the developers are mostly based in Germany) ? > and although bisdn connects and works most of the time > it did have a nasty habit of just halting the machine completely. Never has halted for me, but then my isdn machine runs lighter perhaps than yours (just does net, not X11 & keyboard driven other stuff, that I run on another ethernet'd box). > If I > used natd Huh ? man natd No manual entry for natd > and aliased a bunch of machines through it it crashed sooner.. > but it only seems to crash when bisdn I was using telnet. (ping etc. > wouldn't crash it for me). I rarely use telnet (but do use it) mostly I `just' use rlogin, ftp (& whatever make fetch calls) & popclient & http etc on a 16M 486 33MHz ISA 2.2.1 (going to 2.2.2 soon when I replace a 2nd monitor to do it with :-)) > Basically though, bisdn isn't a workable stable system. It _Is_ Stable for me on mine ! > It was a pain to > install True, but then there are copyright etc reasons why the code comes as old + new bits + patches, till the rewrite is done. There are also README cookbooks & patchkits (on ftp.muc.ditec.de/isdn, (personally I have a src/ customising script & same diffs in different format in my http://www.freebsd.org/~jhs/src/bsd/fixes/customise ) > and IMHO is a total mess. I wouldn't know about the code stylistic quality, I've not looked, I've only hacked one trivial tiny morsel (to add bell on connect/disconnect). > Well, just wanted to say that in case someone suggests that we should all > be using bisdn. Because IMHO, it sucks, and really shouldn't be used as a > base for future code either. (except as a bad example.) I disagree ! PS I found a couple of phone calls to Gary J. helped me enormously, since then I've been a very happy user of the bisdn code that Hellmuth, Gary et al have given us, I'm just quietly waiting for the rewrite, which will only get delayed if those guys get side tracked by criticism such as this. The isdn has always suffered from an excess of demanding users, & lack of programmers, so I suggest, (without wishing to be rude), that you contribute code, or keep quiet, & figure out what you've done wrong on your system, .... 'cos it sure works fine for me :-) Ideally, invest in a couple of international calls to Gary J, and hope he's kind enought to talk you through to discover what you've probably done wrong. It works for me, so it could for you, I guess ? .... Good Luck :-) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708052316.BAA01266>