From owner-freebsd-stable Sun Jan 12 07:32:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA01894 for stable-outgoing; Sun, 12 Jan 1997 07:32:35 -0800 (PST) Received: from ns.tp.silkera.net (ns.tp.silkera.net [203.70.2.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA01802; Sun, 12 Jan 1997 07:28:04 -0800 (PST) Received: from dorothy.bsd.zerodist.com (ts63-ip79.tp.silkera.net [203.70.2.79]) by ns.tp.silkera.net (8.8.4/8.8.4) with SMTP id XAA08819; Sun, 12 Jan 1997 23:24:55 +0800 (CST) Message-ID: <32D90341.2419@ms2.hinet.net> Date: Sun, 12 Jan 1997 23:29:58 +0800 From: zerodist Reply-To: zerodist@ms2.hinet.net X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: owensc@enc.edu, wangel@wgrobez1.remote.louisville.edu, dnex@access.digex.net, current@freebsd.org, stable@freebsd.org Subject: ppp setup Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello: I have a question about ppp setup. Could someone out there help me? My ISP use PAP authentication. My ppp.conf setup is as follows. default: set device /dev/cuaa1 set speed 38400 disable lqr deny lqr set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0 OK-AT-OK \\dATDT\ \T TIMEOUT 40 CONNECT" iij-pap: set phone 727-2710 set login "TIMEOUT 5 name:-\\r-name: member word: silkera" deny chap accept pap set authname zerodist #dkfjdfjo my fake password, I typed real one though set authkey dkfjdfjo set timeout 0 set openmode active set ifaddr 0 203.70.2.4/24 add 203.70.2.0 255.255.255.0 203.70.2.4 add 0 0 203.70.2.4 dial Now I issue command ppp iij-pap, it will dial and establish a connection between me and my ISP. And both me and my ISP will get an IP dynamically. Say I get 203.70.2.36 and my ISP get 203.70.2.6. I can ping 203.70.2.6. But I can not ping 203.70.2.36 and the main server(203.70.2.4) of my ISP. I ,also tried to delete those add lines in the ppp.conf file. And put them to my ppp.linkup as follows MYADDR: delete ALL add 0 0 203.70.2.4 Still it won't work. I guess there got be something wrong with my routing table. I shall greatly appreciate your help. From owner-freebsd-stable Sun Jan 12 18:35:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA12981 for stable-outgoing; Sun, 12 Jan 1997 18:35:21 -0800 (PST) Received: from nemesis.lonestar.org ([207.136.12.34]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA12942; Sun, 12 Jan 1997 18:35:07 -0800 (PST) Received: by nemesis.lonestar.org (Smail3.1.27.1 #22) id m0vjcEb-000u3fC; Sun, 12 Jan 97 20:34 CST Message-Id: Date: Sun, 12 Jan 97 20:34 CST To: nate@mt.sri.com, freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org, chuckr@glue.umd.edu From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Sun Jan 12 1997, 20:34:48 CST Subject: Re: User ppp not hanging up modem. Cc: uhclem@nemesis.lonestar.org Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk [14]On Sat, 21 Dec 1996 dicen@hooked.net wrote: [14]Note that the standard command "&D3" tells the modem to reset itself when [14]DTR drops. Nate's right, this _is_ standard. I have been modem designs for three years, so you have stepped into an area where I have some expertise. Unfortunately, &D3 is not a standard. EIA 602, the AT command set standard (as opposed to a vendors reference modem standard) includes only &D0, &D1, and &D2. Many major brands including Sportsters, either do not support &D3 or don't store it in EEPROM, making it useless. If available, &D3 or a given modem makers functional equivalent command is the best way to go for all serial modem sessions, since it guarantees that no settings from one call persist to the next. Everybody gets a clean slate. &D2 is the next best available choice. If all you have is &D2, add a ATZ to the hang-up or dial-out script to obtain functionality close to what &D3 would have provided. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" |"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-stable Sun Jan 12 18:43:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA13377 for stable-outgoing; Sun, 12 Jan 1997 18:43:02 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA13341; Sun, 12 Jan 1997 18:42:51 -0800 (PST) Received: from uplink.eng.umd.edu (uplink.eng.umd.edu [129.2.98.181]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id VAA15799; Sun, 12 Jan 1997 21:42:48 -0500 (EST) Received: from localhost (chuckr@localhost) by uplink.eng.umd.edu (8.8.3/8.7.3) with SMTP id VAA13238; Sun, 12 Jan 1997 21:42:47 -0500 (EST) X-Authentication-Warning: uplink.eng.umd.edu: chuckr owned process doing -bs Date: Sun, 12 Jan 1997 21:42:47 -0500 (EST) From: Chuck Robey X-Sender: chuckr@uplink.eng.umd.edu To: Frank Durda IV cc: nate@mt.sri.com, freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: User ppp not hanging up modem. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 12 Jan 1997, Frank Durda IV wrote: > > [14]On Sat, 21 Dec 1996 dicen@hooked.net wrote: > [14]Note that the standard command "&D3" tells the modem to reset itself when > [14]DTR drops. Nate's right, this _is_ standard. > > I have been modem designs for three years, so you have stepped into > an area where I have some expertise. > > Unfortunately, &D3 is not a standard. EIA 602, the AT command set > standard (as opposed to a vendors reference modem standard) includes only > &D0, &D1, and &D2. Many major brands including Sportsters, either do > not support &D3 or don't store it in EEPROM, making it useless. I have a Sportster, the manual is open in front of me, and that's NOT true, it DOES have &D3. If its specified on dialup, then it will work on disconnect (with or without eeprom storage). > > If available, &D3 or a given modem makers functional equivalent command > is the best way to go for all serial modem sessions, since it guarantees > that no settings from one call persist to the next. Everybody gets a > clean slate. > > &D2 is the next best available choice. If all you have is &D2, add a > ATZ to the hang-up or dial-out script to obtain functionality close to > what &D3 would have provided. > > Frank Durda IV |"The Knights who say "LETNi" > or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" > |"A what?" > or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-stable Sun Jan 12 20:24:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA17992 for stable-outgoing; Sun, 12 Jan 1997 20:24:41 -0800 (PST) Received: from RWSystems.net (root@rwsystr.RWSystems.net [204.251.23.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id UAA17987; Sun, 12 Jan 1997 20:24:35 -0800 (PST) Received: from nemesis by RWSystems.net with uucp (Smail3.1.29.1 #3) id m0vjdkz-0001ePC; Sun, 12 Jan 97 22:12 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #22) id m0vjdq6-000tx1C; Sun, 12 Jan 97 22:17 CST Message-Id: Date: Sun, 12 Jan 97 22:17 CST To: chuckr@glue.umd.edu, nate@mt.sri.com, freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Sun Jan 12 1997, 22:17:37 CST Subject: Re: User ppp not hanging up modem. Cc: uhclem@nemesis.lonestar.org Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk [-]Unfortunately, &D3 is not a standard. EIA 602, the AT command set [-]standard (as opposed to a vendors reference modem standard) includes only [-]&D0, &D1, and &D2. Many major brands including Sportsters, either do [-]not support &D3 or don't store it in EEPROM, making it useless. [0]I have a Sportster, the manual is open in front of me, and that's NOT [0]true, it DOES have &D3. If its specified on dialup, then it will work on [0]disconnect (with or without eeprom storage). Yes, the current/recent Sportsters do accept &D3, BUT Sportsters do NOT save the &D3 setting in EEPROM. Try it: ATZ AT&D3 ATI4 (verify that &D3 is there) AT&W (save) ATZ (reset) ATI4 (inspect) It's now &D2. USR argues (badly) that this value doesn't need to be saved permanently. USR says that if you wanted the action &D3 provides, you should add it to your dialing string on each dial-out. Of course, this ignores dial-ins. My current company has been complaining about this and many other Sportster bugs for over a year. We own over 3,000 of them. I personally believe USR ran out of bits in EEPROM and this is one of many settings that don't "stick" over resets and power cycles. I have heard that VERY OLD Sportsters don't have &D3 at all, but I haven't found one that old in the revisions I have access to. Couriers apparently have sufficient EEPROM to correctly hold &D3. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" |"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-stable Mon Jan 13 05:16:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA12031 for stable-outgoing; Mon, 13 Jan 1997 05:16:35 -0800 (PST) Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA12026 for ; Mon, 13 Jan 1997 05:16:32 -0800 (PST) Received: from nixe.ISAR.net by relay.xlink.net id <71553-0@relay.xlink.net>; Mon, 13 Jan 1997 14:15:15 +0000 Received: from m.cht.de (root@urmele.Augsburg.ISAR.net [194.45.233.6]) by nixe.isar.net (8.8.4/8.8.4/ni-2.2) with SMTP id OAA00544; Mon, 13 Jan 1997 14:15:14 +0100 (MET) Received: from mx42.cht.de (mx42.cht.de [194.45.233.2]) by m.cht.de (8.6.12/cht-1.1) with ESMTP id OAA20279; Mon, 13 Jan 1997 14:15:12 +0100 Received: (from paule@localhost) by mx42.cht.de (8.6.12/8.6.12) id OAA01003; Mon, 13 Jan 1997 14:15:11 +0100 Date: Mon, 13 Jan 1997 14:15:11 +0100 Message-Id: <199701131315.OAA01003@mx42.cht.de> From: "Gerd M. Pauli" To: fgray@rice.edu CC: freebsd-stable@freebsd.org Subject: Problems with the 3Com Etherlink XL (PCI) under 2.1.6 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, When using the Etherlink XL Card under FreeBSD 2.1.6, the card seems to be in "Promiscuous mode". It seems, that the function "vxsetfilter" in the file /sys/dev/vx/if_vx.c has no effect ! After reconfiguring the Card with the DOS Utility from 3Com and manually setting the "Network Driver Optimisation" to "Minimal CPU Performance" or "Normal" ,saving the Setup ,and booting FreeBSD the Card works normally. ( Changing of "Promiscuous mode" with vxsetfilter is ok ) But after booting FreeBSD after a power cycle the same Problem is detected. Has anyone an idea how to fix the Problem ? Does anyone has a Documentation describing the Registers of the Chip ? -- Gerd Pauli NIC-Handle: GP40-RIPE CHT Software Service GmbH Internet Access Provider Steinerne Furt 78,D-86167 Augsburg I.S.A.R Netzwerke, NTG Xlink Phone: +49 821 7406-0 Fax: +49 821 7406-100 E-Mail: Gerd.Pauli@CHT.de From owner-freebsd-stable Tue Jan 14 10:26:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA28284 for stable-outgoing; Tue, 14 Jan 1997 10:26:31 -0800 (PST) Received: from gvr.win.tue.nl (gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA28275 for ; Tue, 14 Jan 1997 10:26:18 -0800 (PST) Received: (from guido@localhost) by gvr.win.tue.nl (8.8.4/8.8.2) id TAA03475; Tue, 14 Jan 1997 19:24:55 +0100 (MET) From: Guido van Rooij Message-Id: <199701141824.TAA03475@gvr.win.tue.nl> Subject: Re: Problems with the 3Com Etherlink XL (PCI) under 2.1.6 In-Reply-To: <199701131315.OAA01003@mx42.cht.de> from "Gerd M. Pauli" at "Jan 13, 97 02:15:11 pm" To: paule@CHT.de (Gerd M. Pauli) Date: Tue, 14 Jan 1997 19:24:55 +0100 (MET) Cc: fgray@rice.edu, freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gerd M. Pauli wrote: > Hello, > > When using the Etherlink XL Card under FreeBSD 2.1.6, the card > seems to be in "Promiscuous mode". It seems, that > the function "vxsetfilter" in the file /sys/dev/vx/if_vx.c has no effect ! > After reconfiguring the Card with the DOS Utility from 3Com and manually > setting the "Network Driver Optimisation" to "Minimal CPU Performance" > or "Normal" ,saving the Setup ,and booting FreeBSD the Card works normally. > ( Changing of "Promiscuous mode" with vxsetfilter is ok ) > But after booting FreeBSD after a power cycle the same Problem is detected. > > Has anyone an idea how to fix the Problem ? > Does anyone has a Documentation describing the Registers of the Chip ? Yep I do. Let me see how I can help you. First, could you send me how the device is detected at boot time? That can be found either with the dmesg command or in your log files. Further, I'd like to know how you detect that it is in promiscuous mode. I am thinking of some hardware problem in your system. It is explicitly mentioned in the docs (page 4-46) for RxFilter that it is cleared (i.e. set to receiveIndividual (which is normal operation)) upon reset. Apparently the hard reset stuff does something weird to the card. -Guido From owner-freebsd-stable Wed Jan 15 04:41:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA25742 for stable-outgoing; Wed, 15 Jan 1997 04:41:42 -0800 (PST) Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA25735 for ; Wed, 15 Jan 1997 04:41:36 -0800 (PST) Received: from nixe.ISAR.net by relay.xlink.net id <149205-1@relay.xlink.net>; Wed, 15 Jan 1997 13:40:58 +0000 Received: from m.cht.de (root@urmele.Augsburg.ISAR.net [194.45.233.6]) by nixe.isar.net (8.8.4/8.8.4/ni-2.2) with SMTP id NAA21488; Wed, 15 Jan 1997 13:40:53 +0100 (MET) Received: from mx42.cht.de (mx42.cht.de [194.45.233.2]) by m.cht.de (8.6.12/cht-1.1) with ESMTP id NAA13252; Wed, 15 Jan 1997 13:40:51 +0100 Received: (from paule@localhost) by mx42.cht.de (8.6.12/8.6.12) id NAA06285; Wed, 15 Jan 1997 13:40:50 +0100 Date: Wed, 15 Jan 1997 13:40:50 +0100 Message-Id: <199701151240.NAA06285@mx42.cht.de> From: "Gerd M. Pauli" To: Guido van Rooij Cc: freebsd-stable@freebsd.org Subject: Re: Problems with the 3Com Etherlink XL (PCI) under 2.1.6 In-Reply-To: <199701141824.TAA03475@gvr.win.tue.nl> References: <199701131315.OAA01003@mx42.cht.de> <199701141824.TAA03475@gvr.win.tue.nl> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Guido van Rooij writes: > Yep I do. Let me see how I can help you. Great ! Thanx ! > First, could you send me how the device is detected at boot time? That > can be found either with the dmesg command or in your log files. FreeBSD 2.1.6-RELEASE #4: Mon Jan 13 13:44:05 MET 1997 cht@bastl.cht.de:/usr/src/sys.2.1.6/compile/BASTL CPU: 99-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 16777216 (16384K bytes) avail memory = 14757888 (14412K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 vx0 <3COM 3C900 Etherlink XL PCI> rev 0 int a irq 15 on pci0:10 utp/aui/bnc[*bnc*] address 00:60:97:0b:bf:52 ahc0 rev 0 int a irq 9 on pci0:11 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ....... vga0 rev 0 int a irq 12 on pci0:12 Probing for devices on the ISA bus: ....... npx0 on motherboard npx0: INT 16 interface > Further, I'd like to know how you detect that it is in promiscuous mode. I have ipfw in the kernel and some log filters set, so I can see that the interface vx0 is receiving all packets on the local ethernet :-( The next is that the Machine is sending icmp messages ( net/host unreach. ) > I am thinking of some hardware problem in your system. It is explicitly > mentioned in the docs (page 4-46) for RxFilter that it is cleared > (i.e. set to receiveIndividual (which is normal operation)) upon > reset. The board is an ASUS P/I-P55TP4N Do you know where I can get the docs ? I looked at www.3com.com but could not find the stuff. > Apparently the hard reset stuff does something weird to the card. The Dos Config Program from 3Com for this Card has the answer, I guess. There must be a Config Register which has to be initialized from the Kernel at boot time . -- Gerd Pauli NIC-Handle: GP40-RIPE CHT Software Service GmbH Internet Access Provider Steinerne Furt 78,D-86167 Augsburg I.S.A.R Netzwerke, NTG Xlink Phone: +49 821 7406-0 Fax: +49 821 7406-100 E-Mail: Gerd_Pauli@CHT.de From owner-freebsd-stable Thu Jan 16 12:24:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA11527 for stable-outgoing; Thu, 16 Jan 1997 12:24:54 -0800 (PST) Received: from freefall.anasazi.com ([138.113.128.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA11520 for ; Thu, 16 Jan 1997 12:24:51 -0800 (PST) Received: (from chad@localhost) by freefall.anasazi.com (8.8.3/8.8.3) id NAA02521; Thu, 16 Jan 1997 13:25:17 -0700 (MST) From: "Chad R. Larson" Message-Id: <199701162025.NAA02521@freefall.anasazi.com> Subject: 2.1.6-RELEASE doesn't compile To: freebsd-stable@FreeBSD.org Date: Thu, 16 Jan 1997 13:25:16 -0700 (MST) Cc: chad@chad.anasazi.com Reply-to: chad@anasazi.COM X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I have a machine running 2.1.6-RELEASE loaded via ftp from ftp.FreeBSD.org a few weeks ago. I'm told the CD-ROM arrives today or tomorrow. Yesterday, I changed to /usr/src and typed "make >>& Make.out". About six hours later, this was at the end of my make log: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ===> usr.bin/tn3270/mset cd /usr/src/usr.bin/tn3270/mset/../tools/mkastosc; make /usr/src/usr.bin/tn3270/mset/../tools/mkastosc/obj/mkastosc /usr/src/usr.bin/tn3270/mset/../ctlr/hostctlr.h /usr/src/usr.bin/tn3270/mset/../ctlr/function.h < /usr/src/usr.bin/tn3270/mset/../ctlr/unix.kbd > astosc.OUT /usr/src/usr.bin/tn3270/mset/../tools/mkastosc/obj/mkastosc: not found *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= The problem is that the executable "mkastosc" is in the ../tools/mkastosc directory, not in an "obj" subdirectory. It seems to me I would have three options at this point: 1) create an ./obj/mkastosc under the mkastosc directory 2) edit the Makefile in /usr/src/usr.bin/tn3270/mset to correct the path to the executable 3) Use "sup" to sync the usr.bin/tn3270 directory tree against the stable tree to see if someone has already fixed this. What would you suggest? And am I correct in assuming that the "stable" CVS tree is, in fact, the 2.1.6-RELEASE tree with bug fixes generated since 2.1.6 was declared to be "release"? Would I want to sync my entire /usr/src tree? -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 From owner-freebsd-stable Fri Jan 17 04:38:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA27236 for stable-outgoing; Fri, 17 Jan 1997 04:38:10 -0800 (PST) Received: from bcc01.burton-computer.com (bcc01.burton-computer.com [207.79.89.66]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA27231 for ; Fri, 17 Jan 1997 04:38:08 -0800 (PST) Received: (from brian@localhost) by bcc01.burton-computer.com (8.8.3/8.8.3) id HAA23947; Fri, 17 Jan 1997 07:38:02 -0500 (EST) Date: Fri, 17 Jan 1997 07:38:02 -0500 (EST) Message-Id: <199701171238.HAA23947@bcc01.burton-computer.com> From: Brian Burton To: chad@anasazi.COM CC: freebsd-stable@FreeBSD.ORG, chad@chad.anasazi.com In-reply-to: <199701162025.NAA02521@freefall.anasazi.com> (chad@freefall.anasazi.com) Subject: Re: 2.1.6-RELEASE doesn't compile Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: "Chad R. Larson" > Date: Thu, 16 Jan 1997 13:25:16 -0700 (MST) > Cc: chad@chad.anasazi.com > Reply-to: chad@anasazi.COM > > I have a machine running 2.1.6-RELEASE loaded via ftp from ftp.FreeBSD.org > a few weeks ago. I'm told the CD-ROM arrives today or tomorrow. > > Yesterday, I changed to /usr/src and typed "make >>& Make.out". > About six hours later, this was at the end of my make log: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > The problem is that the executable "mkastosc" is in the > ../tools/mkastosc directory, not in an "obj" subdirectory. > > It seems to me I would have three options at this point: > 1) create an ./obj/mkastosc under the mkastosc directory > 2) edit the Makefile in /usr/src/usr.bin/tn3270/mset to correct > the path to the executable > 3) Use "sup" to sync the usr.bin/tn3270 directory tree against > the stable tree to see if someone has already fixed this. > > What would you suggest? > I would suggest 3. I installed 2.1.6-RELEASE on Monday and supped stable on Wednesday. I successfully did a make world last night (3 hours on a Pentium 166 with 64MB). > > And am I correct in assuming that the "stable" CVS tree is, in fact, the > 2.1.6-RELEASE tree with bug fixes generated since 2.1.6 was declared to > be "release"? Would I want to sync my entire /usr/src tree? > Yes. According to the handbook, stable is a bug fix channel for release. I supped the entire tree except for DES. ++Brian -- Brian Burton Burton Computer Corp. brian@burton-computer.com 14315 National Highway Suite 340 "This space intentionally left blank." La Vale, MD 21502