From owner-freebsd-isdn Sun Sep 20 21:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22503 for freebsd-isdn-outgoing; Sun, 20 Sep 1998 21:34:20 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22448 for ; Sun, 20 Sep 1998 21:33:52 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id GAA28833 for freebsd-isdn@FreeBSD.ORG; Mon, 21 Sep 1998 06:30:13 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id GAA10345 for freebsd-isdn@FreeBSD.ORG; Mon, 21 Sep 1998 06:28:19 +0200 (CEST) (envelope-from andreas) Message-ID: <19980921062819.A9855@klemm.gtn.com> Date: Mon, 21 Sep 1998 06:28:19 +0200 From: Andreas Klemm To: freebsd-isdn@FreeBSD.ORG Subject: ethereal port (network analyzer) and i4b doesn't work together Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-BETA SMP Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi ! When trying to scan my ISDN traffic, the analyzer only gets confused by sunny characters. Only scanning ethernet interfaces is possible. Is there something wrong with byte order or something like this ? BTW, ethereal is a really cool thing... See ports collection. Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Sep 21 08:00:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23173 for freebsd-isdn-outgoing; Mon, 21 Sep 1998 08:00:56 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from dhi.dk (gateway.dhi.dk [193.88.35.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23168 for ; Mon, 21 Sep 1998 08:00:54 -0700 (PDT) (envelope-from fpc@dhi.dk) Received: by gateway.dhi.dk id <19722>; Mon, 21 Sep 1998 15:08:51 +0000 Message-Id: <98Sep21.150851gmt.19722@gateway.dhi.dk> Date: Mon, 21 Sep 1998 14:59:48 +0000 From: Frederico Pereira da Costa Organization: Danish Hydraulic Institute X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en Mime-Version: 1.0 To: ISDN for BSD Subject: Hi Again... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi ... As i told you i manage to put ISDN working through isppp0. And i sayd that i want to start to contribute to this package. Before i start doing that, i would like to know a few things. I am developing software since 1994, i have used VB, Java, C++, pascal, and others. Currently i am workign with Visual C++ 5.0 and wirh MFC at my work. As i would like to start making some code for freebsd, in particular for this package, can some of you point me some directions on the platform to use (gcc x.x.x) and some tools for analysing and managing code. I don't know if this is the right mailing list. If not please point me the correct one ... Thanks in advance Frederico -- Frederico Pereira da Costa Danish Hydraulic Institute Phone: +45 45 179 100 Fax: +45 45 762 567 Email: mailto:fpc@dhi.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Sep 22 13:11:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19569 for freebsd-isdn-outgoing; Tue, 22 Sep 1998 13:11:59 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from downtown.oche.de (downtown.oche.de [194.94.253.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19450 for ; Tue, 22 Sep 1998 13:10:30 -0700 (PDT) (envelope-from vs@lucy.wrath.oche.de) Received: (from uucp@localhost) by downtown.oche.de (8.8.8/8.8.8/Debian/GNU) with UUCP id WAA09802 for freebsd-isdn@freebsd.org; Tue, 22 Sep 1998 22:02:42 +0200 Received: (from vs@localhost) by lucy.wrath.oche.de (8.8.8/8.8.5) id VAA01425 for freebsd-isdn@freebsd.org; Tue, 22 Sep 1998 21:04:54 +0200 (CEST) Date: Tue, 22 Sep 1998 21:04:54 +0200 (CEST) From: Volker Stolz Message-Id: <199809221904.VAA01425@lucy.wrath.oche.de> To: freebsd-isdn@FreeBSD.ORG Subject: Fun with i4b & teles (retry) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just grabbed i4b-00.63-alpha and (succesfully) built a kernel vor FreeBSD-2.2.7 and a Teles S0/16. After rebooting with the new kernel, I got a message stating "HSCX version 15 unknown" at isic0-initialisation time. As both the ISAC and HSCX-chips are labeled with the (for a Teles S0/16) valid names (i.e. ISAC V2.3/HSCX 82525 N V2.1) I tweaked the source to skip this check for HSCX_UNKWN (l1/i4b_isic.c). After this, the machine boots and detects the right card with the right chipset. But of course I am suffering from the "State F4"-trouble :( After wildly configuring the BIOS I still don't get past this error after accessing ipr0. What makes me wonder though (warning, this is a little source-specific): At a later point in i4b_isic.c, sc->sc_hscx_version (which I don't touch, I just skip the return(0); exit;) is checked again to printf() "HSCX Version UNKNOWN" again in a slightly different "syntax" and set the value to HSCX_UNKN for all values >=HSCX_UNKN. My tweaked version doesn't select this if-branch, but uses the else-branch to print (correct) HSCX-version-information! -> the first check detects sc->sc_hscx_version = 15 (HSCX_UNKN) -> I don't do anything but just let the driver go on -> the second check detects a valid version for sc->sc_hscx_version (82525 or 21525 Version 2.1) Any hints on this one? Volker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Sep 23 00:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02395 for freebsd-isdn-outgoing; Wed, 23 Sep 1998 00:48:36 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from RVC1.Informatik.BA-Stuttgart.DE (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02283 for ; Wed, 23 Sep 1998 00:48:12 -0700 (PDT) (envelope-from helbig@RVC1.Informatik.BA-Stuttgart.DE) Received: (from helbig@localhost) by RVC1.Informatik.BA-Stuttgart.DE (8.8.8/8.8.8) id JAA05433; Wed, 23 Sep 1998 09:50:09 +0200 (CEST) Date: Wed, 23 Sep 1998 09:50:09 +0200 (CEST) From: Wolfgang Helbig Message-Id: <199809230750.JAA05433@RVC1.Informatik.BA-Stuttgart.DE> To: freebsd-isdn@FreeBSD.ORG, vs@lucy.wrath.oche.de Subject: Re: Fun with i4b & teles (retry) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > I just grabbed i4b-00.63-alpha and (succesfully) built a kernel vor > FreeBSD-2.2.7 and a Teles S0/16. > After rebooting with the new kernel, I got a message stating "HSCX version > 15 unknown" at isic0-initialisation time. As both the ISAC and HSCX-chips > are labeled with the (for a Teles S0/16) valid names (i.e. ISAC V2.3/HSCX 82525 N V2.1) looks like you configured TEL_S0_16_3, flags 0x04 instead of TEL_S0_16, flags 0x02. Please double check your kernel configuration file and consult "man 4 isic" for the proper statements. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Sep 23 05:53:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19385 for freebsd-isdn-outgoing; Wed, 23 Sep 1998 05:53:51 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from hq.seicom.net (hq.seicom.net [194.97.200.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19371 for ; Wed, 23 Sep 1998 05:53:41 -0700 (PDT) (envelope-from js@mgm-net.de) Received: from bastjon.mgm-net.de by hq.seicom.net (8.8.5/8.8.3) with ESMTP id OAA15423; Wed, 23 Sep 1998 14:53:49 +0200 (CEST) Received: from orion.mgm-net.de (orion [192.168.1.1]) by bastjon.mgm-net.de (8.8.8/8.8.5) with ESMTP id OAA01220; Wed, 23 Sep 1998 14:53:30 +0200 (CEST) Received: (from js@localhost) by orion.mgm-net.de (8.8.3/8.8.5) id OAA12281; Wed, 23 Sep 1998 14:48:35 +0200 (MET DST) Date: Wed, 23 Sep 1998 14:48:35 +0200 (MET DST) Message-Id: <199809231248.OAA12281@orion.mgm-net.de> From: Jochen Scharrlach To: hm@kts.org CC: logix@foobar.franken.de, hm@kts.org, freebsd-isdn@FreeBSD.ORG In-reply-to: (hm@kts.org) Subject: Re: i'll unsubscribe from isdn-freebsd Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mighty GNU Emacs Reply-to: js@mgm-net.de Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 From owner-freebsd-isdn Wed Sep 23 12:21:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25716 for freebsd-isdn-outgoing; Wed, 23 Sep 1998 12:21:01 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from shire.domestic.de (kuebart.stuttgart.netsurf.de [194.233.216.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25696 for ; Wed, 23 Sep 1998 12:20:52 -0700 (PDT) (envelope-from joki@kuebart.stuttgart.netsurf.de) Received: (from joki@localhost) by shire.domestic.de (8.8.8/8.8.7) id VAA00494; Wed, 23 Sep 1998 21:21:25 +0200 (CEST) (envelope-from joki) From: Joachim Kuebart Message-Id: <199809231921.VAA00494@shire.domestic.de> Subject: Problem with Q.931 implementation To: isdn@FreeBSD.ORG Date: Wed, 23 Sep 1998 21:21:24 +0200 (CEST) Cc: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, for a few weeks now, I've got the following problem: The log files lead me to conclude that some Q.931 isn't properly understood by the driver. Due to some follow-up errors this leads to a reboot as soon as a connection succeeds. This version of i4b: -rw-r--r-- 1 root bin 525165 10 Jul 10:10 i4b-00.63-alpha-100798.tgz This is the debug log: 1st attempt ------------- Sep 23 21:05:44 shire /kernel: isppp0: lcp open(initial) Sep 23 21:05:44 shire /kernel: isppp0: phase establish Sep 23 21:05:44 shire isdnd[214]: DBG msg_dialout: dial req from isppp, unit 0 Sep 23 21:05:44 shire isdnd[214]: DBG find_device: found entry 0! Sep 23 21:05:44 shire isdnd[214]: DBG FSM event [msg-dialout]: [idle => dialing] Sep 23 21:05:44 shire isdnd[214]: DBG F_DIAL: local dial out request Sep 23 21:05:44 shire isdnd[214]: DBG select_first_dialno: only one no, no = 726704 Sep 23 21:05:44 shire isdnd[214]: CHD 00004 Netsurf rate 240 sec/unit (rate) Sep 23 21:05:44 shire isdnd[214]: CHD 00004 Netsurf dialing out from 653706 to 726704 Sep 23 21:05:44 shire isdnd[214]: CHD 00004 Netsurf outgoing call proceeding (ctl 0, ch 0) Sep 23 21:05:45 shire isdnd[214]: CHD 00004 Netsurf incoming alert Sep 23 21:05:45 shire /kernel: isppp0: Up event Sep 23 21:05:45 shire /kernel: isppp0: lcp up(starting) Sep 23 21:05:45 shire /kernel: isppp0: lcp output Sep 23 21:05:45 shire isdnd[214]: DBG msg_charging: 1 unit(s) (estimated) Sep 23 21:05:45 shire /kernel: i4b-L3-i4b_decode_q931_message: STATUS message ^^^^^^^^^^^^^^^^^^^^^^^^^^ First error condition Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) + k) & 127)! Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_i_frame_queued_up: state = ST_MULTIFR Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_print_l2var: unit0 V(R)=13, V(S)=11, V(A)=10,ACKP=0,PBSY=0,OBSY=0 Sep 23 21:05:45 shire isdnd[214]: CHD 00004 Netsurf outgoing call active (ctl 0, ch 0) Sep 23 21:05:45 shire /kernel: isppp0: lcp down(req-sent) Sep 23 21:05:45 shire /kernel: isppp0: Down event (carrier loss) Sep 23 21:05:45 shire /kernel: isppp0: lcp close(starting) Sep 23 21:05:46 shire /kernel: isppp0: phase dead Sep 23 21:05:45 shire isdnd[214]: DBG exec_prog: popmail, args: 00004 Netsurf outgoing call active (ctl 0, ch 0) Sep 23 21:05:45 shire isdnd[214]: DBG FSM event [msg-con-act-ind]: [dialing => connected] Sep 23 21:05:45 shire isdnd[214]: DBG F_DOK: dial out ok Sep 23 21:05:45 shire isdnd[214]: DBG select_this_dialno: index = 0, no = 726704 Sep 23 21:05:45 shire isdnd[214]: DBG normal child (pid=1384) termination, exitstat = 0 Sep 23 21:05:45 shire isdnd[214]: DBG msg_charging: 1 unit(s) (AOCE) Sep 23 21:05:45 shire isdnd[214]: CHD 00004 Netsurf outgoing call disconnected (remote) Sep 23 21:05:45 shire isdnd[214]: CHD 00004 Netsurf cause 101: Message not compatible with call state (Q.850) Sep 23 21:05:45 shire isdnd[214]: CHD 00004 Netsurf charging: 1 units, 0 seconds Sep 23 21:05:45 shire isdnd[214]: CHD 00004 Netsurf accounting: in 0, out 19 (in 0, out 0) Sep 23 21:05:45 shire isdnd[214]: DBG FSM event [msg-disc-ind]: [connected => idle] Sep 23 21:05:45 shire isdnd[214]: DBG F_IDIS: disconnect indication 2nd attempt ------------- Sep 23 21:05:52 shire /kernel: isppp0: lcp open(initial) Sep 23 21:05:52 shire /kernel: isppp0: phase establish Sep 23 21:05:52 shire isdnd[214]: DBG msg_dialout: dial req from isppp, unit 0 Sep 23 21:05:52 shire isdnd[214]: DBG find_device: found entry 0! Sep 23 21:05:52 shire isdnd[214]: DBG FSM event [msg-dialout]: [idle => dialing] Sep 23 21:05:52 shire isdnd[214]: DBG F_DIAL: local dial out request Sep 23 21:05:52 shire isdnd[214]: DBG select_first_dialno: only one no, no = 726704 Sep 23 21:05:52 shire isdnd[214]: CHD 00005 Netsurf rate 240 sec/unit (rate) Sep 23 21:05:52 shire isdnd[214]: CHD 00005 Netsurf dialing out from 653706 to 726704 Sep 23 21:05:52 shire /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x65, crflag = 0x1, msg = 0x4d, frame = 0x4d 0x8 0x2 0x82 0xd1 ^^^^^^^^^^^^^^^^^^^^^ Now something weired is happening... Sep 23 21:05:56 shire /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 41 Sep 23 21:05:56 shire /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x65, crflag = 0x1, msg = 0x4d, frame = 0x4d 0x8 0x2 0x82 0xd1 Sep 23 21:05:56 shire isdnd[214]: CHD 00005 Netsurf outgoing call proceeding (ctl 0, ch 0) Sep 23 21:05:57 shire isdnd[214]: CHD 00005 Netsurf incoming alert Sep 23 21:05:57 shire /kernel: isppp0: Up event Sep 23 21:05:57 shire /kernel: isppp0: lcp up(starting) Sep 23 21:05:57 shire /kernel: isppp0: lcp output Sep 23 21:05:57 shire /kernel: isppp0: lcp input(req-sent): Sep 23 21:05:57 shire /kernel: isppp0: lcp parse opts: 0x0 [rej] mru auth-proto 0x11 [rej] 0x13 [rej] send conf-rej Sep 23 21:05:57 shire /kernel: isppp0: lcp output Sep 23 21:05:57 shire /kernel: isppp0: lcp input(req-sent): Sep 23 21:05:57 shire /kernel: isppp0: lcp rej opts: auth-proto [don't insist on auth for callout] Sep 23 21:05:57 shire /kernel: isppp0: lcp output Sep 23 21:05:58 shire /kernel: isppp0: lcp input(req-sent): Sep 23 21:05:58 shire /kernel: isppp0: lcp parse opts: mru auth-proto Sep 23 21:05:58 shire /kernel: isppp0: lcp parse opt values: mru 1524 auth-proto send conf-ack Sep 23 21:05:58 shire /kernel: isppp0: lcp output Sep 23 21:05:58 shire /kernel: isppp0: lcp input(ack-sent): Sep 23 21:05:58 shire /kernel: isppp0: lcp tlu Sep 23 21:05:58 shire /kernel: isppp0: phase authenticate Sep 23 21:05:57 shire isdnd[214]: DBG msg_charging: 1 unit(s) (estimated) Sep 23 21:05:58 shire /kernel: isppp0: chap input Sep 23 21:05:58 shire /kernel: isppp0: chap output Sep 23 21:05:58 shire /kernel: isppp0: chap success: \x0 Sep 23 21:05:58 shire /kernel: isppp0: phase network Sep 23 21:05:58 shire /kernel: isppp0: ipcp open(initial) Sep 23 21:05:58 shire /kernel: isppp0: ipcp up(starting) Sep 23 21:05:58 shire /kernel: isppp0: ipcp output Sep 23 21:05:58 shire /kernel: isppp0: ipcp input(req-sent): Sep 23 21:05:58 shire /kernel: isppp0: ipcp parse opts: compression [rej] address send conf-rej Sep 23 21:05:58 shire /kernel: isppp0: ipcp output Sep 23 21:05:58 shire /kernel: isppp0: ipcp input(req-sent): Sep 23 21:05:58 shire /kernel: isppp0: ipcp nak opts: address [wantaddr 194.233.216.182] [agree] Sep 23 21:05:59 shire /kernel: isppp0: ipcp output Sep 23 21:05:59 shire /kernel: isppp0: ipcp input(req-sent): Sep 23 21:05:59 shire /kernel: isppp0: ipcp parse opts: address Sep 23 21:05:59 shire /kernel: isppp0: ipcp parse opt values: address 0.0.0.1 [ack] send conf-ack Sep 23 21:05:59 shire /kernel: isppp0: ipcp output Sep 23 21:05:59 shire /kernel: isppp0: ipcp input(ack-sent): Sep 23 21:05:59 shire /kernel: isppp0: ipcp tlu Sep 23 21:08:00 shire syslogd: restart ^^^^^^^ And now this... :-( Sep 23 21:08:00 shire /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Sep 23 21:08:00 shire /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Sep 23 21:08:00 shire /kernel: The Regents of the University of California. All rights reserved. Sep 23 21:08:01 shire /kernel: Sep 23 21:08:01 shire /kernel: FreeBSD 2.2.6-STABLE #0: Wed Sep 23 19:45:55 CEST 1998 ... This is the isdn part of dmesg: isic0 at 0x240 irq 10 flags 0x8 on isa isic0: AVM A1 or AVM Fritz!Card isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x1620) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x620, AddrB=0xe20) i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached cu Jo --------------------------------------------------------------------- FreeBSD: The Power to Serve Joachim Kuebart Tel: +49 711 653706 Replicants are like any other machine -- Germany they're either a benefit or a hazard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Sep 24 01:02:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20965 for freebsd-isdn-outgoing; Thu, 24 Sep 1998 01:02:11 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20960 for ; Thu, 24 Sep 1998 01:02:06 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id KAA15792; Thu, 24 Sep 1998 10:02:01 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0zM6Lh-002ZjZC; Thu, 24 Sep 98 10:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Thu, 24 Sep 1998 09:15:18 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for isdn@freebsd.org; Thu, 24 Sep 1998 09:15:20 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #2 built 1998-Aug-25) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Problem with Q.931 implementation In-Reply-To: <199809231921.VAA00494@shire.domestic.de> from Joachim Kuebart at "Sep 23, 98 09:21:24 pm" To: joki@kuebart.stuttgart.netsurf.de (Joachim Kuebart) Date: Thu, 24 Sep 1998 09:15:20 +0200 (CEST) Cc: isdn@FreeBSD.ORG, hm@kts.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joachim Kuebart wrote: > Sep 23 21:05:45 shire /kernel: i4b-L3-i4b_decode_q931_message: STATUS message > Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) + k) & 127)! > Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_i_frame_queued_up: state = ST_MULTIFR > Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_print_l2var: unit0 V(R)=13, V(S)=11, V(A)=10,ACKP=0,PBSY=0,OBSY=0 This looks exactly like a phenomenon i had here and which took me several weeks to debug. This is fixed in my sources of i4b. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Sep 24 02:02:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28436 for freebsd-isdn-outgoing; Thu, 24 Sep 1998 02:02:23 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28425 for ; Thu, 24 Sep 1998 02:02:17 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id LAA17054; Thu, 24 Sep 1998 11:02:01 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0zM7Hk-002ZjcC; Thu, 24 Sep 98 11:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Thu, 24 Sep 1998 10:31:20 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for freebsd-isdn@FreeBSD.ORG; Thu, 24 Sep 1998 10:31:22 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #2 built 1998-Aug-25) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: i'll unsubscribe from isdn-freebsd In-Reply-To: <199809231248.OAA12281@orion.mgm-net.de> from Jochen Scharrlach at "Sep 23, 98 02:48:35 pm" To: js@mgm-net.de Date: Thu, 24 Sep 1998 10:31:22 +0200 (CEST) Cc: hm@kts.org, logix@foobar.franken.de, freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org All the following is not a flame and it is not meant to be taken personally. A noticable amount of letters has a content similar to the one i'm replying to here and just because of this i'm answering this one. > > 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. Why do you think you can avoid something and instead depend on me doing this work for you ? There are two ways available to get something done, one way is to do sit down and do something yourself and the other is to pay someone to do something which one self does not want to do or is not able to do. > 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". I once (and the only time i remeber) wrote you (on the list): > I'm not sure what they mean, but they don't look good. It seems to me > that i4b gets trouble if the machine runs for several days. Mine run for several weeks without trouble .... until they are upgraded. Just for the record - a quoute from the i4b README: Some bugs seem to occur only in certain environments and are not reproducable here without access to the equipment you are connected to or other equipment like PBX simulators: in this case you are the only person being able to trace down the bug and fix it. > I promise to upgrade to 0.62 soon :) That would be a good idea! hellmuth That is quite different to "I don't have your problem, so I don't care", isn't it ? And i would write it again; its as valid today as it was valid at the time i wrote it. > Sorry, but that's not very satisfying for me. I can imagine that. But read it again: Some bugs seem to occur only in certain environments and are not reproducable here without access to the equipment you are connected to or other equipment like PBX simulators: in this case you are the only person being able to trace down the bug and fix it. I cannot reproduce certain failure scenes here. I simply cannot afford to have all the resources available here to reproduce all sorts of failures. I simply have sometimes no idea where to search or where to look. And some- times i'm simply not in a condition or i don't have the time to handhold people to fix problems or get their installation up and running. > 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. You are implying that i'm not interested in fixing bugs. How do you come to that (wrong) conclusion ? I do my very best to make i4b as good as possible, but i simply have no idea why it fails sometimes. I would really like to be able to debug certain failure scenes, but it always reduces to money why i'm not able to do exactly that: travel to customers site and fix it in the field or buy the equipment needed to simulate the bug here or invest a huge amount of time to write and debug code to implement this or that nice to have feature like being able to recover from pulling the S0 plug in an orderly manner. (I've got one or two offers to use this type of equipment remotely over the internet. Thanks a lot, but i'm simply not able to use it because my internet connection is charged by volume and i have to care for nearly every single byte i use it for.) (Note: i4b is _quite_ different in nature from emacs, gcc or samba: to debug them you usually don't need to pay communication charges, ITU/ETSI documentation, buy hardware and analyzers or simulators.) > 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. It would be nice and i would appreciate it highly if i would be able to write a general purpose ISDN package. I would be able to work all day long on just isdn4bsd! It would take many machines and many cards and many different configurations and many different OS releases. I would have to buy all those docs i just know from saying and i would have to buy all those shiny new cards and sign many NDA's. I would test my implementation against references and buy test suites and simulators and eventually it would run under all imaginable situations and i'd get a telco approval for i4b. And i would charge everyone who needs an i4b copy, hmmm, lets say 100$ plus shipping and handling, just binaries. Telephone support for the first 30 days add up another 25 or 50$ and after that i'm shure everyone here signs a maintenance agreement for ongoing support and quarteryearly updates and enhancements. Oh, you want to get something for free - Ok. What i'm then able to do is a package which fits my needs. And as much help and contribution and donation i get from the outside exactly proportional that much general purpose it will be. Oh, you want me to care for your problems, do you then also want to care for my problems ? And what do you think, shall i care only for your problems or also for everyone else's problems with i4b ? Where do you think shall i take the time from ? Where shall i take the money from when fixing a bug or implementing a feature or a driver means being connected to some remote site or buying docs or buying hardware ? I'm sorry, but you get exactly what you pay for. And in the case of isdn4bsd you get a whole more than what you did actually payed for. And belive me, i care. Usually i care as much as the remote side is willing to invest time (for learning, understanding the code, reading the docs and the README, to produce proper and complete bugreports, to solve the problem by themselves), persistence and other resources. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Sep 24 10:15:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04064 for freebsd-isdn-outgoing; Thu, 24 Sep 1998 10:15:42 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from shire.domestic.de (kuebart.stuttgart.netsurf.de [194.233.216.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04045 for ; Thu, 24 Sep 1998 10:15:32 -0700 (PDT) (envelope-from joki@kuebart.stuttgart.netsurf.de) Received: from yacht.domestic.de (yacht.domestic.de [192.168.1.4]) by shire.domestic.de (8.8.8/8.8.7) with ESMTP id TAA17967; Thu, 24 Sep 1998 19:15:55 +0200 (CEST) (envelope-from joki@shire.domestic.de) From: Joachim Kuebart Received: (from joki@localhost) by yacht.domestic.de (8.9.1/8.8.7) id TAA00408; Thu, 24 Sep 1998 19:18:19 +0200 (CEST) (envelope-from joki@shire.domestic.de) Message-Id: <199809241718.TAA00408@yacht.domestic.de> Subject: Re: Problem with Q.931 implementation In-Reply-To: from Hellmuth Michaelis at "Sep 24, 98 09:15:20 am" To: hm@kts.org Date: Thu, 24 Sep 1998 19:18:19 +0200 (CEST) Cc: joki@kuebart.stuttgart.netsurf.de, isdn@FreeBSD.ORG, hm@kts.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis wrote: > Joachim Kuebart wrote: > > > Sep 23 21:05:45 shire /kernel: i4b-L3-i4b_decode_q931_message: STATUS message > > Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) + k) & 127)! > > Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_i_frame_queued_up: state = ST_MULTIFR > > Sep 23 21:05:45 shire /kernel: i4b-L2-i4b_print_l2var: unit0 V(R)=13, V(S)=11, V(A)=10,ACKP=0,PBSY=0,OBSY=0 > > This looks exactly like a phenomenon i had here and which took me several > weeks to debug. This is fixed in my sources of i4b. > That's good news. How do I go about getting these sources? I have no problem running cutting edge stuff (we all have to die someday)... cu Jo --------------------------------------------------------------------- FreeBSD: The Power to Serve Joachim Kuebart Tel: +49 711 653706 I like to think. Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Sep 24 11:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16123 for freebsd-isdn-outgoing; Thu, 24 Sep 1998 11:32:13 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16118 for ; Thu, 24 Sep 1998 11:32:11 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id UAA28495; Thu, 24 Sep 1998 20:32:02 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0zMGBN-002ZjZC; Thu, 24 Sep 98 20:32 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Thu, 24 Sep 1998 20:30:56 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for isdn@freebsd.org; Thu, 24 Sep 1998 20:30:58 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #2 built 1998-Aug-25) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Problem with Q.931 implementation In-Reply-To: <199809241718.TAA00408@yacht.domestic.de> from Joachim Kuebart at "Sep 24, 98 07:18:19 pm" To: joki@kuebart.stuttgart.netsurf.de (Joachim Kuebart) Date: Thu, 24 Sep 1998 20:30:58 +0200 (CEST) Cc: isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joachim Kuebart wrote: > That's good news. How do I go about getting these sources? Currently they are not available. The tree needs a major cleanup after some horrible debugging sessions, finishing a halfready utility, a cleanup for beta release, i have to go thru a beta cycle i promised Martin and in case someone has a good example of a proven for personal, educational and non-commercial usage only licence, i'd like to hear from him/her. I know this is unsatisfying, and i know how _i_ sometimes think about people not immediately releasing code for certain reasons, but this is the current state as it is. Comments welcome, flames to /dev/null please. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Sep 24 13:08:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02907 for freebsd-isdn-outgoing; Thu, 24 Sep 1998 13:08:28 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02891 for ; Thu, 24 Sep 1998 13:08:22 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA08811; Thu, 24 Sep 1998 22:00:10 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id VAA06932; Thu, 24 Sep 1998 21:52:09 +0200 (CEST) (envelope-from andreas) Message-ID: <19980924215208.A3974@klemm.gtn.com> Date: Thu, 24 Sep 1998 21:52:08 +0200 From: Andreas Klemm To: hm@kts.org, js@mgm-net.de Cc: logix@foobar.franken.de, freebsd-isdn@FreeBSD.ORG Subject: Re: i'll unsubscribe from isdn-freebsd References: <199809231248.OAA12281@orion.mgm-net.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Hellmuth Michaelis on Thu, Sep 24, 1998 at 10:31:22AM +0200 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-BETA SMP Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Sep 24, 1998 at 10:31:22AM +0200, Hellmuth Michaelis wrote: > [...] Hellmuth, your description of a "home developers world" is very clear and true. I hope that many people understand now, that even for "cracks like you (tm)" it's a huge amount of time and money, to develope and maintain a piece of software like i4b or something else. Freetime is a very precious thing and communication costs and hardware costs eat you up financially ... But ... I'd say don't hear to the end users too much and don't get angry or frustrated. They are end users and always want their problems fixed for $0 ;-) Helle, even in business people mostly try to get something for the half of the price or $0. So what do you expect from end users who usually don't have $xxxxxx in the pocket ?! ;-)) I'd say, be happy that people like me are proud to know people like you, who are very kind and competent and write damn good software for free ;-) Get some spare time, if you need to and write some more code if you have fun to do so. But don't get influenced by people simply crying "more, more". Keep on doing the good work if you like. Write people a standard mail, if they want too much from you. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Sep 26 08:35:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15491 for freebsd-isdn-outgoing; Sat, 26 Sep 1998 08:35:21 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15485 for ; Sat, 26 Sep 1998 08:35:17 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.7) with SMTP id QAA09156; Sat, 26 Sep 1998 16:35:39 +0100 (BST) (envelope-from arg@arg1.demon.co.uk) Date: Sat, 26 Sep 1998 16:35:36 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: freebsd-isdn@FreeBSD.ORG cc: hm@kts.org Subject: i4b/YACC breakage in -STABLE? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After doing a 'make world' with recent -STABLE sources, I find that i4b/isdnd no longer builds - "lex: can't open y.tab.h". It appears that yacc is now creating rc_parse.h instead of y.tab.h; a workaround to get isdnd to build is to attempt the make, when it fails "mv rc_parse.h y.tab.h" and make again. Looking at the CVS logs, yacc itself doesn't seem to have changed, but there have been some relevant looking changes to /usr/share/mk/bsd.dep.mk. I tried a few quick hacks to the isdnd makefile, but I couldn't get it to work properly (not surprising given that I don't really understand what is going on here). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Sep 26 10:10:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25267 for freebsd-isdn-outgoing; Sat, 26 Sep 1998 10:10:55 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from RVC1.Informatik.BA-Stuttgart.DE (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25209 for ; Sat, 26 Sep 1998 10:10:37 -0700 (PDT) (envelope-from helbig@RVC1.Informatik.BA-Stuttgart.DE) Received: (from helbig@localhost) by RVC1.Informatik.BA-Stuttgart.DE (8.8.8/8.8.8) id TAA12237; Sat, 26 Sep 1998 19:12:45 +0200 (CEST) Date: Sat, 26 Sep 1998 19:12:45 +0200 (CEST) From: Wolfgang Helbig Message-Id: <199809261712.TAA12237@RVC1.Informatik.BA-Stuttgart.DE> To: arg@arg1.demon.co.uk, freebsd-isdn@FreeBSD.ORG Subject: Re: i4b/YACC breakage in -STABLE? Cc: hm@kts.org Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I fixed a similar problem for FreeBSD current by changing some statements in the Makefile. These changes take effect only under the condition ${BSDTYPE}==FREEBSD && ${RELEASE}=="3.0-CURRENT". You might want to try out these changes by lying to make: make clean RELEASE="3.0-CURRENT" make If this works, we might have to prepare for RELEASE=="2.2.8", the next 2... release. (And for 3.0-RELEASE) Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Sep 26 16:26:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02667 for freebsd-isdn-outgoing; Sat, 26 Sep 1998 16:26:55 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02635 for ; Sat, 26 Sep 1998 16:26:42 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.7) with SMTP id AAA10107; Sun, 27 Sep 1998 00:26:40 +0100 (BST) (envelope-from arg@arg1.demon.co.uk) Date: Sun, 27 Sep 1998 00:26:40 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Wolfgang Helbig cc: freebsd-isdn@FreeBSD.ORG, hm@kts.org Subject: Re: i4b/YACC breakage in -STABLE? In-Reply-To: <199809261712.TAA12237@RVC1.Informatik.BA-Stuttgart.DE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 26 Sep 1998, Wolfgang Helbig wrote: > I fixed a similar problem for FreeBSD current by changing some > statements in the Makefile. These changes take effect only under the > condition ${BSDTYPE}==FREEBSD && ${RELEASE}=="3.0-CURRENT". I had spotted those, and tried editing the makefile to activate the -CURRENT behaviour. I must have got it wrong somehow, as it didn't work. > You might want to try out these changes by lying to make: > > make clean > RELEASE="3.0-CURRENT" make This did work however. > If this works, we might have to prepare for RELEASE=="2.2.8", the next > 2... release. (And for 3.0-RELEASE) Isn't there something better we can do? Like explicitly invoking yacc from the makefile rather than relying on the default rule from bsd.def.mk maybe? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message