From owner-freebsd-stable Sun Jul 14 02:12:38 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA09881 for stable-outgoing; Sun, 14 Jul 1996 02:12:38 -0700 (PDT) Received: from scapa.cs.ualberta.ca (root@scapa.cs.ualberta.ca [129.128.4.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA09863 for ; Sun, 14 Jul 1996 02:12:34 -0700 (PDT) Received: from ve6kik by scapa.cs.ualberta.ca with UUCP id <13079-3651>; Sun, 14 Jul 1996 03:12:26 -0700 Received: from alive.ampr.ab.ca by ve6kik.ampr.ab.ca with uucp (Smail3.1.28.1 #5) id m0ufMwP-000O4PC; Sun, 14 Jul 96 02:54 WET DST Received: by alive.ampr.ab.ca (Linux Smail3.1.29.1 #2) id m0ufLHo-000292C; Sun, 14 Jul 96 01:08 MDT Date: Sun, 14 Jul 1996 01:08:10 -0600 (MDT) From: Marc Slemko To: freebsd-stable@freebsd.org Subject: vi sometimes core dumps when scrolling with 'set list' Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have noticed that sometimes vi will core dump when viewing a file with 'set list'. It seems to happen right when it tries to display the '$' at the end of a line which ends up being exactly 80 characters long before the '$'. For an example, try using /sys/scsi/st.c version 1.36.4.5; nothing special about this file, just a random example. Make sure you have your screen set for 80 columns. Do a ':set list', then scroll down. Line 185 displays fine for me (as long as you go down line by line), but going down one more line where the '$' should be for the end of line causes the core dump. This has been observed in stable as of a couple of days ago, and stable of a couple of weeks ago. 2.1.0-RELEASE doesn't seem to have this problem, but it wasn't compiled here. I don't know about current. This doesn't necessarily look to be a problem in vi, and it may not even be a real problem with anything except the way things are being compiled. Making slight modifications to the source (ie. changing one line, compiling, changing it back, then recompiling) or compile flags (once when I added a -g to get some debugging info the problem went away) can eliminate the problem. It is on two systems here running stable, built from independent source trees, but it may not be on all systems. There don't appear to have been any changes in the vi source tree between 2.1.0 and 2.1.5. I have not had time to actually look at the vi source much to see if it looks to be at fault. Any ideas? Some gdb output: Core was generated by `nvi'. Program terminated with signal 11, Segmentation fault. #0 0x312b6 in svi_line (sp=0x3f800, ep=0x45080, smp=0x5bdcc, yp=0x0, xp=0x0) at /usr/var/tmp/vi/common/../svi/svi_line.c:376 376 smp->c_ecsize = smp->c_eclen = KEY_LEN(sp, ch); (gdb) where #0 0x312b6 in svi_line (sp=0x3f800, ep=0x45080, smp=0x5bdcc, yp=0x0, xp=0x0) at /usr/var/tmp/vi/common/../svi/svi_line.c:376 #1 0x34695 in svi_sm_1up (sp=0x3f800, ep=0x45080) at /usr/var/tmp/vi/common/../svi/svi_smap.c:766 #2 0x34440 in svi_sm_up (sp=0x3f800, ep=0x45080, rp=0xefbfd48c, count=4, scmd=CNTRL_D, smp=0x5bc00) at /usr/var/tmp/vi/common/../svi/svi_smap.c:663 #3 0x340e4 in svi_sm_scroll (sp=0x3f800, ep=0x45080, rp=0xefbfd48c, count=12, scmd=CNTRL_D) at /usr/var/tmp/vi/common/../svi/svi_smap.c:535 #4 0x28644 in v_hpagedown (sp=0x3f800, ep=0x45080, vp=0xefbfd464) at /usr/var/tmp/vi/common/../vi/v_scroll.c:332 #5 0x2e48f in vi (sp=0x3f800, ep=0x45080) at /usr/var/tmp/vi/common/../vi/vi.c:200 #6 0x32f24 in svi_screen_edit (sp=0x3f800, ep=0x45080) at /usr/var/tmp/vi/common/../svi/svi_screen.c:225 #7 0x580c in main (argc=2, argv=0xefbfda24) at main.c:435 -- Marc Slemko 1:342/1003@fidonet marcs@alive.ampr.ab.ca marcs@alive.ersys.edmonton.ab.ca From owner-freebsd-stable Sun Jul 14 04:53:36 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA17578 for stable-outgoing; Sun, 14 Jul 1996 04:53:36 -0700 (PDT) Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA17554 for ; Sun, 14 Jul 1996 04:53:30 -0700 (PDT) Received: from 199.183.109.242 by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Sun, 14 Jul 1996 06:53:23 -0600 Message-ID: Date: 14 Jul 1996 06:53:06 -0500 From: "Richard Wackerbarth" Subject: CTM files for 2.1.5 Release Available To: "freebsd-stable@freebsd.org" X-Mailer: Mail*Link PT/Internet 1.6.0 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For those of you tracking the -stable source tree via ctm, update #146 represents the 2.1.5-RELEASE tree. Additional updates will continue to reflect any subsequent changes. -- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-stable Sun Jul 14 10:02:32 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01299 for stable-outgoing; Sun, 14 Jul 1996 10:02:32 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA01217; Sun, 14 Jul 1996 10:02:23 -0700 (PDT) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id MAA08234; Sun, 14 Jul 1996 12:02:03 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Sun, 14 Jul 96 12:02 CDT Date: Sun, 14 Jul 1996 12:02:02 -0500 (CDT) From: Alex Nash X-Sender: nash@Venus.mcs.com To: michael butler cc: current@freebsd.org, nate@mt.sri.com, stable@freebsd.org Subject: Re: ep driver now unstable .. In-Reply-To: <199607141629.CAA00572@walkabout.asstdc.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Crossposted from current, please direct followups back to current ] On Mon, 15 Jul 1996, michael butler wrote: > Whatever changed in the last day or so in the ep driver has now resulted in > the same symptoms as I had with the nep driver on my laptop. Intermittently, > it'll just stop working and I have to use "ifconfig ep0 down; ifconfig ep0 > up" to make it go again, Yep, ep is broken (and unfortunately it's in 2.1.5). If you have the CVS archive, checkout rev 1.28.4.5 of if_ep.c for -stable, or rev 1.49 for -current. If you don't have the CVS archive, change: outw(BASE + EP_W1_TX_PIO_WR_1, len | 0x8000); /* XXX */ to outw(BASE + EP_W1_TX_PIO_WR_1, len); (line 775 for 2.1.5, line 967 for -current) Alex From owner-freebsd-stable Sun Jul 14 12:59:09 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA07183 for stable-outgoing; Sun, 14 Jul 1996 12:59:09 -0700 (PDT) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA07160 for ; Sun, 14 Jul 1996 12:59:03 -0700 (PDT) Received: (from robinson@localhost) by public.bta.net.cn (8.6.8.1/8.6.9) id DAA02769 for stable@freebsd.org; Mon, 15 Jul 1996 03:58:59 +0800 Date: Mon, 15 Jul 1996 03:58:59 +0800 From: Michael Robinson Message-Id: <199607141958.DAA02769@public.bta.net.cn> To: stable@freebsd.org Subject: xterm won't load Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just did a "brute force" upgrade from 2.0.5 to 2.1.5. Everything went fine except for the following wierd problem. The X server (SVGA) and twm will start up, and run xclock, but any attempt to load an xterm results in this error message: xterm: Error 23, errno 25: Inappropriate ioctl for device So, what did I break? Thanks. -Michael Robinson From owner-freebsd-stable Sun Jul 14 14:33:01 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25927 for stable-outgoing; Sun, 14 Jul 1996 14:33:01 -0700 (PDT) Received: from bdd.net (bdd.net [207.61.119.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25904 for ; Sun, 14 Jul 1996 14:32:54 -0700 (PDT) Received: from localhost (matt@localhost) by bdd.net (8.7.5/8.7.3) with SMTP id RAA29112; Sun, 14 Jul 1996 17:32:37 -0400 (EDT) Date: Sun, 14 Jul 1996 17:32:37 -0400 (EDT) From: Matthew Stein To: Michael Robinson cc: stable@FreeBSD.ORG Subject: Re: xterm won't load In-Reply-To: <199607141958.DAA02769@public.bta.net.cn> 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 Mon, 15 Jul 1996, Michael Robinson wrote: > will start up, and run xclock, but any attempt to load an xterm results in > this error message: > > xterm: Error 23, errno 25: Inappropriate ioctl for device Check your kernel config. For xterms, you need to have ... options "COMPAT_43" ...in there, as the xterm code still requires it. It's a compatibility with BSD 4.3 tag, and should solve your problem. Let me know if it helped! -- mat. +-Matthew Stein-------------------------------------------- matt@bdd.net-+ | Network Design phone: +1 519 823-8577 | | ButtonDown Digital fax: +1 519 823-9556 | +------------------------------------------------------------------------+ From owner-freebsd-stable Sun Jul 14 22:23:44 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA29900 for stable-outgoing; Sun, 14 Jul 1996 22:23:44 -0700 (PDT) Received: from bdd.net (bdd.net [207.61.119.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA29877; Sun, 14 Jul 1996 22:23:37 -0700 (PDT) Received: from localhost (matt@localhost) by bdd.net (8.7.5/8.7.3) with SMTP id BAA02809; Mon, 15 Jul 1996 01:23:34 -0400 (EDT) Date: Mon, 15 Jul 1996 01:23:34 -0400 (EDT) From: Matthew Stein Reply-To: Matthew Stein To: freebsd-stable@freebsd.org, freebsd-multimedia@freebsd.org Subject: Quickcam driver help? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been struggling with the Connectix Quickcam driver for a little while, and was wondering if anyone has any tips that might help getting it to work. Right now, my lpt0 comes up alright, and is fully functional, but the Quickcam driver doesn't. Here's the boot log. lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port qcam0 not found at 0x378 I know that it's functional because running Windows on the same machine, worked fine with the quickcam. Here's the two kernel config lines that apply. # device lpt0 at isa? port? tty irq 7 vector lptintr device qcam0 at isa? port "IO_LPT1" conflicts tty What should I be looking for here? I've tried many combinations of BIOS setting for the port, and keeping the printer port in and out. Ideas? -- mat. +-Matthew Stein-------------------------------------------- matt@bdd.net-+ | Network Design phone: +1 519 823-8577 | | ButtonDown Digital fax: +1 519 823-9556 | +------------------------------------------------------------------------+ From owner-freebsd-stable Sun Jul 14 23:54:00 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA06662 for stable-outgoing; Sun, 14 Jul 1996 23:54:00 -0700 (PDT) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA06653 for ; Sun, 14 Jul 1996 23:53:56 -0700 (PDT) Received: (from robinson@localhost) by public.bta.net.cn (8.6.8.1/8.6.9) id OAA25240; Mon, 15 Jul 1996 14:53:21 +0800 Date: Mon, 15 Jul 1996 14:53:21 +0800 From: Michael Robinson Message-Id: <199607150653.OAA25240@public.bta.net.cn> To: matt@bdd.net Subject: Re: xterm won't load Cc: stable@FreeBSD.ORG Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From matt@bdd.net Mon Jul 15 05:32:42 1996 >Received: from bdd.net (bdd.net [207.61.119.1]) by public.bta.net.cn (8.6.8.1/8.6.9) with ESMTP id FAA04233 for ; Mon, 15 Jul 1996 05:32:39 +0800 >Received: from localhost (matt@localhost) by bdd.net (8.7.5/8.7.3) with SMTP id RAA29112; Sun, 14 Jul 1996 17:32:37 -0400 (EDT) >Date: Sun, 14 Jul 1996 17:32:37 -0400 (EDT) >To: Michael Robinson >cc: stable@FreeBSD.ORG >Subject: Re: xterm won't load >In-Reply-To: <199607141958.DAA02769@public.bta.net.cn> >Message-ID: >MIME-Version: 1.0 >Content-Type: TEXT/PLAIN; charset=US-ASCII >Status: RO Matthew Stein wrote: >On Mon, 15 Jul 1996, Michael Robinson wrote: >> xterm: Error 23, errno 25: Inappropriate ioctl for device > >Check your kernel config. For xterms, you need to have ... > >options "COMPAT_43" Verily! Well, except for that minor glitch, 2.0.5 to 2.1.5 is a win (because I remembered to back up my XF86Config; probably that, and the COMPAT_43 requirement should be more prominently documented). Kudos on the fixed psm driver, which finally enables me to run Tcl/Tk, bitmap, etc., on my Toshiba. Also kudos on the newly useful /stand/sysinstall, which got me up and running over a 64Kbps line faster than I would have thought possible (some kind of persistant state storage would be nice, though, so you wouldn't have to enter all the config information from scratch every time). As soon as I figure out how to get the PCMCIA support working for my modem I'll probably donate a chunk of cash to the cause, such will be my state of delirious joy. -Michael Robinson From owner-freebsd-stable Mon Jul 15 00:06:25 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA08065 for stable-outgoing; Mon, 15 Jul 1996 00:06:25 -0700 (PDT) Received: from acc0.elvisti.kiev.ua (acc0.elvisti.kiev.ua [193.125.28.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA07874 for ; Mon, 15 Jul 1996 00:04:57 -0700 (PDT) Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by acc0.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id KAA26260; Mon, 15 Jul 1996 10:06:17 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id KAA00739; Mon, 15 Jul 1996 10:06:17 +0300 From: "Andrew V. Stesin" Message-Id: <199607150706.KAA00739@office.elvisti.kiev.ua> Subject: Re: Memory leak in 1.0.1 / FreeBSD 2.1R & BSDI To: stefan@netscafe.rotterdam.luna.net (Stefan Arentz) Date: Mon, 15 Jul 1996 10:06:16 +0300 (EET DST) Cc: squid-users@nlanr.net, stable@freebsd.org In-Reply-To: <199607142159.XAA01121@netscafe.rotterdam.luna.net> from "Stefan Arentz" at Jul 14, 96 11:59:53 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi people, that's me who did an "official" FreeBSD port, and we don't see any such problems here. BUT: we are running Squid on a FreeBSD-stable machine with malloc() taken from FreeBSD-current (so called phkmalloc). I'll be grateful to see the results of the testing. # Eric, # # Danny ter Haar send me the following private message: # # >From: Danny ter Haar # >Subject: Re: Memory leak in 1.0.1 / FreeBSD 2.1R # > # >An other provider running BSD and squid had the same problem: # >After compiling with the linux malloc everything worked like a charm # > # >Danny # # So i installed libdlmalloc-2.5 from the FreeBSD packages collection. I'm now # running a squid binary linked with that library. I'll post the results on # tuesday I think. # # Regards, # - Stefan # # Your message dated: Sun, 14 Jul 1996 23:24:41 +0200 # >At 22:05 14/07/1996 +0200, Stefan Arentz wrote: # > # >>> top -b | grep squid # >>> 23351 root 2 0 13M 6365K sleep 9:40 0.00% 0.00% squid # >>> # >>> and Total Accounted was 10092KB. # >>> # >>> This is on a squid-1.0.1 system running on FreeBSD-2.1-stable. # >>> # >>> Personally I wouldn't be worried about the discrepencies in your # >>> figures until they affect your system in some manor. # >> # >>If it's broken then it should be fixed imho. I'm running squid on a web # >>server and cant afford to let squid crash this machine... Four days ago # >>squid was using 42MB of memory while there was just 20MB cached on disk.. # >> # >>I'll track this down. It looks like a memory leak somewhere... # >> # > # >Since the Jul 8th, 1996: # >I run squid 1.0.1 on a 128 MB central server running BSDI. # >Process squid grows steadily in memory (we have over 17.000 users) until it # >reaches Datasize memory limit then "crashes" (xxalloc can't alloc 4096 bytes # >of memory). # > # >I run squid 1.0.1 on a neighbor server handling requests, from the above # >server, that are related to US sites: So far, so good. # > # >Since the "squid" source has been passed through "purify", I would think the # >memory leak is real but doesn't show up until some error condition occurs. # > # >Most errors reported in "cache.log" are related to the following source # >lines: # > # >* comm.c : 372 # >* comm.c : 1194 # > # >ftpget.c: 652 # > # >ipc.c : 1158 # >ipc.c : 1375 # >* ipc.c : 1887 # >ipc.c : 1862 # > # >* outlines the most common errors. # > # >Hope it will help. I'll try to spend some time around those lines. # >Best regards, # >Eric Salome # > # > # -- With best regards -- Andrew Stesin. Phones/fax: +380 (44) { 244-0122, 276-0188, 271-3457, 271-3560 } "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-stable Mon Jul 15 07:40:42 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA14129 for stable-outgoing; Mon, 15 Jul 1996 07:40:42 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA14117 for ; Mon, 15 Jul 1996 07:40:35 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA18617; Mon, 15 Jul 1996 08:40:12 -0600 (MDT) Date: Mon, 15 Jul 1996 08:40:12 -0600 (MDT) Message-Id: <199607151440.IAA18617@rocky.mt.sri.com> From: Nate Williams To: Michael Robinson Cc: stable@freebsd.org Subject: Re: xterm won't load In-Reply-To: <199607150653.OAA25240@public.bta.net.cn> References: <199607150653.OAA25240@public.bta.net.cn> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well, except for that minor glitch, 2.0.5 to 2.1.5 is a win (because I > remembered to back up my XF86Config; probably that, and the COMPAT_43 > requirement should be more prominently documented). > > Kudos on the fixed psm driver, which finally enables me to run Tcl/Tk, > bitmap, etc., on my Toshiba. Umm, I don't think we've done much with the psm driver since 2.0.5, but if it works congratulations! > As soon as I figure out how to get the PCMCIA support working for my modem > I'll probably donate a chunk of cash to the cause, such will be my state of > delirious joy. 2.1.5 doesn't have PCMCIA support enabled. The PCMCIA chipset code actually exists, but none of the PCMCIA specific drivers nor the userland code is in 2.1.5. You'll need to run -current, or at least hack in patches into 2.1.5. Nate From owner-freebsd-stable Mon Jul 15 07:44:09 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA14322 for stable-outgoing; Mon, 15 Jul 1996 07:44:09 -0700 (PDT) Received: from acc0.elvisti.kiev.ua (acc0.elvisti.kiev.ua [193.125.28.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA14293 for ; Mon, 15 Jul 1996 07:43:38 -0700 (PDT) Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by acc0.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id RAA01690; Mon, 15 Jul 1996 17:45:26 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id RAA22557; Mon, 15 Jul 1996 17:45:26 +0300 From: "Andrew V. Stesin" Message-Id: <199607151445.RAA22557@office.elvisti.kiev.ua> Subject: Re: Memory leak in 1.0.1 / FreeBSD 2.1R & BSDI To: map@iphil.net (Miguel A.L. Paraz) Date: Mon, 15 Jul 1996 17:45:26 +0300 (EET DST) Cc: stesin@elvisti.kiev.ua, squid-users@nlanr.net, stable@freebsd.org In-Reply-To: <199607151250.UAA12011@marikit.iphil.net> from "Miguel A.L. Paraz" at Jul 15, 96 08:50:58 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello Miguel and Squiders, # I'm also running 2.1R on the main caching machine. # The kernel tends to panic very often (around once a day), though. # I've *never* been able to catch the exact error, it's not logged to # syslog. However, the server is performing other functions as well. 2.1R is great -- but it's stability heavily depends on the hardware configuration. Many "interesting" conditions were fixed since that time by the core team, especially in the drivers. We have seen occasional crashes with plain 2.1R on some of our boxes; after an upgrade to a late March -stable _all_ machines are rock solid, nothing can crash them. # # I'll try changing the malloc(). However, I feel that upgrading to # FreeBSD 2.1.5 will help, and I'm waiting for it. 2.1.5 is already here, BTW (check ftp://ftp.freebsd.org/pub/FreeBSD ) As for me, I strongly suggest you doing both steps: upgrade an OS to 2.1.5 and recompile and reinstall libc with a pkhmalloc (take malloc.c from -current sources). Long ago I was impressed by the improvement phkmalloc gave me, but the -stable developers refused to retrofit this wonderful thing to a -stable branch :-( # Right now I'm not # inclined to upgrading to the interim versions, whether SNAPs or # STABLEs. I understand you, but let me note you aren't right here. -stable snapshots might be considered as an interim bugfix releases to 2.1R (instaed of patchkits) and I must noter that upgrade from 2.1R to -stable was painless. The above should also be true for 2.1R -> 2.1.5R path. Good luck! # # -- # miguel a.l. paraz / iphil communications / PGP keyID 0x43F0D011 # # # # -- With best regards -- Andrew Stesin. Phones/fax: +380 (44) { 244-0122, 276-0188, 271-3457, 271-3560 } "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-stable Mon Jul 15 09:02:19 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19397 for stable-outgoing; Mon, 15 Jul 1996 09:02:19 -0700 (PDT) Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA19378 for ; Mon, 15 Jul 1996 09:02:13 -0700 (PDT) Received: (from news@localhost) by haywire.DIALix.COM (8.7.5/8.7.3) id AAA16652 for freebsd-stable@freebsd.org; Tue, 16 Jul 1996 00:02:08 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-stable@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-stable@freebsd.org Date: 15 Jul 1996 16:02:08 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <4sdq20$b43$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199607120110.TAA21879@rover.village.org> Subject: Re: Uptime report Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199607120110.TAA21879@rover.village.org>, imp@village.org (Warner Losh) writes: > Like I said, at this point, I'm willing just to chalk it up to my > getting a not quite stable -stable kernel and see if I have similar > problems with the -current kernel/system that I'll be building while I > sleep tonight. [*] Any chance you use a MFS /tmp? That consumes lots of swap and doesn't give it back once you delete files. (it faults the pages in, and once they are "allocated" they are never freed.) Try unmounting /tmp and see if that brings it back. (beware any files will disappear). -Peter From owner-freebsd-stable Mon Jul 15 12:04:19 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01869 for stable-outgoing; Mon, 15 Jul 1996 12:04:19 -0700 (PDT) Received: from empire.ucnet.hinet.net (empire.ucnet.hinet.net [202.39.252.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01801 for ; Mon, 15 Jul 1996 12:03:59 -0700 (PDT) Received: (from roylin@localhost) by empire.ucnet.hinet.net (8.7.5/8.7.3) id DAA00613; Tue, 16 Jul 1996 03:05:03 +0800 (CST) Date: Tue, 16 Jul 1996 03:05:03 +0800 (CST) From: Roy Lin To: freebsd-stable@freebsd.org Subject: Re: worm device Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi I add the "device worm0 at scbus?" to my kernel config file and make a new kernel, but appear the error messages. cc -O -m486 -pipe -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -nostdinc -I. -I../.. -I../../sys -I../../../include -DLOCAL -DI586_CPU -DI486_CPU -DATAPI -DSYSVMSG -DSYSVSEM -DSYSVSHM -DOPEN_MAX=128 -DCHILD_MAX=128 -DUCONSOLE -DBOUNCE_BUFFERS -DSCSI_DELAY=15 -DCOMPAT_43 -DPROCFS -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 -c vers.c loading kernel conf.o: Undefined symbol `_wormopen' referenced from data segment conf.o: Undefined symbol `_wormclose' referenced from data segment conf.o: Undefined symbol `_wormioctl' referenced from data segment conf.o: Undefined symbol `_wormstrategy' referenced from data segment *** Error code 1 Stop. Why? Does FreeBSD-stable support worm (CD-R) device? Please give me some suggestions! Roy From owner-freebsd-stable Mon Jul 15 16:04:48 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26763 for stable-outgoing; Mon, 15 Jul 1996 16:04:48 -0700 (PDT) Received: from burnout.cts.com (root@burnout.cts.com [205.163.23.25]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA26756 for ; Mon, 15 Jul 1996 16:04:46 -0700 (PDT) Received: from io.cts.com (io.cts.com [198.68.174.34]) by burnout.cts.com (8.6.12/8.6.9) with ESMTP id QAA26649 for ; Mon, 15 Jul 1996 16:04:44 -0700 Received: (from mdavis@localhost) by io.cts.com (8.7.5/8.6.9) id QAA00327 for stable@freebsd.org; Mon, 15 Jul 1996 16:04:30 -0700 (PDT) From: Morgan Davis Message-Id: <199607152304.QAA00327@io.cts.com> Subject: can't build GENERIC To: stable@freebsd.org Date: Mon, 15 Jul 1996 16:04:30 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL19 (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 With the 2.1.5R out now, I have supped -stable, made world, made a new custom kernel, and rebooted. I'm up on 2.1.5-RELEASE now, according to my /etc/motd, and I thought it would be a good idea to build a new generic kernel now just for safety purposes. But it doesn't want to build: # cd /usr/src/sys/i386/conf # config GENERIC # cd ../../compile/GENERIC # make depend # make cc -c -O -pipe -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -nostdinc -I. -I../.. -I../../sys -I../../../include -DGENERIC -DI586_CPU -DI486_CPU -DI386_CPU -DATAPI -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUCONSOLE -DBOUNCE_BUFFERS -DSCSI_DELAY=15 -DCOMPAT_43 -DPROCFS -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DMATH_EMULATE -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 ../../i386/isa/matcd/matcd.c In file included from ../../i386/isa/matcd/matcd.c:354: ../../i386/isa/matcd/matcddrv.h:171: redefinition of `matcderrors' ../../i386/isa/matcd/matcd.h:171: `matcderrors' previously defined here ../../i386/isa/matcd/matcd.c:437: `NMATCD' undeclared here (not in a function) ../../i386/isa/matcd/matcd.c:437: size of array `matcd_data' has non-integer type ../../i386/isa/matcd/matcd.c:461: `NMATCD' undeclared here (not in a function) ../../i386/isa/matcd/matcd.c:485: `NMATCD' undeclared here (not in a function) ../../i386/isa/matcd/matcd.c:485: size of array `kdc_matcd' has non-integer type ../../i386/isa/matcd/matcd.c: In function `matcdopen': ../../i386/isa/matcd/matcd.c:639: `NMATCD' undeclared (first use this function) ../../i386/isa/matcd/matcd.c:639: (Each undeclared identifier is reported only once ../../i386/isa/matcd/matcd.c:639: for each function it appears in.) ../../i386/isa/matcd/matcd.c: In function `matcdclose': ../../i386/isa/matcd/matcd.c:830: `NMATCD' undeclared (first use this function) ../../i386/isa/matcd/matcd.c: In function `matcdstrategy': ../../i386/isa/matcd/matcd.c:896: `NMATCD' undeclared (first use this function) ../../i386/isa/matcd/matcd.c: In function `matcd_probe': ../../i386/isa/matcd/matcd.c:1255: `NMATCD' undeclared (first use this function) ../../i386/isa/matcd/matcd.c: In function `matcd_blockread': ../../i386/isa/matcd/matcd.c:1915: warning: `dp' might be used uninitialized in this function *** Error code 1 Ideas? From owner-freebsd-stable Mon Jul 15 17:07:08 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA01810 for stable-outgoing; Mon, 15 Jul 1996 17:07:08 -0700 (PDT) Received: from platinum.com (gateway.platinum.com [206.214.170.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA01801 for ; Mon, 15 Jul 1996 17:07:06 -0700 (PDT) Received: from mailhub.platinum.com ([172.17.26.25]) by gateway.platinum.com with ESMTP id <18647-2>; Mon, 15 Jul 1996 19:05:56 -0500 Received: from bigbert.vt.platinum.com by mailhub.platinum.com (8.7.4/) id TAA03430; Mon, 15 Jul 1996 19:05:23 -0500 (CDT) Received: from doh.vt.platinum.com by bigbert.vt.platinum.com (8.7.3/NX3.0S) id TAA08277; Mon, 15 Jul 1996 19:09:59 -0500 (CDT) From: "Brent J. Nordquist" Received: by doh.vt.platinum.com (8.6.12) id TAA06496; Mon, 15 Jul 1996 19:01:33 -0500 Message-Id: <199607160001.TAA06496@doh.vt.platinum.com> Subject: 2.1.5-RELEASE: Can't get out to the network To: freebsd-stable@freebsd.org Date: Mon, 15 Jul 1996 19:01:33 -0500 Reply-to: nordquist@platinum.com (Brent J. Nordquist) X-Mailer: ELM [version 2.4 PL23] 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 Congratulations to the FreeBSD team on getting 2.1.5 out the door! All the hard work in keeping FreeBSD -stable (while still trying to keep it -current) is greatly appreciated! [I'm assuming that -stable is the place to post about 2.1.5-RELEASE. ;-) ] I was running the 2.1-960627-SNAP "beta" version (with its kernel). I pulled down just the sources for 2.1.5-RELEASE, and did a make world plus a kernel build+install. The compile went flawlessly. Since GENERIC didn't change between beta and final, I used my same kernel config from the beta. Now that I've rebooted the machine, I can't get out to the network any more. DNS and NIS both wait long times before failing. The syslog is producing an NIS-related message at a rate of about 40k lines/10 minutes. The nub of the problem appears to be the output from ping. ping to localhost (lo0) works fine, but to any network address (ep0) I get: ping: sendto: No buffer space available ping: Wrote [host] 64 chars, ret=-1 The routing table (netstat -r) looks the same as it did before. (I'm not using routed/gated.) A search in /etc revealed no files of interest that have changed today (i.e., since/during the compile). Is this a -RELEASE problem? Any ideas where I could start looking? Thanks in advance for any help... -- Brent J. Nordquist PLATINUM technology, inc. (ViaTech Development Lab) nordquist@platinum.com 2600 Eagan Woods Dr., Suite 410, Eagan, MN 55121-1152 Voice +1 612 688-3033 Which is worse: ignorance or apathy? Vmail +1 708 620-5116 ...Who knows? (ext. 7806) ...Who cares? From owner-freebsd-stable Mon Jul 15 17:19:13 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA03056 for stable-outgoing; Mon, 15 Jul 1996 17:19:13 -0700 (PDT) Received: from platinum.com (gateway.platinum.com [206.214.170.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA03047 for ; Mon, 15 Jul 1996 17:19:10 -0700 (PDT) Received: from mailhub.platinum.com ([172.17.26.25]) by gateway.platinum.com with ESMTP id <18647-3>; Mon, 15 Jul 1996 19:18:12 -0500 Received: from bigbert.vt.platinum.com by mailhub.platinum.com (8.7.4/) id TAA03635; Mon, 15 Jul 1996 19:17:40 -0500 (CDT) Received: from doh.vt.platinum.com by bigbert.vt.platinum.com (8.7.3/NX3.0S) id TAA26943; Mon, 15 Jul 1996 19:22:14 -0500 (CDT) From: "Brent J. Nordquist" Received: by doh.vt.platinum.com (8.6.12) id TAA06533; Mon, 15 Jul 1996 19:13:49 -0500 Message-Id: <199607160013.TAA06533@doh.vt.platinum.com> Subject: Irony [was: 2.1.5-RELEASE: Can't get out to the network] To: freebsd-stable@freebsd.org Date: Mon, 15 Jul 1996 19:13:49 -0500 Reply-to: nordquist@platinum.com (Brent J. Nordquist) X-Mailer: ELM [version 2.4 PL23] 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 hit send, 15 seconds later "ding-dong" (new mail arriving). Ah! The freebsd-stable-digest! Let's see here... instability in the ep driver... You can put my previous post in "Wally's pile of perpetual ignorage" (don't touch it with your hands). Just don't anyone accuse me of using -stable without reading the mailing list! I just have a little latency problem. ;-) -- Brent J. Nordquist PLATINUM technology, inc. (ViaTech Development Lab) nordquist@platinum.com 2600 Eagan Woods Dr., Suite 410, Eagan, MN 55121-1152 Voice +1 612 688-3033 Which is worse: ignorance or apathy? Vmail +1 708 620-5116 ...Who knows? (ext. 7806) ...Who cares? From owner-freebsd-stable Mon Jul 15 17:20:53 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA03284 for stable-outgoing; Mon, 15 Jul 1996 17:20:53 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA03275 for ; Mon, 15 Jul 1996 17:20:51 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id RAA17535; Mon, 15 Jul 1996 17:20:41 -0700 (PDT) To: nordquist@platinum.com (Brent J. Nordquist) cc: freebsd-stable@freebsd.org Subject: Re: 2.1.5-RELEASE: Can't get out to the network In-reply-to: Your message of "Mon, 15 Jul 1996 19:01:33 CDT." <199607160001.TAA06496@doh.vt.platinum.com> Date: Mon, 15 Jul 1996 17:20:41 -0700 Message-ID: <17533.837476441@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is this a -RELEASE problem? Any ideas where I could start looking? KNOWNBUG.TXT :-( Jordan From owner-freebsd-stable Mon Jul 15 18:40:21 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA11571 for stable-outgoing; Mon, 15 Jul 1996 18:40:21 -0700 (PDT) Received: from optim.ism.net ([205.199.12.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA11550; Mon, 15 Jul 1996 18:40:16 -0700 (PDT) Received: from optim.ism.net (jdc@optim.ism.net [205.199.12.2]) by optim.ism.net (8.6.12/8.6.12) with SMTP id TAA03803; Mon, 15 Jul 1996 19:56:07 -0600 Date: Mon, 15 Jul 1996 19:56:07 -0600 (MDT) From: John-David Childs To: freebsd-stable@freebsd.org cc: freebsd-questions@freebsd.org Subject: pwd_mkdb bug in 2.1.5? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've got a 2.1.-RELEASE system and a newly installed 2.1.5 system. I ftp'd a copy of the master.passwd file from -RELEASE to 2.1.5 and ran pwd_mkdb -p (I do this regularly between BSDi 2.01 and the -RELEASE machine). Fortunately, I did a 'passwd root' before logging out, because NONE of the other userid's work (bad passwords). Anyone else have the same problem or should I do another 'make world'??? -- John-David Childs www.marsweb.com/www.ism.net System Administrator Internet Services Montana (406)721-6277 & Network Engineer M@RSWeb - Montana's PREMIER Web Site "I used up all my sick days...so I'm calling in dead" From owner-freebsd-stable Mon Jul 15 20:14:31 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA22660 for stable-outgoing; Mon, 15 Jul 1996 20:14:31 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA22628; Mon, 15 Jul 1996 20:14:23 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id UAA18274; Mon, 15 Jul 1996 20:14:16 -0700 (PDT) Date: Mon, 15 Jul 1996 20:14:13 -0700 Message-ID: <18266.837486853.1@time.cdrom.com> From: "Jordan K. Hubbard" Subject: I'm re-rolling the 2.1.5 release. MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message To: hackers@freebsd.org Subject: I'm re-rolling the 2.1.5 release. Date: Mon, 15 Jul 1996 20:14:13 -0700 Message-ID: <18266.837486853@time.cdrom.com> From: "Jordan K. Hubbard" I totally hate this, but at this point I've got little choice. For one thing, as everyone probably already knows, we broke the 3c509 driver badly with that 11th hour patch and people have been complaining all over the place about it. I could roll another boot floppy, but that wouldn't cover the GENERIC kernel in the bindist nor would the srcdist match. It'd be a mess. For another thing, it appears that I've totally broken CD installation. It doesn't work at all and I'm not even sure why. It worked at some point along the way, since I *did* test it with a one-off CD, but in the final release it's broken again. You can't load anything off the CD. Needless to say, that is unacceptable and now I've got to dive back into sysinstall and figure out what the heck happened. Finally, the ports collection has grown so much that it no longer fits on the first CD. I'd moved it onto the second CD knowing that the "link to your ports tree?" option of sysinstall would then break, but I figured this wouldn't be too big a deal and I did document it. Since I'm re-rolling things anyway, I can now at least fix this too. Since the sum total of changes it's going to take to fix this now exceeds the threshold of what I'd consider a reasonable "patch", I'm simply going to start over. Some tags will have to be slid forward for RELENG_2_1_5_RELEASE and I'll be replacing the distribution on wcarchive entirely once the CDs have been rolled again and I've verified completely that they work. Needless to say, I'm really sorry for the inconvenience and, in our rush to get this out, I'm afraid to say that we skipped some regression testing - this is evidently our just reward for cutting corners! I'll be setting the permissions on the 2.1.5-RELEASE directory on wcarchive to 700 until the new release is in place - please simply pretend to yourselves that you never even saw my first announcement. :-) If it's any consolation, this aborted release did point up some crucial problems and now 2.1.5-RELEASE mark II will at least be that much the better for us having found them. Jordan ------- =_aaaaaaaaaa-- From owner-freebsd-stable Mon Jul 15 21:04:04 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA28292 for stable-outgoing; Mon, 15 Jul 1996 21:04:04 -0700 (PDT) Received: from zeus.xtalwind.net (h-advice.x31.infi.net [206.27.115.63]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA28221; Mon, 15 Jul 1996 21:03:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zeus.xtalwind.net (8.7.5/8.6.12) with SMTP id AAA00640; Tue, 16 Jul 1996 00:03:23 -0400 (EDT) Date: Tue, 16 Jul 1996 00:03:22 -0400 (EDT) From: jack X-Sender: jacko@localhost To: John-David Childs cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: pwd_mkdb bug in 2.1.5? 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 Mon, 15 Jul 1996, John-David Childs wrote: > I've got a 2.1.-RELEASE system and a newly installed 2.1.5 system. > I ftp'd a copy of the master.passwd file from -RELEASE to 2.1.5 and ran > pwd_mkdb -p (I do this regularly between BSDi 2.01 and the -RELEASE > machine). > > Fortunately, I did a 'passwd root' before logging out, because NONE of the > other userid's work (bad passwords). Anyone else have the same problem or > should I do another 'make world'??? > -- Did you remember to install (or not) DES support to match your 2.1-R setup? > > John-David Childs www.marsweb.com/www.ism.net > System Administrator Internet Services Montana (406)721-6277 > & Network Engineer M@RSWeb - Montana's PREMIER Web Site > "I used up all my sick days...so I'm calling in dead" > ------------------------------------------------------------------------------ jacko@xtalwind.net Finger jacko@onyx.xtalwind.net for my PGP key Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD ------------------------------------------------------------------------------ From owner-freebsd-stable Tue Jul 16 08:09:06 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01130 for stable-outgoing; Tue, 16 Jul 1996 08:09:06 -0700 (PDT) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA01119 for ; Tue, 16 Jul 1996 08:08:59 -0700 (PDT) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id LAA23587; Tue, 16 Jul 1996 11:08:21 -0400 for Date: Tue, 16 Jul 1996 11:08:21 -0400 From: "Frank E. Terhaar-Yonkers" Message-Id: <199607161508.LAA23587@robin.mcnc.org.mcnc.org> To: freebsd-stable@FreeBSD.ORG Subject: sporadic compiler error with O2 and -pipe X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Every now and then I get the following when I compile the kernel. It's always the same .c file, and it never fails if I leave off -pipe or use -O instead of -O2. Any ideas? System is a Tyan Tomcat/CY120+, 2.1.5r. Thanks - Frank =================================================== cc -c -O2 -pipe -m486 -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -nostdinc -I. -I../.. -I../../sys -I../../../include -DLOCO -DI486_CPU -DMAXCONS=4 -DXSERVER -DPROBE_VERBOSE -DDODUMP -DDDB -DSYSVMSG -DSYSVSEM -DSYSVSHM -DNCONS=4 -DUCONSOLE -DSCSI_REPORT_GEOMETRY -DSCSI_DELAY=10 -DCOMPAT_43 -DKTRACE -DPROCFS -DMSDOSFS -DARP_PROXYALL -DGATEWAY -DFFS -DINET -DBOUNCE_BUFFERS -DUSER_LDT -DNMBCLUSTERS=4096 -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 ../../msdosfs/msdosfs_vnops.c ../../msdosfs/msdosfs_vnops.c: In function `msdosfs_write': ../../msdosfs/msdosfs_vnops.c:769: internal error--insn does not satisfy its constraints: (insn 398 1118 1121 (parallel[ (set (mem:DI (plus:SI (reg:SI 6 %ebp) (const_int -72))) (plus:DI (mem/s:DI (plus:SI (reg:SI 2 %ecx) (const_int 8))) (mem:DI (plus:SI (reg:SI 6 %ebp) (const_int -80))))) (clobber (scratch:SI)) ] ) 127 {adddi3} (insn_list 397 (nil)) (expr_list:REG_DEAD (mem:DI (plus:SI (reg:SI 6 %ebp) (const_int -80))) (expr_list:REG_UNUSED (scratch:SI) (nil)))) cpp: output pipe has been closed cc: Internal compiler error: program cc1 got fatal signal 6 *** Error code 1 Stop. {standard input}: Assembler messages: {standard input}:1349: Error: Local symbol L301 never defined. {standard input}:1349: Error: Local symbol L300 never defined. {standard input}:1349: Error: Local symbol L267 never defined. {standard input}:1349: Error: Local symbol L302 never defined. {standard input}:1349: Error: Local symbol L276 never defined. {standard input}:1349: Fatal error:5 errors, 0 warnings, no object file generated. \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-stable Tue Jul 16 23:43:16 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA03788 for stable-outgoing; Tue, 16 Jul 1996 23:43:16 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA03778; Tue, 16 Jul 1996 23:43:14 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id XAA23252; Tue, 16 Jul 1996 23:42:56 -0700 (PDT) Date: Tue, 16 Jul 1996 23:42:55 -0700 Message-ID: <23246.837585775.1@time.cdrom.com> From: "Jordan K. Hubbard" Subject: New 2.1.5-RELEASE on ftp.freebsd.org MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message To: hackers@freebsd.org Subject: New 2.1.5-RELEASE on ftp.freebsd.org Date: Tue, 16 Jul 1996 23:42:55 -0700 Message-ID: <23246.837585775@time.cdrom.com> From: "Jordan K. Hubbard" OK, the release has been updated and is now back in the ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE directory. All problems reported with the previously announced 2.1.5-RELEASE have been fixed - please let me know if you have any problems! Thanks! Jordan ------- =_aaaaaaaaaa-- From owner-freebsd-stable Thu Jul 18 11:48:38 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08617 for stable-outgoing; Thu, 18 Jul 1996 11:48:38 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA08611 for ; Thu, 18 Jul 1996 11:48:36 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by misery.sdf.com (8.7.5/UNS-1.0) with SMTP id MAA10728; Thu, 18 Jul 1996 12:00:50 -0700 (PDT) Date: Thu, 18 Jul 1996 12:00:49 -0700 (PDT) From: Tom Samplonius To: "Jordan K. Hubbard" cc: stable@freebsd.org Subject: cmu-snmp In-Reply-To: <10199.837710572@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Should cmu-snmp have been included in the xperimnt directory? I understand that cmu-snmp is no longer being developed. The particular version included in 2.1.5-RELEASE appears to be exact same one included in 2.1? However, 2.1.5-R has a perfectly good snmp package in the ports collection (ucd-snmp) that works quite well, while cmu-snmp barely works. Tom From owner-freebsd-stable Thu Jul 18 11:54:50 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA09118 for stable-outgoing; Thu, 18 Jul 1996 11:54:50 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA09111 for ; Thu, 18 Jul 1996 11:54:48 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id OAA05540; Thu, 18 Jul 1996 14:54:30 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Tom Samplonius cc: stable@freebsd.org From: "Gary Palmer" Subject: Re: cmu-snmp In-reply-to: Your message of "Thu, 18 Jul 1996 12:00:49 PDT." Date: Thu, 18 Jul 1996 14:54:30 -0400 Message-ID: <5535.837716070@orion.webspan.net> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius wrote in message ID : > However, 2.1.5-R has a perfectly good snmp package in the ports > collection (ucd-snmp) that works quite well, while cmu-snmp barely works. Only ``quite well''? Have you found problems with it? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-stable Thu Jul 18 12:08:06 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09930 for stable-outgoing; Thu, 18 Jul 1996 12:08:06 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA09925 for ; Thu, 18 Jul 1996 12:08:05 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id MAA16258; Thu, 18 Jul 1996 12:07:50 -0700 (PDT) To: Tom Samplonius cc: stable@freebsd.org Subject: Re: cmu-snmp In-reply-to: Your message of "Thu, 18 Jul 1996 12:00:49 PDT." Date: Thu, 18 Jul 1996 12:07:50 -0700 Message-ID: <16256.837716870@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Should cmu-snmp have been included in the xperimnt directory? > > I understand that cmu-snmp is no longer being developed. The particular > version included in 2.1.5-RELEASE appears to be exact same one included in > 2.1? Yes, it's the same one. I had such an embarassingly low turn-out for the experimental collection for 2.1.5 (maybe 3 entries) that I simply merged the old one back in. I wasn't aware that cmu-snmp was quite so obsolete, but I also doubt that it's going to cause any significant degree of harm, either. Jordan From owner-freebsd-stable Thu Jul 18 18:08:06 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05838 for stable-outgoing; Thu, 18 Jul 1996 18:08:06 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA05830 for ; Thu, 18 Jul 1996 18:08:04 -0700 (PDT) Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.67.25]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id SAA13109 for ; Thu, 18 Jul 1996 18:08:02 -0700 Received: (from skynyrd@localhost) by tahoma.cwu.edu (8.6.13/8.6.9) id SAA24409; Thu, 18 Jul 1996 18:08:01 -0700 Date: Thu, 18 Jul 1996 18:08:00 -0700 (PDT) From: Chris Timmons To: stable@freebsd.org Subject: tcpdump nfsv2.h missed from cvs checkout of 2.1.5-R Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There is a high probability I am intellectually bankrupt. In any case, I supped CVS today and checked out a RELENG_2_1_5_RELEASE src tree and made world. When it got to tcpdump, print-udp.c and print-nfs.c couldn't find nfsv2.h in the directory. I can see nfsv2.h,v in tcpdump/Attic in my CVS repository, and it has the RELENG_2_1_5_RELEASE tag, so there must be something i've missed in my checkout command to pick it off? I understand that wrt -current, nfsv2.h is deprecated, and was able to check out the -current tcpdump tree to diff against my 2.1.5-R tree; looks like i got the cvs checkout mostly right. Any ideas? -Chris From owner-freebsd-stable Thu Jul 18 19:50:18 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA16557 for stable-outgoing; Thu, 18 Jul 1996 19:50:18 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA16542 for ; Thu, 18 Jul 1996 19:50:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id TAA13413; Thu, 18 Jul 1996 19:48:54 -0700 (PDT) Message-Id: <199607190248.TAA13413@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Chris Timmons cc: stable@freebsd.org Subject: Re: tcpdump nfsv2.h missed from cvs checkout of 2.1.5-R In-reply-to: Your message of "Thu, 18 Jul 1996 18:08:00 PDT." From: David Greenman Reply-To: davidg@root.com Date: Thu, 18 Jul 1996 19:48:54 -0700 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >There is a high probability I am intellectually bankrupt. > >In any case, I supped CVS today and checked out a RELENG_2_1_5_RELEASE >src tree and made world. > >When it got to tcpdump, print-udp.c and print-nfs.c couldn't find nfsv2.h >in the directory. > >I can see nfsv2.h,v in tcpdump/Attic in my CVS repository, and it has the >RELENG_2_1_5_RELEASE tag, so there must be something i've missed in my >checkout command to pick it off? > >I understand that wrt -current, nfsv2.h is deprecated, and was able to check >out the -current tcpdump tree to diff against my 2.1.5-R tree; looks like i >got the cvs checkout mostly right. > >Any ideas? nfsv2.h is in the sys/nfs directory. It sounds like your /usr/include hierarchy needs to be rebuilt. Try "cd /usr/src; make includes", and see if this fixes it. ...although 'make world' should have done this for you. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Fri Jul 19 00:44:12 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA12186 for stable-outgoing; Fri, 19 Jul 1996 00:44:12 -0700 (PDT) Received: from bofh.noc.best.net (bofh.noc.best.net [205.149.163.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA12167; Fri, 19 Jul 1996 00:44:09 -0700 (PDT) Received: (from rone@localhost) by bofh.noc.best.net (8.7.5/8.7.3) id AAA01260; Fri, 19 Jul 1996 00:44:05 -0700 (PDT) Date: Fri, 19 Jul 1996 00:44:05 -0700 (PDT) From: Ron Echeverri Message-Id: <199607190744.AAA01260@bofh.noc.best.net> To: questions@freebsd.org, stable@freebsd.org Subject: rlogin/rsh stop working in 2.1.5 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk % rlogin shellx rcmd: socket: Protocol not available This did not happen when i was running 2.1-STABLE nor did it happen with 2.2-SNAP9606. What'd i do wrong? I don't know what could be causing this, so i'm not sure where to look to fix it. In the meantime, of course, i'm trying to figure out how to work with ssh (and also figure out why it refuses to start certain X clients from my .xinitrc now) and xauth... thanks rone From owner-freebsd-stable Sat Jul 20 05:06:45 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA06612 for stable-outgoing; Sat, 20 Jul 1996 05:06:45 -0700 (PDT) Received: from moon.yzit.edu.tw (moon.yzit.edu.tw [140.138.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA06605 for ; Sat, 20 Jul 1996 05:06:42 -0700 (PDT) Received: from Zappa ([140.115.2.119]) by moon.yzit.edu.tw (8.6.12/8.6.9) with SMTP id UAA26785 for ; Sat, 20 Jul 1996 20:10:17 +0800 Received: by Zappa with Microsoft Mail id <01BB7677.0E4354A0@Zappa>; Sat, 20 Jul 1996 20:07:19 +0800 Message-ID: <01BB7677.0E4354A0@Zappa> From: Jaw Jr-Chiang To: "'freebsd-stable@freebsd.org'" Subject: src-2.1.0146A make world fail! Date: Sat, 20 Jul 1996 20:07:07 +0800 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 Could anyone help me solve this problem? I am using FreeBSD 2.1.0 Release and I want to upgrade to 2.1.5R So I fetch the FreeBSD-stable/ctm/src-2.1.0146A.gz and do ctm. After ctm, I make world. But, when it make ipfw, it shows many problem. What's wrong? Here is its error message: cc -O -c /usr/src/ctm/sbin/ipfw/ipfw.c /usr/src/ctm/sbin/ipfw/ipfw.c: In function `show_ipfw': /usr/src/ctm/sbin/ipfw/ipfw.c:114: structure has no member named `fw_number' /usr/src/ctm/sbin/ipfw/ipfw.c:121: structure has no member named `timestamp' /usr/src/ctm/sbin/ipfw/ipfw.c:125: structure has no member named `timestamp' /usr/src/ctm/sbin/ipfw/ipfw.c:137: `IP_FW_F_COUNT' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:137: (Each undeclared identifier is reported only once /usr/src/ctm/sbin/ipfw/ipfw.c:137: for each function it appears in.) /usr/src/ctm/sbin/ipfw/ipfw.c:237: `IP_FW_F_IN' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:237: `IP_FW_F_OUT' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:249: `IP_FW_F_IFUWILD' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:258: `IP_FW_F_FRAG' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:261: structure has no member named `fw_ipopt' /usr/src/ctm/sbin/ipfw/ipfw.c:261: structure has no member named `fw_ipnopt' /usr/src/ctm/sbin/ipfw/ipfw.c:267: structure has no member named `fw_ipopt' /usr/src/ctm/sbin/ipfw/ipfw.c:267: `IP_FW_IPOPT_SSRR' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:268: structure has no member named `fw_ipnopt' /usr/src/ctm/sbin/ipfw/ipfw.c:269: structure has no member named `fw_ipopt' /usr/src/ctm/sbin/ipfw/ipfw.c:269: `IP_FW_IPOPT_LSRR' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:270: structure has no member named `fw_ipnopt' /usr/src/ctm/sbin/ipfw/ipfw.c:271: structure has no member named `fw_ipopt' /usr/src/ctm/sbin/ipfw/ipfw.c:271: `IP_FW_IPOPT_RR' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:272: structure has no member named `fw_ipnopt' /usr/src/ctm/sbin/ipfw/ipfw.c:273: structure has no member named `fw_ipopt' /usr/src/ctm/sbin/ipfw/ipfw.c:273: `IP_FW_IPOPT_TS' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:274: structure has no member named `fw_ipnopt' /usr/src/ctm/sbin/ipfw/ipfw.c:277: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:277: `IP_FW_TCPF_ESTAB' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:279: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:279: `IP_FW_TCPF_SYN' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:280: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:280: `IP_FW_TCPF_ACK' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:282: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:282: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:288: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:288: `IP_FW_TCPF_FIN' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:289: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:290: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:291: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:292: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:292: `IP_FW_TCPF_RST' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:293: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:294: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:294: `IP_FW_TCPF_PSH' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:295: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:296: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:297: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:298: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:298: `IP_FW_TCPF_URG' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:299: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:301: `IP_FW_F_ICMPBIT' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:308: structure has no member named `fw_icmptypes' /usr/src/ctm/sbin/ipfw/ipfw.c: In function `list': /usr/src/ctm/sbin/ipfw/ipfw.c:330: `IP_FW_GET' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c: In function `fill_tcpflag': /usr/src/ctm/sbin/ipfw/ipfw.c:490: `IP_FW_TCPF_SYN' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:491: `IP_FW_TCPF_FIN' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:492: `IP_FW_TCPF_ACK' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:493: `IP_FW_TCPF_PSH' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:494: `IP_FW_TCPF_RST' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:495: `IP_FW_TCPF_URG' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c: In function `fill_ipopt': /usr/src/ctm/sbin/ipfw/ipfw.c:537: `IP_FW_IPOPT_SSRR' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:538: `IP_FW_IPOPT_LSRR' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:539: `IP_FW_IPOPT_RR' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:540: `IP_FW_IPOPT_TS' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c: In function `fill_icmptypes': /usr/src/ctm/sbin/ipfw/ipfw.c:570: `IP_FW_F_ICMPBIT' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c: In function `delete': /usr/src/ctm/sbin/ipfw/ipfw.c:588: structure has no member named `fw_number' /usr/src/ctm/sbin/ipfw/ipfw.c: In function `add': /usr/src/ctm/sbin/ipfw/ipfw.c:610: structure has no member named `fw_number' /usr/src/ctm/sbin/ipfw/ipfw.c:621: `IP_FW_F_COUNT' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:696: `IP_FW_F_IFUWILD' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:708: `IP_FW_F_FRAG' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:711: `IP_FW_F_IN' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:714: `IP_FW_F_OUT' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:718: structure has no member named `fw_ipopt' /usr/src/ctm/sbin/ipfw/ipfw.c:718: structure has no member named `fw_ipnopt' /usr/src/ctm/sbin/ipfw/ipfw.c:723: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:723: `IP_FW_TCPF_ESTAB' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:727: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:727: `IP_FW_TCPF_SYN' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:728: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:728: `IP_FW_TCPF_ACK' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:733: structure has no member named `fw_tcpf' /usr/src/ctm/sbin/ipfw/ipfw.c:733: structure has no member named `fw_tcpnf' /usr/src/ctm/sbin/ipfw/ipfw.c:740: structure has no member named `fw_icmptypes' /usr/src/ctm/sbin/ipfw/ipfw.c: In function `zero': /usr/src/ctm/sbin/ipfw/ipfw.c:763: `IP_FW_ZERO' undeclared (first use this function) /usr/src/ctm/sbin/ipfw/ipfw.c:776: structure has no member named `fw_number' /usr/src/ctm/sbin/ipfw/ipfw.c:780: structure has no member named `fw_number' *** Error code 1 Stop. From owner-freebsd-stable Sat Jul 20 05:45:05 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13070 for stable-outgoing; Sat, 20 Jul 1996 05:45:05 -0700 (PDT) Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA13061 for ; Sat, 20 Jul 1996 05:45:02 -0700 (PDT) Received: from 199.183.109.242 by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Sat, 20 Jul 1996 07:44:50 -0600 Message-ID: Date: 20 Jul 1996 07:44:29 -0500 From: "Richard Wackerbarth" Subject: Re: src-2.1.0146A make world fail! To: "'freebsd-stable@freebsd.org'" , "Jaw Jr-Chiang" X-Mailer: Mail*Link PT/Internet 1.6.0 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Could anyone help me solve this problem? > I am using FreeBSD 2.1.0 Release and I want to upgrade to 2.1.5R > So I fetch the FreeBSD-stable/ctm/src-2.1.0146A.gz and do ctm. It won't help with your problem, but you should also fetch FreeBSD-stable/ctm/src-2.1.0147.gz. That file fixes the things that were changed after the first attempted release was withdrawn. Similarly, I suggest that you consider subscribing to the ctm distribution mailing list to automatically receive any future updates to 2.1. -- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-stable Sat Jul 20 16:46:09 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA24670 for stable-outgoing; Sat, 20 Jul 1996 16:46:09 -0700 (PDT) Received: from bofh.noc.best.net (bofh.noc.best.net [205.149.163.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA24652; Sat, 20 Jul 1996 16:46:04 -0700 (PDT) Received: (from rone@localhost) by bofh.noc.best.net (8.7.5/8.7.3) id QAA10046; Sat, 20 Jul 1996 16:46:01 -0700 (PDT) From: Ron Echeverri Message-Id: <199607202346.QAA10046@bofh.noc.best.net> Subject: Re: rcmd: socket: Protocol not available To: spfarrel@midway.uchicago.edu (steve farrell) Date: Sat, 20 Jul 1996 16:46:01 -0700 (PDT) Cc: stable@freebsd.org, questions@freebsd.org In-Reply-To: <199607191703.MAA00970@meno.uchicago.edu> from steve farrell at "Jul 19, 96 12:03:16 pm" 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 steve farrell writes: >% rlogin shellx >rcmd: socket: Protocol not available ...actually, i rather suspect you did what i did, which was give yourself a copy of libc.so.3.0 so you could run binaries from a -current box. evidentally i've been building against this library not libc.so.2.2. i wouldn't think it would matter much, except that 3.0 doesn't seem to match a 2.1 kernel, and hence these errors. [that's my guess, at least] try ldd'ing your rsh. bofh# ldd `which rsh` /usr/bin/rsh: -lc.3 => /usr/lib/libc.so.3.0 (0x801c000) bofh# cd /usr/lib bofh# mv libc.so.3.0 libc.so.3.0.disabled bofh# ln -s libc.so.2.2 libc.so.3.0 % rlogin shellx Best Internet Communications, Inc. Mountain View, California USA Customer Shell system - * Unauthorized access prohibited * And Bingo was his name. Do you expect that my linking 3.0 to 2.2 will cause any problems? (jeez, that sounds like a dumb question, but what the heck...) thanks rone -- Ron Echeverri Best Internet Systems Administration rone@best.net ============================================================================== No, i don't know what i'm doing, and if i did, i wouldn't tell you.