From owner-freebsd-current Sun Jan 25 00:08:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22718 for current-outgoing; Sun, 25 Jan 1998 00:08:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22713 for ; Sun, 25 Jan 1998 00:08:13 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from giovannelli.it (modem00.masternet.it [194.184.65.254]) by www.giovannelli.it (8.8.8/8.8.5) with ESMTP id JAA00314; Sun, 25 Jan 1998 09:10:28 +0100 (MET) Message-ID: <34CAF36F.E2EE340F@giovannelli.it> Date: Sun, 25 Jan 1998 09:10:23 +0100 From: Gianmarco Giovannelli Reply-To: gmarco@giovannelli.it X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Bruce Albrecht CC: current@FreeBSD.ORG Subject: Re: Last stable -current? References: <199801250157.TAA27057@zuhause.mn.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Bruce Albrecht wrote: > > What's the last stable -current? Is it really 97.12.23, as Chris > Timmons suggested in an email on January 15th? Now for me works everything (at least everything I have tried :-). I think you can safely use -current . -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it From owner-freebsd-current Sun Jan 25 00:42:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24159 for current-outgoing; Sun, 25 Jan 1998 00:42:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24154 for ; Sun, 25 Jan 1998 00:42:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id AAA20980; Sun, 25 Jan 1998 00:42:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199801250842.AAA20980@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: gmarco@giovannelli.it cc: Bruce Albrecht , current@FreeBSD.ORG Subject: Re: Last stable -current? In-reply-to: Your message of "Sun, 25 Jan 1998 09:10:23 +0100." <34CAF36F.E2EE340F@giovannelli.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jan 1998 00:42:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk I haven't seen any posting from Dyson so I assume that -current still has vm problems. Cheers, Amancio From owner-freebsd-current Sun Jan 25 01:05:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25188 for current-outgoing; Sun, 25 Jan 1998 01:05:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25181 for ; Sun, 25 Jan 1998 01:05:19 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id TAA02250; Sun, 25 Jan 1998 19:28:19 +1030 (CST) Message-Id: <199801250858.TAA02250@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: jbryant@unix.tfs.net cc: freebsd-current@FreeBSD.ORG Subject: Re: apm on toshiba In-reply-to: Your message of "Sat, 24 Jan 1998 13:51:27 MDT." <199801241951.NAA14274@unix.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jan 1998 19:28:18 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > i just got a toshiba laptop [portege 660cdt] from work, and am > planning to run -current... > > has anything been done with the apm on these to support dim > backlighting, and disk spindown? No. You can hotkey through your power settings, and organise your disk spindown with the BIOS setup, but if you want to let the disk spin down you need to stretch the update time out further. Basically, if you want to save power, take an active approach. 'zzz' works fine, or close the lid and wind the update time out if you want the machine to keep responding. > has anyone had any experience with these laptops? any pointers? > anything to avoid? I've been using a 220CDS, which is reasonably similar, for a while now. For all that it's a custom-chipset unit, it's pretty solid. > also, is the sound driver code supported on these? I think the 660 still uses the Yamaha OPL-SAX hardware, so yes, it looks like an MSS. I quite often use MP3 audio as an alternative to playing CDs, and I seem to recall having recorded stuff too. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ From owner-freebsd-current Sun Jan 25 01:10:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25540 for current-outgoing; Sun, 25 Jan 1998 01:10:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA25535 for ; Sun, 25 Jan 1998 01:10:21 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 7681 invoked from network); 25 Jan 1998 09:10:06 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 25 Jan 1998 09:10:06 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id BAA00416 for freebsd-current@freebsd.org; Sun, 25 Jan 1998 01:10:18 -0800 (PST) (envelope-from scottm) Date: Sun, 25 Jan 1998 01:10:18 -0800 (PST) From: Scott Michel Message-Id: <199801250910.BAA00416@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: stable current? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk For UNI kernels, John's latest round of vm changes seem to be more stable -- OTOH I'm not really pushing things that hard either. >From a CVSUP late this evening (yes, I'm at UCLA on a Sat. night, so there!) and a rebuild of world, I haven't encountered: a) Spurious splats of 'cc'... b) Random bus errors c) VM splats on MS-DOG file system mounts FWIW. -scooter From owner-freebsd-current Sun Jan 25 04:36:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05644 for current-outgoing; Sun, 25 Jan 1998 04:36:28 -0800 (PST) (envelope-from owner-freebsd-current@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 EAA05636 for ; Sun, 25 Jan 1998 04:36:25 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id NAA02714 for current@FreeBSD.ORG; Sun, 25 Jan 1998 13:30:09 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id NAA02115; Sun, 25 Jan 1998 13:26:01 +0100 (CET) (envelope-from andreas) Message-ID: <19980125132600.08003@klemm.gtn.com> Date: Sun, 25 Jan 1998 13:26:00 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: Why isn't it possible to do a "make release" without "make world" ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Hi ! I wanted to create a new -current SNAP for me and trapped into a problem, that I can't do a "make release" without doing a "make world" as the first step. The error message looks as follows: cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 nfs/*.h /home/release/usr/include/nfs cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 pccard/*.h /home/release/usr/include/pccard cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 sys/*.h /home/release/usr/include/sys cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 vm/*.h /home/release/usr/include/vm cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 isofs/cd9660/*.h /home/release/usr/include/isofs/cd9660 cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 ufs/ffs/*.h /home/release/usr/include/ufs/ffs cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 ufs/lfs/*.h /home/release/usr/include/ufs/lfs cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 ufs/mfs/*.h /home/release/usr/include/ufs/mfs cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 ufs/ufs/*.h /home/release/usr/include/ufs/ufs cd /usr/src/include/../sys/i386/include; install -C -o bin -g bin -m 444 *.h /home/release/usr/include/machine cd /usr/src/include; install -C -o bin -g bin -m 444 a.out.h ar.h assert.h bitstring.h ctype.h db.h dirent.h disktab.h elf.h err.h fnmatch.h fstab.h fts.h glob.h grp.h strhash.h histedit.h kvm.h limits.h link.h locale.h malloc.h memory.h mpool.h ndbm.h netdb.h nl_types.h nlist.h paths.h pthread.h pthread_np.h pwd.h ranlib.h regex.h regexp.h resolv.h rune.h runetype.h setjmp.h sgtty.h signal.h stab.h stddef.h stdio.h stdlib.h string.h stringlist.h strings.h struct.h sysexits.h tar.h time.h timers.h ttyent.h unistd.h utime.h utmp.h vis.h /home/release/usr/include cd /usr/src/include/arpa; install -C -o bin -g bin -m 444 ftp.h inet.h nameser.h telnet.h tftp.h /home/release/usr/include/arpa cd /usr/src/include/protocols; install -C -o bin -g bin -m 444 dumprestore.h routed.h rwhod.h talkd.h timed.h /home/release/usr/include/protocols cd /usr/src/include/rpc; install -C -o bin -g bin -m 444 auth.h auth_unix.h clnt.h pmap_clnt.h pmap_prot.h pmap_rmt.h rpc.h rpc_com.h rpc_msg.h svc.h svc_auth.h types.h xdr.h auth_des.h des.h des_crypt.h key_prot.h /home/release/usr/include/rpc install -C -o bin -g bin -m 444 /usr/obj/usr/src/include/osreldate.h /home/release/usr/include install: /usr/obj/usr/src/include/osreldate.h: No such file or directory *** Error code 71 Stop. *** Error code 1 Is this normal behaviour ? Or shouldn't it be possible, to build a release, no matter on what machine your are on ? Really don't know, what's the final goal, please let me know. Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' From owner-freebsd-current Sun Jan 25 06:35:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10206 for current-outgoing; Sun, 25 Jan 1998 06:35:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10199 for ; Sun, 25 Jan 1998 06:35:47 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id PAA13448 for current@FreeBSD.ORG; Sun, 25 Jan 1998 15:35:41 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id OAA22808; Sun, 25 Jan 1998 14:55:37 +0100 (CET) (envelope-from roberto) Message-ID: <19980125145536.61375@keltia.freenix.fr> Date: Sun, 25 Jan 1998 14:55:36 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Last stable -current? Mail-Followup-To: current@FreeBSD.ORG References: <34CAF36F.E2EE340F@giovannelli.it> <199801250842.AAA20980@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <199801250842.AAA20980@rah.star-gate.com>; from Amancio Hasty on Sun, Jan 25, 1998 at 12:42:12AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4010 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk According to Amancio Hasty: > I haven't seen any posting from Dyson so I assume that -current still has > vm problems. The bad period is between Dec, 28th and Jan, 20th approx. nullfs/umapfs are unusable right now although some unionfs fixes are probably relevant to them as well. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #4: Sun Jan 18 15:50:16 CET 1998 From owner-freebsd-current Sun Jan 25 07:43:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13548 for current-outgoing; Sun, 25 Jan 1998 07:43:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sierra.covalent.net (sierra.covalent.net [208.214.58.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13543 for ; Sun, 25 Jan 1998 07:43:16 -0800 (PST) (envelope-from randy@covalent.net) Received: from localhost (localhost [127.0.0.1]) by sierra.covalent.net (8.8.8/8.8.2) with ESMTP id JAA11500 for ; Sun, 25 Jan 1998 09:36:02 -0600 (CST) To: current@FreeBSD.ORG Subject: Cyclades/Hylafax/SMP select problems? X-Mailer: Mew version 1.92.4 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980125093559D.randy@covalent.net> Date: Sun, 25 Jan 1998 09:35:59 -0600 From: Randy Terbush X-Dispatcher: imput version 971024 Lines: 11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk I have a dual P6 machine with a Cy-16Ye running the latest current. The Hylafax faxgetty and faxq processes spin out of control chewing up nearly 100% CPU. The same configuration ran without problems on a single P5 machine running 2.2-STABLE. As I begin to dig deeper into this, are there any know problems with this mix? From owner-freebsd-current Sun Jan 25 09:18:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21580 for current-outgoing; Sun, 25 Jan 1998 09:18:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21572 for ; Sun, 25 Jan 1998 09:18:44 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id JAA15636; Sun, 25 Jan 1998 09:18:26 -0800 (PST) To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: Why isn't it possible to do a "make release" without "make world" ? In-reply-to: Your message of "Sun, 25 Jan 1998 13:26:00 +0100." <19980125132600.08003@klemm.gtn.com> Date: Sun, 25 Jan 1998 09:18:26 -0800 Message-ID: <15632.885748706@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > I wanted to create a new -current SNAP for me and trapped into > a problem, that I can't do a "make release" without doing a > "make world" as the first step. That's always been the case. > Is this normal behaviour ? Or shouldn't it be possible, to > build a release, no matter on what machine your are on ? It's not possible. Jordan From owner-freebsd-current Sun Jan 25 10:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28220 for current-outgoing; Sun, 25 Jan 1998 10:00:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28213 for ; Sun, 25 Jan 1998 10:00:03 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA25937; Sun, 25 Jan 1998 12:59:35 -0500 (EST) (envelope-from toor) Message-Id: <199801251759.MAA25937@dyson.iquest.net> Subject: Re: Last stable -current? In-Reply-To: <19980125145536.61375@keltia.freenix.fr> from Ollivier Robert at "Jan 25, 98 02:55:36 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sun, 25 Jan 1998 12:59:35 -0500 (EST) Cc: current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk Ollivier Robert said: > According to Amancio Hasty: > > I haven't seen any posting from Dyson so I assume that -current still has > > vm problems. > > The bad period is between Dec, 28th and Jan, 20th approx. nullfs/umapfs are > unusable right now although some unionfs fixes are probably relevant to > them as well. > Things should be better now. I am being very cautious about making any claims, however, try again. (The problems weren't strictly with VM but with VFS.) PHK had started some things in motion, not breaking the system, but showed me where things needed work. I initially broke the system, but worked on some stuff that followed up on PHK's work. Things should be better now, including the system should be more memory efficient. Keep me posted. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Sun Jan 25 10:03:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28787 for current-outgoing; Sun, 25 Jan 1998 10:03:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28780 for ; Sun, 25 Jan 1998 10:03:48 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA25960; Sun, 25 Jan 1998 13:03:42 -0500 (EST) (envelope-from toor) Message-Id: <199801251803.NAA25960@dyson.iquest.net> Subject: Re: stable current? In-Reply-To: <199801250910.BAA00416@mordred.cs.ucla.edu> from Scott Michel at "Jan 25, 98 01:10:18 am" To: scottm@cs.ucla.edu (Scott Michel) Date: Sun, 25 Jan 1998 13:03:42 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk Scott Michel said: > > For UNI kernels, John's latest round of vm changes seem to be more > stable -- OTOH I'm not really pushing things that hard either. > Rather than announcing the system is "better", I have been holding out until someone else sees it. The only thing(s) that shouldn't be working are the layered filesystems. Those thing(s) are really broken, and absolutely no Lite/2 derivative has them working properly. Because of the structure of the merged VM/Buffer cache, we haven't had them working for, a long time but now at least we have a better chance of someone fixing them. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Sun Jan 25 10:03:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28888 for current-outgoing; Sun, 25 Jan 1998 10:03:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28766 for ; Sun, 25 Jan 1998 10:03:33 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id TAA28404 for freebsd-current@FreeBSD.ORG; Sun, 25 Jan 1998 19:02:59 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id SAA18397; Sun, 25 Jan 1998 18:08:47 +0100 (CET) (envelope-from roberto) Message-ID: <19980125180846.52993@keltia.freenix.fr> Date: Sun, 25 Jan 1998 18:08:46 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Weird error with bison in current Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i X-Operating-System: FreeBSD 3.0-CURRENT ctm#4016 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk I'm getting this weird error in buildworld. It used to work... in gnu/usr.bin/cc/cc_tools: -=-=-=-=-=-=- 210 [18:04] root@keltia:cc/cc_tools# make bison -d /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-parser.y -o bi-parser.c bison: extra arguments ignored after '/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-parser.y' cc -O -pipe -DFREEBSD_AOUT -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/src/gnu/usr.bin/cc/cc_tools/obj/../cc_tools -c bi-parser.c cc: bi-parser.c: No such file or directory *** Error code 1 Stop. -=-=-=-=-=-=- It worked fine in my 12/8/97 build: -=-=-=-=-=-=- cc -O -pipe -DFREEBSD_AOUT -I/src/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/src/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/src/src/gnu/usr.bin/cc/cc_tools/obj/../cc_tools -I/usr/obj/src/src/tmp/usr/include -c /src/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-arity.c bison -d /src/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-parser.y -o bi-parser.c -=-=-=-=-=-=- CURRENT sources from cvs-cur 4016 1998/01/25 14:09:28 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #4: Sun Jan 18 15:50:16 CET 1998 From owner-freebsd-current Sun Jan 25 11:25:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06926 for current-outgoing; Sun, 25 Jan 1998 11:25:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06915 for ; Sun, 25 Jan 1998 11:25:31 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id UAA04386 for freebsd-current@FreeBSD.ORG; Sun, 25 Jan 1998 20:25:28 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id TAA05133; Sun, 25 Jan 1998 19:41:53 +0100 (CET) (envelope-from roberto) Message-ID: <19980125194153.58529@keltia.freenix.fr> Date: Sun, 25 Jan 1998 19:41:53 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Re: Weird error with bison in current Mail-Followup-To: FreeBSD Current Users' list References: <19980125180846.52993@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980125180846.52993@keltia.freenix.fr>; from Ollivier Robert on Sun, Jan 25, 1998 at 06:08:46PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4016 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk According to Ollivier Robert: > I'm getting this weird error in buildworld. It used to work... The following does fix it but why did it stopped working ? I fixed all the gnu/usr.bin/cc/*/Makefile as well (and don't tell me my cvs shouldn't emit Index: lines). Index: cc1plus/Makefile =================================================================== RCS file: /spare/FreeBSD-current/src/gnu/usr.bin/cc/cc1plus/Makefile,v retrieving revision 1.13 diff -u -2 -r1.13 Makefile --- Makefile 1997/10/05 09:39:06 1.13 +++ Makefile 1998/01/25 18:44:37 @@ -20,5 +20,5 @@ .ORDER: parse.c parse.h parse.c parse.h: parse.y - ${BISON} -d ${GCCDIR}/cp/parse.y -o parse.c + ${BISON} -o parse.c -d ${GCCDIR}/cp/parse.y grep '^#define[ ]*YYEMPTY' parse.c >>parse.h Index: cc_tools/Makefile =================================================================== RCS file: /spare/FreeBSD-current/src/gnu/usr.bin/cc/cc_tools/Makefile,v retrieving revision 1.6 diff -u -2 -r1.6 Makefile --- Makefile 1998/01/25 09:47:46 1.6 +++ Makefile 1998/01/25 18:40:03 @@ -29,5 +29,5 @@ .ORDER: bi-parser.c bi-parser.h bi-parser.c bi-parser.h: bi-parser.y - ${BISON} ${BISONFLAGS} -d ${.ALLSRC} -o bi-parser.c + ${BISON} ${BISONFLAGS} -o bi-parser.c -d ${.ALLSRC} SRCS+= bi-parser.c bi-parser.h @@ -89,5 +89,5 @@ -e "/^ifc$$/d" -e "/^end ifc$$/d" \ ${GCCDIR}/c-parse.in > c-parse.y - ${BISON} -d c-parse.y -o c-parse.c + ${BISON} -o c-parse.c -d c-parse.y rm -f c-parse.y @@ -102,5 +102,5 @@ -e "/^ifobjc$$/d" -e "/^end ifobjc$$/d" \ ${GCCDIR}/c-parse.in > objc-parse.y - ${BISON} -d objc-parse.y -o objc-parse.c + ${BISON} -o objc-parse.c -d objc-parse.y rm -f objc-parse.y Index: cpp/Makefile =================================================================== RCS file: /spare/FreeBSD-current/src/gnu/usr.bin/cc/cpp/Makefile,v retrieving revision 1.10 diff -u -2 -r1.10 Makefile --- Makefile 1997/10/05 09:39:08 1.10 +++ Makefile 1998/01/25 18:44:01 @@ -12,5 +12,5 @@ .ORDER: cexp.c cexp.h cexp.c cexp.h: cexp.y - ${BISON} -d ${GCCDIR}/cexp.y -o cexp.c + ${BISON} -o cexp.c -d ${GCCDIR}/cexp.y CLEANFILES+= cexp.c cexp.h -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #4: Sun Jan 18 15:50:16 CET 1998 From owner-freebsd-current Sun Jan 25 12:15:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14750 for current-outgoing; Sun, 25 Jan 1998 12:15:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14745 for ; Sun, 25 Jan 1998 12:15:22 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id MAA04673 for ; Sun, 25 Jan 1998 12:15:11 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sun, 25 Jan 1998 12:15:10 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG Subject: kernel build fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk current smp kernel fails to build after sup this morning here is where it stops: cc -c -O2 -pipe -m486 -fno-strength-reduce -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DPQ_LARGECACHE -DLKM -DSYSVSMG -DSYSVIPC -DKERNEL -include opt_global.h ../../kern/kern_clock.c In file included from ../../kern/kern_clock.c:67: machine/smp.h:173: `cpuid' redeclared as different kind of symbol machine/cpufunc.h:62: previous declaration of `cpuid' *** Error code 1 cpufunc.h is a new file -rw-r--r-- 1 root bin 10934 Jan 25 09:26 and smp.h is dated -rw-r--r-- 1 root wheel 4998 Jan 1 17:45 I built a kernel last night with no problem Manfred ============================== || mantar@netcom.com || || Ph. (415) 647-4843 || ============================== From owner-freebsd-current Sun Jan 25 12:18:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15236 for current-outgoing; Sun, 25 Jan 1998 12:18:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15220 for ; Sun, 25 Jan 1998 12:18:02 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id VAA08211 for freebsd-current@FreeBSD.ORG; Sun, 25 Jan 1998 21:17:59 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id VAA02442; Sun, 25 Jan 1998 21:16:54 +0100 (CET) (envelope-from roberto) Message-ID: <19980125211653.18913@keltia.freenix.fr> Date: Sun, 25 Jan 1998 21:16:53 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Re: Weird error with bison in current Mail-Followup-To: FreeBSD Current Users' list References: <19980125180846.52993@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980125180846.52993@keltia.freenix.fr>; from Ollivier Robert on Sun, Jan 25, 1998 at 06:08:46PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4016 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk According to Ollivier Robert: > bison -d /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-parser.y -o bi-parser.c > bison: extra arguments ignored after '/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-parser.y' I've found the source of this error. I have POSIXLY_CORRECT set (in order to work around the new patch) and that makes getopt(3) behave like this. Ignore the patches I posted. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #4: Sun Jan 18 15:50:16 CET 1998 From owner-freebsd-current Sun Jan 25 13:03:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18955 for current-outgoing; Sun, 25 Jan 1998 13:03:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18944 for ; Sun, 25 Jan 1998 13:03:18 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id AAA26654; Mon, 26 Jan 1998 00:00:09 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id AAA02332; Mon, 26 Jan 1998 00:00:16 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199801252100.AAA02332@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Ollivier Robert cc: "FreeBSD Current Users' list" Subject: Re: Weird error with bison in current In-reply-to: Your message of "Sun, 25 Jan 1998 21:16:53 +0100." <19980125211653.18913@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jan 1998 00:00:15 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Ollivier Robert wrote: > According to Ollivier Robert: > > bison -d /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-parser.y -o bi-parser.c > > bison: extra arguments ignored after '/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bi-parser.y' > > I've found the source of this error. I have POSIXLY_CORRECT set (in order > to work around the new patch) and that makes getopt(3) behave like this. And, indeed, it is incorrect to use options after filenames. > Ignore the patches I posted. Why? They wouldn't broke anything, I believe. Dima From owner-freebsd-current Sun Jan 25 15:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01189 for current-outgoing; Sun, 25 Jan 1998 15:33:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01184 for ; Sun, 25 Jan 1998 15:33:08 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA20944; Sun, 25 Jan 1998 16:33:06 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd020916; Sun Jan 25 16:32:59 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA17175; Sun, 25 Jan 1998 16:32:55 -0700 (MST) From: Terry Lambert Message-Id: <199801252332.QAA17175@usr02.primenet.com> Subject: Re: apm on toshiba To: mike@smith.net.au (Mike Smith) Date: Sun, 25 Jan 1998 23:32:55 +0000 (GMT) Cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199801250858.TAA02250@word.smith.net.au> from "Mike Smith" at Jan 25, 98 07:28:18 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > > i just got a toshiba laptop [portege 660cdt] from work, and am > > planning to run -current... > > > > has anything been done with the apm on these to support dim > > backlighting, and disk spindown? > > No. You can hotkey through your power settings, and organise your > disk spindown with the BIOS setup, but if you want to let the disk spin > down you need to stretch the update time out further. The update time only applies to dirty buffers. If you don't dirty any buffers, you won't spin up for update writes. If you do dirty buffers, you are probably doing reads to do it, so your disk will already be spun up. Either way, it should not be necessary to hack updated. One thing that *is* useful to do to updated is to force it, if it does an update on an FS and there is nothing to update since last time, to mark the FS clean and write out the superblock. A subsequent write access will need to take a hit for marking the FS dirty before allowing the write to go. This includes atime updates for reads, so it's most useful if atime is turned off. One should not include atime as an fs_time event, BTW. If you were paranoid, you could count number of times there was nothing to update, and go after a count, but I think that's overkill. There's really no overhead on a busy FS, since it will always have stuff to update. For an idle FS... well, it doesn't matter. 8-). This is a really useful thing, since it means that you can just turn idle systems off, and have a reasonable expectation of them coming up clean. Idle is defined as "not making many disk writes". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jan 25 15:47:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02550 for current-outgoing; Sun, 25 Jan 1998 15:47:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02544; Sun, 25 Jan 1998 15:47:37 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA23364; Sun, 25 Jan 1998 16:47:36 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd023357; Sun Jan 25 16:47:33 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA17876; Sun, 25 Jan 1998 16:47:31 -0700 (MST) From: Terry Lambert Message-Id: <199801252347.QAA17876@usr02.primenet.com> Subject: Re: stable current? To: dyson@FreeBSD.ORG Date: Sun, 25 Jan 1998 23:47:31 +0000 (GMT) Cc: scottm@cs.ucla.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199801251803.NAA25960@dyson.iquest.net> from "John S. Dyson" at Jan 25, 98 01:03:42 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > > For UNI kernels, John's latest round of vm changes seem to be more > > stable -- OTOH I'm not really pushing things that hard either. > > Rather than announcing the system is "better", I have been holding > out until someone else sees it. The only thing(s) that shouldn't > be working are the layered filesystems. Those thing(s) are really > broken, and absolutely no Lite/2 derivative has them working properly. > > Because of the structure of the merged VM/Buffer cache, we haven't had them > working for, a long time but now at least we have a better chance of someone > fixing them. That's not the only problem; I've identified most of them at one time or another... Were you out here (Bay Area) last Thursday for McKusick's talk at Network Appliance on FS stacking? I didn't go to that one, but I talked to him for about half an hour about a month ago, and he seemed to agree with most of what I identified (plus added a thing or two that I hadn't thought of before). The single biggest problem has *got* to be alias buffers hung off top and bottom vnodes in a stack. The vop_getpages/vop_putpages interface needs to become mandatory for all FS's. No more sneaking around it in the vnode pager. That should solve most of the nullfs and single-layer stack FS problems up front, so long as you don't expect locking to work. A real fix will require a VOP to ask for the backing vnode where the buffers and locks are hung off of; until then, I don't think unionfs has a chance of being safe to use. Terre Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jan 25 15:54:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03543 for current-outgoing; Sun, 25 Jan 1998 15:54:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03537 for ; Sun, 25 Jan 1998 15:54:40 -0800 (PST) (envelope-from kato@migmatite.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.8/3.6Wbeta7) with ESMTP id IAA03605; Mon, 26 Jan 1998 08:54:22 +0900 (JST) To: root@mantar.slip.netcom.com Cc: current@FreeBSD.ORG Subject: Re: kernel build fails From: KATO Takenori In-Reply-To: Your message of "Sun, 25 Jan 1998 12:15:10 -0800 (PST)" References: X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980126085421G.kato@gneiss.eps.nagoya-u.ac.jp> Date: Mon, 26 Jan 1998 08:54:21 +0900 X-Dispatcher: imput version 971024 Lines: 18 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Manfred Antar wrote: > machine/smp.h:173: `cpuid' redeclared as different kind of symbol > machine/cpufunc.h:62: previous declaration of `cpuid' Oops, I did't realize that cpuid symbol has been already used by SMP stuff. I undo'ed my commit. Well, what symbol should be used for cpuid instruction? I'd submit `getcpuid()'. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- From owner-freebsd-current Sun Jan 25 16:13:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05226 for current-outgoing; Sun, 25 Jan 1998 16:13:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05211 for ; Sun, 25 Jan 1998 16:13:22 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id QAA17034 for ; Sun, 25 Jan 1998 16:13:19 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199801260013.QAA17034@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-current@FreeBSD.ORG Subject: -current seems to be okay Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jan 1998 16:13:18 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk After Dyson's posting , I sup the latest -current today, did a make world, rebuilt the kernel, and now I am rebuiding java on the new system . This is all light testing however the system at this stage seems to be holding up. Not sure whats up with Dyson and cvs commit messages, I spotted one commit message from Dyson in the last month or so;however, the cvs update showed several cvs commits. This blind testing for sure makes me want to stay away from the latest -current till I get a confirmation from someone else on the list 8) Cheers, Amancio From owner-freebsd-current Sun Jan 25 17:11:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10373 for current-outgoing; Sun, 25 Jan 1998 17:11:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (ppp6.portal.net.au [202.12.71.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10367 for ; Sun, 25 Jan 1998 17:11:20 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id LAA00501; Mon, 26 Jan 1998 11:34:14 +1030 (CST) Message-Id: <199801260104.LAA00501@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: freebsd-current@FreeBSD.ORG Subject: Re: -current seems to be okay In-reply-to: Your message of "Sun, 25 Jan 1998 16:13:18 -0800." <199801260013.QAA17034@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jan 1998 11:34:14 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > > After Dyson's posting , I sup the latest -current today, did a make world, > rebuilt the kernel, and now I am rebuiding java on the new system . > > This is all light testing however the system at this stage seems to be > holding up. I've been beating my poor underconfigured laptop to death with a kernel from yesterday (and SLICE/DEVFS); it's been 100% solid so far. I can't speak for NFS though. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ From owner-freebsd-current Sun Jan 25 17:19:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11688 for current-outgoing; Sun, 25 Jan 1998 17:19:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11590 for ; Sun, 25 Jan 1998 17:18:57 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id BAA25658; Mon, 26 Jan 1998 01:18:35 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id CAA19638; Mon, 26 Jan 1998 02:18:34 +0100 (MET) Message-ID: <19980126021833.41846@follo.net> Date: Mon, 26 Jan 1998 02:18:33 +0100 From: Eivind Eklund To: Amancio Hasty Cc: freebsd-current@FreeBSD.ORG Subject: Re: -current seems to be okay References: <199801260013.QAA17034@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199801260013.QAA17034@rah.star-gate.com>; from Amancio Hasty on Sun, Jan 25, 1998 at 04:13:18PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On Sun, Jan 25, 1998 at 04:13:18PM -0800, Amancio Hasty wrote: > > After Dyson's posting , I sup the latest -current today, did a make world, > rebuilt the kernel, and now I am rebuiding java on the new system . > > This is all light testing however the system at this stage seems to be > holding up. > > Not sure whats up with Dyson and cvs commit messages, I spotted one > commit message from Dyson in the last month or so;however, the cvs update > showed several cvs commits. This blind testing for sure makes me want > to stay away from the latest -current till I get a confirmation from > someone else on the list 8) It's reasonably stable. As far as I've been able to tell, it hasn't been _that_ unstable anyway; I've been running kernels with all of the problems with less than one 'random crash' a day throughout the period. (I might have been having some memory loss; it has seemed that way.) The above is on my personal workstation; it has some load, but not too intense, of course. And YMMV. BTW: Thanks to John Dyson for the amount of work he has been putting down - John, remind me to buy you a beer if we meet :-) Eivind. From owner-freebsd-current Sun Jan 25 17:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12059 for current-outgoing; Sun, 25 Jan 1998 17:20:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12000 for ; Sun, 25 Jan 1998 17:20:02 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id RAA24169; Sun, 25 Jan 1998 17:19:50 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199801260119.RAA24169@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: -current seems to be okay In-reply-to: Your message of "Mon, 26 Jan 1998 11:34:14 +1030." <199801260104.LAA00501@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jan 1998 17:19:50 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Funny , that you mentioned NFS 8) I just bought a couple of NetGears 10/100 (chipset 21140A ) and have been happily building ports stuff on my nfs mounted partition. ftp transfers are really nice... ftp> get SETUPJS.EXE local: SETUPJS.EXE remote: SETUPJS.EXE 200 PORT command successful. 150 Opening BINARY mode data connection for 'SETUPJS.EXE' (19558148 bytes). 100% |**************************************************| 19099 KB 00:00 ETA 226 Transfer complete. 19558148 bytes received in 4.26 seconds (4.38 MB/s) ftp> I really like the speed on my new net cards 8) Amancio > > > > After Dyson's posting , I sup the latest -current today, did a make world, > > rebuilt the kernel, and now I am rebuiding java on the new system . > > > > This is all light testing however the system at this stage seems to be > > holding up. > > I've been beating my poor underconfigured laptop to death with a kernel > from yesterday (and SLICE/DEVFS); it's been 100% solid so far. I can't > speak for NFS though. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ > > From owner-freebsd-current Sun Jan 25 17:24:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13427 for current-outgoing; Sun, 25 Jan 1998 17:24:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (ppp6.portal.net.au [202.12.71.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13413 for ; Sun, 25 Jan 1998 17:24:04 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id LAA00637; Mon, 26 Jan 1998 11:46:51 +1030 (CST) Message-Id: <199801260116.LAA00637@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: apm on toshiba In-reply-to: Your message of "Sun, 25 Jan 1998 23:32:55 -0000." <199801252332.QAA17175@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jan 1998 11:46:51 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > > No. You can hotkey through your power settings, and organise your > > disk spindown with the BIOS setup, but if you want to let the disk spin > > down you need to stretch the update time out further. > > The update time only applies to dirty buffers. If you don't dirty any > buffers, you won't spin up for update writes. If you do dirty buffers, > you are probably doing reads to do it, so your disk will already be spun > up. Either way, it should not be necessary to hack updated. You don't need to hack anything, just tune kern.update. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ From owner-freebsd-current Sun Jan 25 17:30:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15108 for current-outgoing; Sun, 25 Jan 1998 17:30:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15099 for ; Sun, 25 Jan 1998 17:30:44 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.7) with SMTP id RAA15590; Sun, 25 Jan 1998 17:30:36 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Sun, 25 Jan 1998 17:30:36 -0800 (PST) From: Chris Timmons To: Amancio Hasty cc: freebsd-current@FreeBSD.ORG Subject: Re: -current seems to be okay In-Reply-To: <199801260119.RAA24169@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Well a really good test of -current and NFS would be to try and build the xemacs20 port from -current with /usr/ports mounted from a -stable host. I won't have time to try that for a couple of days. -Chris On Sun, 25 Jan 1998, Amancio Hasty wrote: > > Funny , that you mentioned NFS 8) > > I just bought a couple of NetGears 10/100 (chipset 21140A ) and have been > happily building ports stuff on my nfs mounted partition. > > ftp transfers are really nice... > > ftp> get SETUPJS.EXE > local: SETUPJS.EXE remote: SETUPJS.EXE > 200 PORT command successful. > 150 Opening BINARY mode data connection for 'SETUPJS.EXE' (19558148 bytes). > 100% |**************************************************| 19099 KB 00:00 ETA > 226 Transfer complete. > 19558148 bytes received in 4.26 seconds (4.38 MB/s) > ftp> > > > > I really like the speed on my new net cards 8) > > Amancio > > > > > > > > After Dyson's posting , I sup the latest -current today, did a make world, > > > rebuilt the kernel, and now I am rebuiding java on the new system . > > > > > > This is all light testing however the system at this stage seems to be > > > holding up. > > > > I've been beating my poor underconfigured laptop to death with a kernel > > from yesterday (and SLICE/DEVFS); it's been 100% solid so far. I can't > > speak for NFS though. > > > > -- > > \\ Sometimes you're ahead, \\ Mike Smith > > \\ sometimes you're behind. \\ mike@smith.net.au > > \\ The race is long, and in the \\ msmith@freebsd.org > > \\ end it's only with yourself. \\ > > > > > > From owner-freebsd-current Sun Jan 25 18:28:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20049 for current-outgoing; Sun, 25 Jan 1998 18:28:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20043 for ; Sun, 25 Jan 1998 18:28:31 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.7) with ESMTP id VAA04328; Sun, 25 Jan 1998 21:48:49 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199801252148.VAA04328@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Phil Staub cc: freebsd-current@FreeBSD.ORG Subject: Re: ppp (iij) doesn't recognize carrier loss anymore In-reply-to: Your message of "Sat, 24 Jan 1998 20:30:50 PST." <34CABFFA.41C67EA6@casagate.plan.pixelogix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jan 1998 21:48:49 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > Brian Somers wrote: > [brian@worldcontrol.com's description of non-hangup problems deleted] > > > > Check out the FAQ on http://www.FreeBSD.org/FAQ/userppp.html. I > > haven't heard of any other problems with the current ppp in that > > area (but there *were* such problems in 2.2.5). > > Can you point me to a paragraph in the FAQ or other reference to the > problems you alluded to in 2.2.5? > > I just brought up a ppp server whose ppp session won't die if the user > at the client machine kills (i.e., via kill -9) *his* end of the > session. Once this has happened, further attempts to dial in fail (the > modem never answers) and the ppp process must be manually killed. > > However, if the idle timeout expires and the connection shuts down that > way, the next dial works just fine. In this case, I'm not sure whether > the ppp process itself shuts down or not. > > I'm sure another piece you'll need to know is that I am using mgetty, > with the setup instructions essentially copied from the online (at > freebsd.org) manual. > > I've looked in what seemed to be the obvious places (FAQ's, Manual, Man > pages) and haven't seen reference to this problem. Can you help? The problems with ppp in 2.2.5 are mentioned at http://www.FreeBSD.org/releases/2.2.5R/errata.html I'd advise trying the latest version (available on http://www.FreeBSD.org/~brian), and also making sure that you have ``normal CD operations'' set on your modem (it should *not* fake carrier detect). > -- > Phil Staub, KE7HC Senior Software Engineer > phils@pixelogix.com Audio Precision, Inc. > or phils@audioprecision.com Beaverton, OR 97075, (800) 231-7350 -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-current Sun Jan 25 18:33:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20974 for current-outgoing; Sun, 25 Jan 1998 18:33:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20969; Sun, 25 Jan 1998 18:33:42 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA00373; Sun, 25 Jan 1998 21:25:26 -0500 (EST) (envelope-from toor) Message-Id: <199801260225.VAA00373@dyson.iquest.net> Subject: Re: stable current? In-Reply-To: <199801252347.QAA17876@usr02.primenet.com> from Terry Lambert at "Jan 25, 98 11:47:31 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sun, 25 Jan 1998 21:25:26 -0500 (EST) Cc: dyson@FreeBSD.ORG, scottm@cs.ucla.edu, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk Terry Lambert said: > > Were you out here (Bay Area) last Thursday for McKusick's talk at > Network Appliance on FS stacking? I didn't go to that one, but I > talked to him for about half an hour about a month ago, and he > seemed to agree with most of what I identified (plus added a thing > or two that I hadn't thought of before). > I identified almost everything that you have also. > > The single biggest problem has *got* to be alias buffers hung off top and > bottom vnodes in a stack. The vop_getpages/vop_putpages interface needs > to become mandatory for all FS's. No more sneaking around it in the > vnode pager. That should solve most of the nullfs and single-layer > stack FS problems up front, so long as you don't expect locking to > work. A real fix will require a VOP to ask for the backing vnode where > the buffers and locks are hung off of; until then, I don't think unionfs > has a chance of being safe to use. > Well, you are right, and the code supports it. PLEASE look at the code before you whine about the way things should be. I really don't think that you look at how things work before you complain. There is some (default) generic code in the vnode pager, that works. You seem to be talking about the way things were in 2.0. (Over 2yrs ago.) Putpages currently uses the VOP_WRITE entry point in the filesystems. Each filesystem can support it's own putpages if that is better in some way or more efficient. Old filesystems can use the generic code. Likewise, getpages. Note how I fixed nfs_getpages, in order to fix some deadlock issues. Things are pretty much interchangeable, because we truly do use the VM object for all (VREG) filesystem buffering. It does NOT violate layering to use VOP_READ/VOP_WRITE or the filesystem strategy, to emulate getpages and putpages. There is no bypassing of the filesystem anymore in our code. There is almost NO difference between a getpages/ putpages interface, and the nocopy version of VOP_READ/VOP_WRITE. Swap_pager does talk directly to the underlying device, but that is a different story. I also don't want to hear about how that should be redone -- there are endless deadlock conditions and performance issues. Geesh, ccd as it is isn't even appropriate for swap pager (it will work, sort of.) I strongly suggest UTSL. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Sun Jan 25 18:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22290 for current-outgoing; Sun, 25 Jan 1998 18:48:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22282; Sun, 25 Jan 1998 18:48:31 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA00479; Sun, 25 Jan 1998 21:48:29 -0500 (EST) (envelope-from toor) Message-Id: <199801260248.VAA00479@dyson.iquest.net> Subject: Re: stable current? In-Reply-To: <199801260225.VAA00373@dyson.iquest.net> from "John S. Dyson" at "Jan 25, 98 09:25:26 pm" To: dyson@FreeBSD.ORG Date: Sun, 25 Jan 1998 21:48:29 -0500 (EST) Cc: tlambert@primenet.com, dyson@FreeBSD.ORG, scottm@cs.ucla.edu, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk John S. Dyson said: > > Well, you are right, and the code supports it. > Following up my own comments: The pager code has supported whatever the filesystems do. This becomes more of an issue with the layered filesystems, and the major impediment that we have had is that the VM object could not be shared across vnodes, and now it can. (Theoretically, we could layer UFS onto other filesystems, but I am not worried about that right now.) Sure there are some layering issues as you have suggested, but I have also known about them. There has been alot more wrong than even you have ever talked about (at least to me.) If this was an easy thing to fix, I would have a long time ago. There are few, if any revelations in what you have said, but damn it, it doesn't hurt to work in parallel, until I hear complaints that don't solve them, or someone who discounts the complexity of problems. Almost none of the problems that we have had are due to the conventional filesystem implementations. I can write a native getpages or putpages in a few hours. It is the layering, and the vnode pager is pretty much not an issue, and hasn't been for the last 2yrs. If the vnode pager implements a default getpages or putpages interface, who cares? The layered filesystems will supply their own. Figure this: I fixed our object reference problem in about 3-4wks. PHK has fixed the vnode caching/reference problem over at least several weeks (I don't know how long.) I can fix the entire FS layering problem in two weeks full time. I can add getpages/putpages to UFS in an hour (we already have a valid getpages/putpages for UFS anyway :-)). Tell me where most of the work is? The time to implement a getpages and putpages is childs-play. The layering structure itself has been in place for two years. Again, read-my-lips, we already have the getpages/putpages abstraction. For example, vnode_pager uses VOP_WRITE for UFS filesystem putpages. (That is totally valid, if not slightly more inefficient than it might be.) vnode_pager uses ufs_getpages which uses spec_getpages for UFS filesystem getpages. (That is also totally valid, and is an example of a full implementation of the abstraction.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Sun Jan 25 19:26:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26045 for current-outgoing; Sun, 25 Jan 1998 19:26:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26040 for ; Sun, 25 Jan 1998 19:26:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA00587; Sun, 25 Jan 1998 19:25:18 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199801260325.TAA00587@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Chris Timmons cc: freebsd-current@FreeBSD.ORG Subject: Re: -current seems to be okay In-reply-to: Your message of "Sun, 25 Jan 1998 17:30:36 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jan 1998 19:25:18 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Good suggestion, my test box crashed trying to dump xemacs: Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under the name xemacs Purespace usage: 705420 of 705932 (100%). Going to try later on after I upgrade my test box to today's current. My main system , rah, is running today's current. Cheers, Amancio > > Well a really good test of -current and NFS would be to try and build the > xemacs20 port from -current with /usr/ports mounted from a -stable host. > I won't have time to try that for a couple of days. > > -Chris > > On Sun, 25 Jan 1998, Amancio Hasty wrote: > > > > > Funny , that you mentioned NFS 8) > > > > I just bought a couple of NetGears 10/100 (chipset 21140A ) and have been > > happily building ports stuff on my nfs mounted partition. > > > > ftp transfers are really nice... > > > > ftp> get SETUPJS.EXE > > local: SETUPJS.EXE remote: SETUPJS.EXE > > 200 PORT command successful. > > 150 Opening BINARY mode data connection for 'SETUPJS.EXE' (19558148 bytes). > > 100% |**************************************************| 19099 KB 00:00 ETA > > 226 Transfer complete. > > 19558148 bytes received in 4.26 seconds (4.38 MB/s) > > ftp> > > > > > > > > I really like the speed on my new net cards 8) > > > > Amancio > > > > > > > > > > > > After Dyson's posting , I sup the latest -current today, did a make world, > > > > rebuilt the kernel, and now I am rebuiding java on the new system . > > > > > > > > This is all light testing however the system at this stage seems to be > > > > holding up. > > > > > > I've been beating my poor underconfigured laptop to death with a kernel > > > from yesterday (and SLICE/DEVFS); it's been 100% solid so far. I can't > > > speak for NFS though. > > > > > > -- > > > \\ Sometimes you're ahead, \\ Mike Smith > > > \\ sometimes you're behind. \\ mike@smith.net.au > > > \\ The race is long, and in the \\ msmith@freebsd.org > > > \\ end it's only with yourself. \\ > > > > > > > > > > > From owner-freebsd-current Mon Jan 26 00:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23062 for current-outgoing; Mon, 26 Jan 1998 00:12:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (tc1-dialin10.nanospace.com [205.199.198.210]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA23057 for ; Mon, 26 Jan 1998 00:12:06 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 526 invoked by uid 100); 26 Jan 1998 08:13:35 -0000 Message-ID: <19980126001331.05717@top.worldcontrol.com> Date: Mon, 26 Jan 1998 00:13:31 -0800 To: Randy Terbush , current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? References: <19980125093559D.randy@covalent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.15i In-Reply-To: <19980125093559D.randy@covalent.net>; from Randy Terbush on Sun, Jan 25, 1998 at 09:35:59AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On %M %N, Randy Terbush wrote: > I have a dual P6 machine with a Cy-16Ye running the latest > current. > > The Hylafax faxgetty and faxq processes spin out of control > chewing up nearly 100% CPU. The same configuration ran without > problems on a single P5 machine running 2.2-STABLE. > > As I begin to dig deeper into this, are there any know problems > with this mix? Just thought you'd like to know you are not alone. faxq on my SMP system does the same thing. -- Brian Litzinger From owner-freebsd-current Mon Jan 26 00:24:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24860 for current-outgoing; Mon, 26 Jan 1998 00:24:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24855 for ; Mon, 26 Jan 1998 00:24:38 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id AAA02827; Mon, 26 Jan 1998 00:24:27 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199801260824.AAA02827@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: brian@worldcontrol.com cc: Randy Terbush , current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? In-reply-to: Your message of "Mon, 26 Jan 1998 00:13:31 PST." <19980126001331.05717@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jan 1998 00:24:27 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Any clues as to where is spending its time?? Cheers, Amancio > On %M %N, Randy Terbush wrote: > > I have a dual P6 machine with a Cy-16Ye running the latest > > current. > > > > The Hylafax faxgetty and faxq processes spin out of control > > chewing up nearly 100% CPU. The same configuration ran without > > problems on a single P5 machine running 2.2-STABLE. > > > > As I begin to dig deeper into this, are there any know problems > > with this mix? > > Just thought you'd like to know you are not alone. faxq on > my SMP system does the same thing. > > -- > Brian Litzinger From owner-freebsd-current Mon Jan 26 00:59:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27861 for current-outgoing; Mon, 26 Jan 1998 00:59:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (tc1-dialin10.nanospace.com [205.199.198.210]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA27856 for ; Mon, 26 Jan 1998 00:59:10 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 1214 invoked by uid 100); 26 Jan 1998 08:54:00 -0000 Message-ID: <19980126005356.16731@top.worldcontrol.com> Date: Mon, 26 Jan 1998 00:53:56 -0800 To: Amancio Hasty , brian@worldcontrol.com Cc: Randy Terbush , current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? References: <19980126001331.05717@top.worldcontrol.com> <199801260824.AAA02827@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.15i In-Reply-To: <199801260824.AAA02827@rah.star-gate.com>; from Amancio Hasty on Mon, Jan 26, 1998 at 12:24:27AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > > On %M %N, Randy Terbush wrote: > > > The Hylafax faxgetty and faxq processes spin out of control > > > chewing up nearly 100% CPU. Brian Litzinger wrote: > > Just thought you'd like to know you are not alone. faxq on > > my SMP system does the same thing. On %M %N, Amancio Hasty wrote: > Any clues as to where is spending its time?? The program gives no clues. Regretably it seems to perpetually be in the RUN state. However, I have a guess. I suspect that a select (poll?) call is returning with nothing set. The program is getting into an infinite loop calling select. I've found that the program does work. It is just consuming 100% of 1 CPU. I believe the problem is not SMP related. I.E. it will happen in uni-processor mode too. -- Brian Litzinger From owner-freebsd-current Mon Jan 26 01:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28509 for current-outgoing; Mon, 26 Jan 1998 01:03:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-ppp86.well.com [206.15.84.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28504 for ; Mon, 26 Jan 1998 01:03:31 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id BAA00937 for ; Mon, 26 Jan 1998 01:05:04 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 26 Jan 1998 01:05:03 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org Reply-To: Alex To: current Subject: inetd patch/idea Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-248059714-885805503=:437" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-248059714-885805503=:437 Content-Type: TEXT/PLAIN; charset=US-ASCII I've been messing around with a little program that provides a front end for inetd.conf, and in doing so, I noticed two things: 1.) inetd.conf wasn't re-read on reception of a SIGHUP 2.) When a SIGTERM is recieved, inetd died a horrible death and didn't clean up its pid file. A little investigation proved that all the code for the re-reading of inet.conf was actually there, however, it was among the list of signals to be blocked. I haven't seen any ill effects of removing it from the list, however if there are any, it's simple enough to generate two lists of signals to be blocked. El hombre mas brillante dijo una vez "Cuidado hay NT". (it's a nerd thing) - alex --0-248059714-885805503=:437 Content-Type: APPLICATION/octet-stream; name="inetd.diff.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: H4sICExQzDQCA2luZXRkLmRpZmYAlVV/b9s2EP2b+hTXDJhlS3acH7WdBFmT ZWmbLcGKLEM3DINDS5TERiIFkrITdPnuu6PkIEm7rhUgyxTv3t17d0cNh0OQ Srh0lIy0kTm70Ap+5gq2JzAe7+/u7o8nsLW3NwuiKFpbPjN6Od3ffdkaHR3B cLITb40hah9HRwHAAFwhwIpEqxTcXS1AZ7g0S2Hg+tpKlZdi6AojeCrSXm9E Lt7tjOJBY4UFDuidybwx3EkMn8lSwKqQSQHSArkCd2AdN66pgyE6c5XGUGtr 5aK8i/2urgSU3GFYJ/GvVOhoa62sAKcxRMFV3tRgZa54OfIoV5j5ZyJjzOvr zAgBmTYVd70erKQrcFOUqYVcLoUifCTuYbRJMaot9ErBQpR6NQI40cpJ1bSo JWprCQzzBqGcuYOqsQ6NUR6P3ZICW/MEBUQKfIEgx2W5DtrZQ42kEIHCC476 eLRREK01+R/a/03ZQ3wt7c9Q9v7fyPo5Y4/x9aS7TmLUbRJRFK8EY2zthdab wiWb3balKLTnfegie0zBJXXV3EJn5tt8a3cSTyFqH9Tm36UiQzrs8vTq8s+r s4tTFk7Gg61xn7HNASpO5HhGzbeQOAcYqRuBjMsSBpsPCHBx/Mcc75O35z+x ne3pZOoRKn4LvEQd+QKrQaukkGVqUHFyDobrBH47e/Pj+a8nv7AQK1pxexPi GwLr//Poxdvf3z1ZH59fXvT7QfRtKJ0XBCilY6lYNDkcwvigXZe6W5Fg29uz eAIRPVrBkoIbBu01sDeyhvn8XRjSaxgM+n0Esc40ifNCYfFh0NXB22EAb0OB GL5f+z/3oYb3ltFSy5SxXLs5MsBCVE+BAmgNGmVELi0amDppTdYvPknIirr1 JYY7U89wZ7oXzzxDhnGWIunkjuF7u4zhIUG/B4P+mACYXY7sco6jmJYY55CO tNoX+OAJDlXgS0DRJ0CP+B4A9tH7Ak9A6ruC17VQIqVDAA14QiP56hV1U/Qo 4tXp5cUXU8f8PuJNPdqOKs1zykWFJwxhawy2MtIJHMqlNFpVNKhkVFsK5qdp NhvHuzhOs9lOvN32B2P3+EM3Dk9jVGiI330QtZUMokfMqEmxeRnWkrJDu4+4 8q3kxK37a2v8N2nz+uz8FAbZvJbpYaaRfYj/5nS8xRtmg+AJI4Pwhbfpk15n GUgHqUxVzwH5xPCBjo9UilYqJm6lC8edd5YLZ0MKit+/uIU58OK8L4TqWX82 lhwB/DfoTjeog0xhxS38gF/MVObS2bYKXTLcaekR+/AC6ykc2of9PmuTIzwC WH+X/GmKMFkmDAn9NEc/cORZG50bXj0j00Vs02aMrflj3i31pNT42ZBr2Myv O/tWgEbhqX7zIGxHHlFWmCe3FhsOjzGf9oYT1tmNGAgKL0ztRnZ7ng5xwUEo 22gPOsN98C8uCBzyuQgAAA== --0-248059714-885805503=:437-- From owner-freebsd-current Mon Jan 26 02:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06165 for current-outgoing; Mon, 26 Jan 1998 02:14:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06155 for ; Mon, 26 Jan 1998 02:14:36 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id FAA00431; Mon, 26 Jan 1998 05:14:29 -0500 (EST) (envelope-from toor) Message-Id: <199801261014.FAA00431@dyson.iquest.net> Subject: Re: Cyclades/Hylafax/SMP select problems? In-Reply-To: <19980126001331.05717@top.worldcontrol.com> from "brian@worldcontrol.com" at "Jan 26, 98 00:13:31 am" To: brian@worldcontrol.com Date: Mon, 26 Jan 1998 05:14:28 -0500 (EST) Cc: randy@covalent.net, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk brian@worldcontrol.com said: > On %M %N, Randy Terbush wrote: > > I have a dual P6 machine with a Cy-16Ye running the latest > > current. > > > > The Hylafax faxgetty and faxq processes spin out of control > > chewing up nearly 100% CPU. The same configuration ran without > > problems on a single P5 machine running 2.2-STABLE. > > > > As I begin to dig deeper into this, are there any know problems > > with this mix? > > Just thought you'd like to know you are not alone. faxq on > my SMP system does the same thing. > Sometimes the output of ktrace or truss can be useful. Also the contents of /proc//map sometimes helps with hints as to what is going on. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Jan 26 03:20:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09770 for current-outgoing; Mon, 26 Jan 1998 03:20:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sierra.covalent.net (sierra.covalent.net [208.214.58.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09765; Mon, 26 Jan 1998 03:20:35 -0800 (PST) (envelope-from randy@covalent.net) Received: from localhost (localhost [127.0.0.1]) by sierra.covalent.net (8.8.8/8.8.2) with ESMTP id FAA21924; Mon, 26 Jan 1998 05:20:34 -0600 (CST) To: dyson@FreeBSD.ORG Cc: brian@worldcontrol.com, current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? In-Reply-To: Your message of "Mon, 26 Jan 1998 05:14:28 -0500 (EST)" <199801261014.FAA00431@dyson.iquest.net> References: <199801261014.FAA00431@dyson.iquest.net> X-Mailer: Mew version 1.92.4 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980126052032B.randy@covalent.net> Date: Mon, 26 Jan 1998 05:20:32 -0600 From: Randy Terbush X-Dispatcher: imput version 971024 Lines: 23 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk "John S. Dyson" wrote: > > > The Hylafax faxgetty and faxq processes spin out of control > > > chewing up nearly 100% CPU. The same configuration ran without > > > problems on a single P5 machine running 2.2-STABLE. > > > > > > As I begin to dig deeper into this, are there any know problems > > > with this mix? > > > > Just thought you'd like to know you are not alone. faxq on > > my SMP system does the same thing. > > > Sometimes the output of ktrace or truss can be useful. Also the > contents of /proc//map sometimes helps with hints as to > what is going on. Seems that a change to open the FIFO O_RDWR solves the problem. Apparently, select() is returning when it should not be. This must be a new bug in select(). From owner-freebsd-current Mon Jan 26 04:13:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14600 for current-outgoing; Mon, 26 Jan 1998 04:13:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baloon.mimi.com (sjx-ca115-49.ix.netcom.com [207.223.162.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14595 for ; Mon, 26 Jan 1998 04:13:43 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by baloon.mimi.com (8.8.8/8.8.8) id EAA12143; Mon, 26 Jan 1998 04:13:29 -0800 (PST) (envelope-from asami) Date: Mon, 26 Jan 1998 04:13:29 -0800 (PST) Message-Id: <199801261213.EAA12143@baloon.mimi.com> To: rlb@mindspring.com CC: freebsd-current@FreeBSD.ORG In-reply-to: <34C90AD2.35D0F115@mindspring.com> (message from Ron Bolin on Fri, 23 Jan 1998 16:25:38 -0500) Subject: Re: Current-3.0 bsd.ports.mk Question From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk * In compiling say, "xperfmon++-1.40" from the ports Makefile I get the * following error: * * * rlb3:...sysutils/xperfmon>make * ===> xperfmon++-1.40 : You have an old tcl installation on your * machine. Remove everything that matches /usr/X11R6/*/*tcl* first. * * I have seen other ports give the same error since early January. What do * I need to do * to make this work? I even did as the messag reports rm -rf * /usr/X11R6/*/*tcl* * without success. BTW, I have tclsh8.0 installed. Yipes. I meant to say "/usr/local/*/*tcl*". Obviouly there is no tcl in /usr/X11R6. Satoshi From owner-freebsd-current Mon Jan 26 05:40:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21956 for current-outgoing; Mon, 26 Jan 1998 05:40:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21950; Mon, 26 Jan 1998 05:40:32 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA30019; Tue, 27 Jan 1998 00:33:55 +1100 Date: Tue, 27 Jan 1998 00:33:55 +1100 From: Bruce Evans Message-Id: <199801261333.AAA30019@godzilla.zeta.org.au> To: dyson@FreeBSD.ORG, randy@covalent.net Subject: Re: Cyclades/Hylafax/SMP select problems? Cc: brian@worldcontrol.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk >Seems that a change to open the FIFO O_RDWR solves the problem. >Apparently, select() is returning when it should not be. This >must be a new bug in select(). More likely, select() is returning when it should be. Fifos used to have a bug that caused them to hang (in the not-O_NONBLOCK case) for all except the first read on a fifo with no writers. select() should have had bug for bug compatibility with read(). Now it should return immediately if there are no writers. O_RDWR might work around a bug in hylafax by ensuring that there is always a writer. Bruce From owner-freebsd-current Mon Jan 26 06:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25171 for current-outgoing; Mon, 26 Jan 1998 06:13:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mexcom.net ([200.38.135.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25158 for ; Mon, 26 Jan 1998 06:13:28 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from mc.mexcom.net (ppp-7.mexcom.net [206.103.65.199]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id IAA00497 for ; Mon, 26 Jan 1998 08:12:44 -0600 (CST) Message-ID: <34CC9B40.1CFBAE39@ver1.telmex.net.mx> Date: Mon, 26 Jan 1998 08:18:41 -0600 From: eculp Organization: MexCom X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-971226-SNAP i386) MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Subject: make release from 25/jan/98. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk After my make world, new kernel then make release I got this on both current and releng_2_2. I did the same on 24/jan/98 and it worked fine. cd /var/ftp/release/usr && rm -rf doc && cvs -d /home/ncvs co -P doc cvs [checkout aborted]: there is no repository /home/ncvs/doc *** Error code 1 Stop. Thanks ed P.D. cvsuping to try again. From owner-freebsd-current Mon Jan 26 06:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28906 for current-outgoing; Mon, 26 Jan 1998 06:45:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28893 for ; Mon, 26 Jan 1998 06:45:56 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA32178; Tue, 27 Jan 1998 01:42:11 +1100 Date: Tue, 27 Jan 1998 01:42:11 +1100 From: Bruce Evans Message-Id: <199801261442.BAA32178@godzilla.zeta.org.au> To: kato@migmatite.eps.nagoya-u.ac.jp, root@mantar.slip.netcom.com Subject: Re: kernel build fails Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk >> machine/smp.h:173: `cpuid' redeclared as different kind of symbol >> machine/cpufunc.h:62: previous declaration of `cpuid' > >Oops, I did't realize that cpuid symbol has been already used by SMP >stuff. I undo'ed my commit. > >Well, what symbol should be used for cpuid instruction? I'd submit >`getcpuid()'. cpuid() :-). The SMP name is poor. Bruce From owner-freebsd-current Mon Jan 26 09:08:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16664 for current-outgoing; Mon, 26 Jan 1998 09:08:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16647 for ; Mon, 26 Jan 1998 09:08:35 -0800 (PST) (envelope-from sasdrq@unx.sas.com) Received: from mozart (wether.sas.com [192.35.83.7]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id MAA19208 for ; Mon, 26 Jan 1998 12:08:27 -0500 (EST) Received: from gamecock.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA06011; Mon, 26 Jan 1998 12:08:26 -0500 Received: by gamecock.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA07176; Mon, 26 Jan 1998 12:08:26 -0500 From: David Quattlebaum Message-Id: <199801261708.AA07176@gamecock.unx.sas.com> Subject: symorder: Cannot allocate memory To: freebsd-current@FreeBSD.ORG (current) Date: Mon, 26 Jan 1998 12:08:26 -0500 (EST) X-Mailer: ELM [version 2.5 PL0b1] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk I am trying to build a debug kernel at 3.0-current and keep getting: loading kernel rearranging symbols symorder: Cannot allocate memory I am running this on a Dell 200MHz GXpro with 128M memory. I tried this with a GENERIC config file and ran "config -g GENERIC" before then trying the "make depend && make". I tried the same thing at home at 3.0-121297-SNAP on a P5-120 with only 16M memory and everything worked fine. Bug or user error? -- David Quattlebaum, (sasdrq@unx.sas.com) < "Weebles wobble but they don't fall down." From owner-freebsd-current Mon Jan 26 09:08:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16678 for current-outgoing; Mon, 26 Jan 1998 09:08:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chassiron.ensta.fr (root@chassiron.ensta.fr [147.250.7.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16624 for ; Mon, 26 Jan 1998 09:08:21 -0800 (PST) (envelope-from bouyer@chassiron.ensta.fr) Received: (from bouyer@localhost) by chassiron.ensta.fr (8.8.8/8.8.5) id SAA07023; Mon, 26 Jan 1998 18:07:53 +0100 (MET) Message-Id: <199801261707.SAA07023@chassiron.ensta.fr> Date: Mon, 26 Jan 1998 18:07:49 +0100 From: bouyer@chassiron.ensta.fr (Manuel Bouyer) To: port-i386@netbsd.org, freebsd-current@FreeBSD.ORG Subject: AMD k6 and > 32Mb RAM X-Mailer: Mutt 0.48.1 Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Hi, Does anybody know if a K6 can run with 64Mb (or more) of RAM ? I've heard that there was a silicon bug in the earlier K6 that would make it not manage properly the RAM, but I don't know if it has been fixed. Thanks ... -- Manuel Bouyer, LIP6, Universite Paris VI. email: bouyer@rp.lip6.fr bouyer@ensta.fr -- From owner-freebsd-current Mon Jan 26 09:40:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22452 for current-outgoing; Mon, 26 Jan 1998 09:40:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from seera.nttlabs.com (seera.nttlabs.com [204.162.36.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22410; Mon, 26 Jan 1998 09:40:16 -0800 (PST) (envelope-from gene@nttlabs.com) Received: from nttlabs.com (localhost [127.0.0.1]) by seera.nttlabs.com (8.8.8/8.8.7) with ESMTP id JAA28495; Mon, 26 Jan 1998 09:39:41 -0800 (PST) Message-ID: <34CCCA5B.7B5AA8FD@nttlabs.com> Date: Mon, 26 Jan 1998 09:39:39 -0800 From: "Eugene M. Kim" Organization: NTT Multimedia Communications Laboratories X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Hardware FreeBSD ML CC: Current FreeBSD ML , "Eugene M. Kim" Subject: Re: ie0 and EE16 References: <199801201816.MAA24372@compound.east.sun.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Greetings, Tony Kimball wrote: > > Just FYI, the ie driver consistently fails for me after several days > of use, with an EE16 card. The mode: network activity stops (by the > hub light); no messages are logged; ping returns "sendto: no buffer > space available"; 'ifconfig ie0 down; ifconfig ie0 up' causes ping > to stop reporting errors, but no network activity occurs until reboot. > > Strangely, I've never seen this effect with NFS traffic, only with X, > and specific applications seem to trigger it: Acroread, or netscape, > for example, but not ghostview. My 3COM 3C509-TP ISA card (ep) does, too. The network activity on ep0 stops almost invariably when I use Netscape on another Win95 PC and try to download something big which imposes a load on the network continuously. It also stops when using Acroread. The symptom is exactly the same as Mr. Kimball's one, that is, some programs including ping report that there is no buffer space available, and also ifconfig ep0 shows that OACTIVE attribute is set on the interface; does this ring a bell to anyone? I CC'ed this message to FreeBSD-current mailing list because I had not seen this problem until the world was rebuilt with a recent -current source tree. This problem was first seen about a week ago. Hope this helped and thanks much, Gene -- Eugene M. Kim Software Developer NTT Multimedia Communications Laboratories mailto:gene@nttlabs.com From owner-freebsd-current Mon Jan 26 09:41:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22903 for current-outgoing; Mon, 26 Jan 1998 09:41:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [209.4.59.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22881 for ; Mon, 26 Jan 1998 09:41:13 -0800 (PST) (envelope-from bofh@terranova.net) Received: from guenhwyvar.TerraNova.net (tog@guenhwyvar.TerraNova.net [209.4.59.4]) by obiwan.TerraNova.net (8.8.8/TNN/3.0) with SMTP id MAA13082; Mon, 26 Jan 1998 12:37:16 -0500 (EST) Message-ID: <34CCC9EB.6@terranova.net> Date: Mon, 26 Jan 1998 12:37:47 -0500 From: Travis Mikalson X-Mailer: Mozilla 3.03 (Win95; I) MIME-Version: 1.0 To: Manuel Bouyer CC: port-i386@netbsd.org, freebsd-current@FreeBSD.ORG Subject: Re: AMD k6 and > 32Mb RAM References: <199801261707.SAA07023@chassiron.ensta.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Manuel Bouyer wrote: > > Hi, > Does anybody know if a K6 can run with 64Mb (or more) of RAM ? I've heard that > there was a silicon bug in the earlier K6 that would make it not manage > properly the RAM, but I don't know if it has been fixed. > > Thanks ... I'm currently running a K6/233 w/ 128 megs of EDO in my proxy server. It's been working great so far under the light load; 20 day uptime at the moment. (Running FreeBSD) I got the chip a few months ago, I believe it was manufactured some time in 5/97 Perhaps you're thinking of the Intel 430FX, VX and TX chipsets which have a limitation in which the L2 cache is disabled when more than 64 megs of RAM is used? Just get a very big heatsink and fan for it and keep it ventilated and it should be fine. (heat grease is a good idea, too) -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- Duct tape is like the force. It has a light side, and a dark side, and it holds the universe together ... -- Carl Zwanzig From owner-freebsd-current Mon Jan 26 10:17:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28589 for current-outgoing; Mon, 26 Jan 1998 10:17:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from veda.is (adam@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28580 for ; Mon, 26 Jan 1998 10:17:06 -0800 (PST) (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.8.8/8.8.8) id SAA21845 for current@freebsd.org; Mon, 26 Jan 1998 18:16:38 GMT (envelope-from adam) From: Adam David Message-Id: <199801261816.SAA21845@veda.is> Subject: bootstrap, *-tools To: current@FreeBSD.ORG Date: Mon, 26 Jan 1998 18:16:38 +0000 (GMT) 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-current@FreeBSD.ORG Precedence: bulk Normally when rebuilding the world, it shouldn't be strictly necessary to always make bootstrap, include-tools, lib-tools, build-tools. 1. Wouldn't it be alright to 'make -DNOCLEAN -DNOOBJDIR -DNOTOOLS buildworld' in order to speed up the build at such times? 2. Is it necessary to build all these tools (including "bootstrap") the first time through buildworld in order to correctly complete the build that time? Upgrading from 2.x to 3.x or other similar quantum leaps do not concern me here, but it seems odd that rebuilding -current:today when -current:yesterday is present in the build tree (and perhaps also installed) should typically not require these additional steps. -- Adam David From owner-freebsd-current Mon Jan 26 10:50:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04475 for current-outgoing; Mon, 26 Jan 1998 10:50:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04470 for ; Mon, 26 Jan 1998 10:50:18 -0800 (PST) (envelope-from murray@pike.cdrom.com) Received: from localhost (murray@localhost) by pike.cdrom.com (8.8.8/8.8.7) with SMTP id KAA10696; Mon, 26 Jan 1998 10:51:24 -0800 (PST) (envelope-from murray@pike.cdrom.com) Date: Mon, 26 Jan 1998 10:51:24 -0800 (PST) From: Murray Stokely To: Manuel Bouyer cc: port-i386@netbsd.org, freebsd-current@FreeBSD.ORG Subject: Re: AMD k6 and > 32Mb RAM In-Reply-To: <199801261707.SAA07023@chassiron.ensta.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk That was with very early K6's that you shouldn't be able to find on the market anymore. You should be able to find the exact stepping #'s of chips with the problem by searching Dejanews if you need to though. On Mon, 26 Jan 1998, Manuel Bouyer wrote: % Does anybody know if a K6 can run with 64Mb (or more) of RAM ? I've heard that % there was a silicon bug in the earlier K6 that would make it not manage % properly the RAM, but I don't know if it has been fixed. Murray Stokely From owner-freebsd-current Mon Jan 26 11:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09909 for current-outgoing; Mon, 26 Jan 1998 11:32:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09902 for ; Mon, 26 Jan 1998 11:32:48 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id LAA20307; Mon, 26 Jan 1998 11:32:55 -0800 (PST) To: eculp cc: FreeBSD-current@FreeBSD.ORG Subject: Re: make release from 25/jan/98. In-reply-to: Your message of "Mon, 26 Jan 1998 08:18:41 CST." <34CC9B40.1CFBAE39@ver1.telmex.net.mx> Date: Mon, 26 Jan 1998 11:32:55 -0800 Message-ID: <20303.885843175@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk I've said this before and I'll say it again: 1. The make release target is for experts only. 2. If you feel yourself to be an expert then you MUST then at least take care to read and *thoroughly understand* /usr/src/release/Makefile. In this case, as the file plainly shows, the doc distribution was reenabled again and the user here isn't cvsup'ing the docs, hence the error. I don't have time to improve *and* document the release building tools right now, folks, so if you're going to use this stuff then you have to watch the commit messages and read that file carefully from time to time so that you can keep up. Jordan > After my make world, new kernel then make release I got this on > both current and releng_2_2. I did the same on 24/jan/98 and > it worked fine. > > cd /var/ftp/release/usr && rm -rf doc && cvs -d /home/ncvs co -P doc > cvs [checkout aborted]: there is no repository /home/ncvs/doc > *** Error code 1 > > Stop. > > Thanks > > ed > > P.D. cvsuping to try again. From owner-freebsd-current Mon Jan 26 11:54:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15133 for current-outgoing; Mon, 26 Jan 1998 11:54:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15108; Mon, 26 Jan 1998 11:54:10 -0800 (PST) (envelope-from dmm125@bellatlantic.net) Received: from myname.my.domain (client201-122-28.bellatlantic.net [151.201.122.28]) by iconmail.bellatlantic.net (IConNet Sendmail) with SMTP id OAA26616; Mon, 26 Jan 1998 14:52:18 -0500 (EST) Date: Mon, 26 Jan 1998 14:50:50 +0000 (GMT) From: Donn Miller X-Sender: dmm125@myname.my.domain To: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: logging in as root under X Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk I've noticed that I can't login as root when running X: xterm -e login root & and then I type the password but I get rejected. All other logins work ok though under X. Also, if I start X as root and then type `finger', I don't see root listed under the pseudo-terminals anywhere. For ex., if I have two xterms open, finger should report that root is on ttyp0 and ttyp1 but I don't see them. If I start a new xterm via xterm -e login dmm125 &, I can log in OK and `finger' reports me as being logged in on ttyp2. But none of this works for root. syslogd reports LOGIN root REFUSED (NOROOT) ON ttyp2. I can still get an xterm open as root by selecting "new window" from the default root menu (mwm). But finger doesn't show root as being logged in on that tty. I'm running FreeBSD 3.0-980123-SNAP. Help appreciated. Thanks Donn From owner-freebsd-current Mon Jan 26 12:32:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21729 for current-outgoing; Mon, 26 Jan 1998 12:32:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mexcom.net ([200.38.135.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21537 for ; Mon, 26 Jan 1998 12:30:47 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id OAA09823; Mon, 26 Jan 1998 14:29:21 -0600 (CST) Message-ID: <34CCF386.2482594D@ver1.telmex.net.mx> Date: Mon, 26 Jan 1998 14:35:19 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: FreeBSD-current@FreeBSD.ORG Subject: Re: make release from 25/jan/98. References: <20303.885843175@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk If their are any more poor ignorant folks out there like me that don't know their place, this message IMHO can be translated to: In your cvs-supfile add a line something like this: doc-all It worked for me and I thank Jordan for the point in the right direction. Although I didn't find the syntax any where. I just tried a few possibilities and used the one that didn't give an error. High tech and very expert :-) Just joking although it is true. Have a great day, ed Better not talk too much I still haven't finished my "make release" :-) Jordan K. Hubbard wrote: > > I've said this before and I'll say it again: > > 1. The make release target is for experts only. > > 2. If you feel yourself to be an expert then you MUST then at least > take care to read and *thoroughly understand* > /usr/src/release/Makefile. > > In this case, as the file plainly shows, the doc distribution was > reenabled again and the user here isn't cvsup'ing the docs, hence the > error. I don't have time to improve *and* document the release > building tools right now, folks, so if you're going to use this stuff > then you have to watch the commit messages and read that file > carefully from time to time so that you can keep up. > > Jordan > > > After my make world, new kernel then make release I got this on > > both current and releng_2_2. I did the same on 24/jan/98 and > > it worked fine. > > > > cd /var/ftp/release/usr && rm -rf doc && cvs -d /home/ncvs co -P doc > > cvs [checkout aborted]: there is no repository /home/ncvs/doc > > *** Error code 1 > > > > Stop. > > > > Thanks > > > > ed > > > > P.D. cvsuping to try again. From owner-freebsd-current Mon Jan 26 12:37:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22762 for current-outgoing; Mon, 26 Jan 1998 12:37:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA22746 for ; Mon, 26 Jan 1998 12:37:15 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xwvH9-000043-00; Mon, 26 Jan 1998 13:36:59 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA13825; Mon, 26 Jan 1998 13:37:36 -0700 (MST) Message-Id: <199801262037.NAA13825@harmony.village.org> To: Amancio Hasty Subject: Re: Last stable -current? Cc: gmarco@giovannelli.it, Bruce Albrecht , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 25 Jan 1998 00:42:12 PST." <199801250842.AAA20980@rah.star-gate.com> References: <199801250842.AAA20980@rah.star-gate.com> Date: Mon, 26 Jan 1998 13:37:36 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk In message <199801250842.AAA20980@rah.star-gate.com> Amancio Hasty writes: : I haven't seen any posting from Dyson so I assume that -current still has : vm problems. My Jan 24 -current build on my laptop seems able to cope with X, vi, emacs, networking and ical w/o any crashes so far. John checked in a bunch of stuff that he claimed would make -current more stable as well as being a good base for building things in the future. Sounded stable enough to me to give it a try :-) Warner From owner-freebsd-current Mon Jan 26 12:45:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24236 for current-outgoing; Mon, 26 Jan 1998 12:45:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hydrogen.nike.efn.org (d182-89.uoregon.edu [128.223.182.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24231 for ; Mon, 26 Jan 1998 12:45:28 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id MAA17359; Mon, 26 Jan 1998 12:22:59 -0800 (PST) Message-ID: <19980126122259.37604@hydrogen.nike.efn.org> Date: Mon, 26 Jan 1998 12:22:59 -0800 From: John-Mark Gurney To: Manuel Bouyer Cc: port-i386@netbsd.org, freebsd-current@FreeBSD.ORG Subject: Re: AMD k6 and > 32Mb RAM References: <199801261707.SAA07023@chassiron.ensta.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199801261707.SAA07023@chassiron.ensta.fr>; from Manuel Bouyer on Mon, Jan 26, 1998 at 06:07:49PM +0100 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Manuel Bouyer scribbled this message on Jan 26: > Does anybody know if a K6 can run with 64Mb (or more) of RAM ? I've heard that > there was a silicon bug in the earlier K6 that would make it not manage > properly the RAM, but I don't know if it has been fixed. yes, this has been fixed... there was a bug if you accessed x and then x +- 32megs... I've been running a k6/225 (actually k6/200 but w/ bus speed of 75mhz) for a while now... once I replaced some faulty edo ram, things ran perfectly fine... I run with 48megs on my machine... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Mon Jan 26 12:59:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27312 for current-outgoing; Mon, 26 Jan 1998 12:59:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA27304 for ; Mon, 26 Jan 1998 12:59:54 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xwvMx-00004I-00; Mon, 26 Jan 1998 13:42:59 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA13871; Mon, 26 Jan 1998 13:43:44 -0700 (MST) Message-Id: <199801262043.NAA13871@harmony.village.org> To: Eivind Eklund Subject: Re: -current seems to be okay Cc: Amancio Hasty , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 26 Jan 1998 02:18:33 +0100." <19980126021833.41846@follo.net> References: <19980126021833.41846@follo.net> <199801260013.QAA17034@rah.star-gate.com> Date: Mon, 26 Jan 1998 13:43:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk In message <19980126021833.41846@follo.net> Eivind Eklund writes: : BTW: Thanks to John Dyson for the amount of work he has been putting : down - John, remind me to buy you a beer if we meet :-) Just a followup. I've alos been building kernels all morning (in a tight make clean ; make loop) and it is working great. No crashes yet, and I'm running X. This is on my Libretto with 32M of memory and a userland from Jan 24 also. And you can me to that (long) list of people that would buy John a beer. Warner From owner-freebsd-current Mon Jan 26 13:14:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29431 for current-outgoing; Mon, 26 Jan 1998 13:14:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29408 for ; Mon, 26 Jan 1998 13:14:27 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id VAA19848; Mon, 26 Jan 1998 21:29:07 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id TAA04669; Mon, 26 Jan 1998 19:43:03 +0100 (CET) (envelope-from roberto) Message-ID: <19980126194303.27534@keltia.freenix.fr> Date: Mon, 26 Jan 1998 19:43:03 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Cc: Manuel Bouyer Subject: Re: AMD k6 and > 32Mb RAM Mail-Followup-To: freebsd-current@FreeBSD.ORG, Manuel Bouyer References: <199801261707.SAA07023@chassiron.ensta.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <199801261707.SAA07023@chassiron.ensta.fr>; from Manuel Bouyer on Mon, Jan 26, 1998 at 06:07:49PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4016 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Manuel Bouyer disait : > there was a silicon bug in the earlier K6 that would make it not manage > properly the RAM, but I don't know if it has been fixed. No, the bug was -- it is fixed since rev. 9731 -- that when: - you have more than 32 MB of RAM, - the CPU tries to execute an instruction with memory operands separated exactly by 32 MB, In that situation, the CPU -- don't forget that it has a RISC core that translate Intel instr. into RISC ones -- thinks it is trying to translate a self-modifying instr. and execute the instruction twice. The result is sig10 or sig11 about 1/3 of the time during "make world" or an egcs compile. If you have a K6 with a rev. # less than 9731, send a mail to "euro.tech@amd.com" (if you're in Europe) and they'll change it very quickly. I don't have the address in the US but it is on www.amd.com. I sent back my K6-166 (rev. # 9725) to them (in UK) on Jan. 17th and got a K6-200 (rev. # 9745) on Jan. 21st. It has done several "make world" and pgcc compiles without a problem running at 3x 75 MHz (3x 83 MHz didn't work unfortunately). Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #53: Sun Jan 25 18:55:28 CET 1998 roberto@keltia.freenix.fr:/src/src/sys/compile/KELTIA CPU: AMD-K6tm w/ multimedia extensions (225.51-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Usenet Canal Historique From owner-freebsd-current Mon Jan 26 14:14:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06795 for current-outgoing; Mon, 26 Jan 1998 14:14:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA06771 for ; Mon, 26 Jan 1998 14:14:05 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 29957 invoked by uid 1000); 26 Jan 1998 22:17:58 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 26 Jan 1998 14:17:58 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: Building EGCS. What am I missing? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk cc -DIN_GCC -O -DHAVE_CONFIG_H -I. -I. -I./config \ -DTARGET_MACHINE=\"i386-unknown-freebsd\" \ -c `echo ./collect2.c | sed 's,^\./,,'` cpp: Usage: /usr/libexec/cpp [switches] input output gmake[1]: *** [collect2.o] Error 1 gmake[1]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.0.1/gcc' gmake: *** [all-gcc] Error 2 *** Error code 2 Stop. Now, I remember missing some configuration file. the only way to have it was to take the plain GNU 2.7.2.1, compile and install that, then use that as the first pass compiler to compile 2.8 or egcs (same problem). Any reminders please? ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 From owner-freebsd-current Mon Jan 26 14:27:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09568 for current-outgoing; Mon, 26 Jan 1998 14:27:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09537 for ; Mon, 26 Jan 1998 14:27:33 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA01708; Mon, 26 Jan 1998 17:27:06 -0500 (EST) (envelope-from toor) Message-Id: <199801262227.RAA01708@dyson.iquest.net> Subject: Re: -current seems to be okay In-Reply-To: <199801262043.NAA13871@harmony.village.org> from Warner Losh at "Jan 26, 98 01:43:43 pm" To: imp@village.org (Warner Losh) Date: Mon, 26 Jan 1998 17:27:06 -0500 (EST) Cc: eivind@yes.no, hasty@rah.star-gate.com, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk Warner Losh said: > > And you can me to that (long) list of people that would buy John a > beer. > I get really really wierd consuming lots of beer. (Okay, I get even more wierd :-).) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Jan 26 14:39:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10892 for current-outgoing; Mon, 26 Jan 1998 14:39:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10875 for ; Mon, 26 Jan 1998 14:39:33 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA01741; Mon, 26 Jan 1998 17:37:44 -0500 (EST) (envelope-from toor) Message-Id: <199801262237.RAA01741@dyson.iquest.net> Subject: Re: symorder: Cannot allocate memory In-Reply-To: <199801261708.AA07176@gamecock.unx.sas.com> from David Quattlebaum at "Jan 26, 98 12:08:26 pm" To: sasdrq@unx.sas.com (David Quattlebaum) Date: Mon, 26 Jan 1998 17:37:44 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk David Quattlebaum said: > I am trying to build a debug kernel at 3.0-current and keep > getting: > > loading kernel > rearranging symbols > symorder: Cannot allocate memory > There were some problems on earlier versions of 3.0-current. Try something supped very recently. (vfs.ioopt can cause problems very similar to what you are talking about.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Jan 26 14:41:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11372 for current-outgoing; Mon, 26 Jan 1998 14:41:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA11367 for ; Mon, 26 Jan 1998 14:41:14 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 10863 invoked by uid 1000); 26 Jan 1998 22:38:22 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20303.885843175@time.cdrom.com> Date: Mon, 26 Jan 1998 14:38:22 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: make release from 25/jan/98. Cc: FreeBSD-current@FreeBSD.ORG, eculp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On 26-Jan-98 Jordan K. Hubbard wrote: > I've said this before and I'll say it again: > > 1. The make release target is for experts only. > > 2. If you feel yourself to be an expert then you MUST then at least > take care to read and *thoroughly understand* > /usr/src/release/Makefile. > > In this case, as the file plainly shows, the doc distribution was > reenabled again and the user here isn't cvsup'ing the docs, hence the > error. I don't have time to improve *and* document the release > building tools right now, folks, so if you're going to use this stuff > then you have to watch the commit messages and read that file > carefully from time to time so that you can keep up. > > Jordan Does it build for you? If not, then we should not waste our time trying to duplicate the breakage. Your reply implies it does (?) Thanx! Simon From owner-freebsd-current Mon Jan 26 14:41:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11455 for current-outgoing; Mon, 26 Jan 1998 14:41:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA11359 for ; Mon, 26 Jan 1998 14:41:08 -0800 (PST) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA02131; Mon, 26 Jan 98 23:44:18 +0100 Date: Mon, 26 Jan 98 23:44:18 +0100 Message-Id: <9801262244.AA02131@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: imp@village.org Cc: eivind@yes.no, hasty@rah.star-gate.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199801262043.NAA13871@harmony.village.org> (message from Warner Losh on Mon, 26 Jan 1998 13:43:43 -0700) Subject: Re: -current seems to be okay X-Mailer: Emacs Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk >>>>> Warner Losh writes: > In message <19980126021833.41846@follo.net> Eivind Eklund writes: > : BTW: Thanks to John Dyson for the amount of work he has been putting > : down - John, remind me to buy you a beer if we meet :-) > Just a followup. I've alos been building kernels all morning (in a > tight make clean ; make loop) and it is working great. No crashes > yet, and I'm running X. This is on my Libretto with 32M of memory and > a userland from Jan 24 also. This is not my experience :-) my machine just locked. I had to reset. X was running so I did'nt see any error message (and nothing in /var/log/messages) Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr From owner-freebsd-current Mon Jan 26 14:54:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14997 for current-outgoing; Mon, 26 Jan 1998 14:54:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA14980 for ; Mon, 26 Jan 1998 14:54:49 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 2613 invoked by uid 1000); 26 Jan 1998 22:58:34 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <9801262244.AA02131@cabri.obs-besancon.fr> Date: Mon, 26 Jan 1998 14:58:34 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Jean-Marc Zucconi Subject: Re: -current seems to be okay Cc: freebsd-current@FreeBSD.ORG, hasty@rah.star-gate.com, eivind@yes.no, imp@village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On 26-Jan-98 Jean-Marc Zucconi wrote: >>>>>> Warner Losh writes: > > > In message <19980126021833.41846@follo.net> Eivind Eklund writes: > > : BTW: Thanks to John Dyson for the amount of work he has been putting > > : down - John, remind me to buy you a beer if we meet :-) > > > Just a followup. I've alos been building kernels all morning (in a > > tight make clean ; make loop) and it is working great. No crashes > > yet, and I'm running X. This is on my Libretto with 32M of memory and > > a userland from Jan 24 also. > > This is not my experience :-) my machine just locked. I had to > reset. X was running so I did'nt see any error message (and nothing in > /var/log/messages) I'm somewhere in between. Got LA to 24 with various activities fomr several hours with no ill effect, but got the system to freeze while reading this very message (these things use telepathy?). Something to do with X or the (PS/2) mouse. Overall it looks very well, though. Simon From owner-freebsd-current Mon Jan 26 15:58:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24006 for current-outgoing; Mon, 26 Jan 1998 15:58:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23993 for ; Mon, 26 Jan 1998 15:58:44 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id AAA04617 for freebsd-current@FreeBSD.ORG; Tue, 27 Jan 1998 00:58:25 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id AAA14800; Tue, 27 Jan 1998 00:20:53 +0100 (CET) (envelope-from roberto) Message-ID: <19980127002052.38606@keltia.freenix.fr> Date: Tue, 27 Jan 1998 00:20:52 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Building EGCS. What am I missing? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: ; from Simon Shapiro on Mon, Jan 26, 1998 at 02:17:58PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4016 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk According to Simon Shapiro: > -c `echo ./collect2.c | sed 's,^\./,,'` > cpp: Usage: /usr/libexec/cpp [switches] input output > gmake[1]: *** [collect2.o] Error 1 > gmake[1]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.0.1/gcc' > gmake: *** [all-gcc] Error 2 > *** Error code 2 > > Stop. > > Now, I remember missing some configuration file. the only way to have it > was to take the plain GNU 2.7.2.1, compile and install that, then use that > as the first pass compiler to compile 2.8 or egcs (same problem). I don't understand how you can have all these problems with egcs :-) I've build pgcc-980122 in both native & ELF cross compiler just a few minutes ago. I don't use the port though and I compile the snapshots, not the released version. Here is what I did: cd pgcc-980122 mkdir objdir cd objdir ../configure --host=i386-unknown-freebsd3.0 --enable-haifa --prefix=/opt/egcs gmake bootstrap gmake install cd ../../pgcc-980122-elf set path=(/opt/egcs/bin /opt/elf/bin $path) mkdir objdir cd objdir ../configure --enable-haifa --prefix=/opt/elf --host=i386-unknown-freebsd --target=i386-unknown-freebsdelf gmake cross [ there, you have to build libgcc1.a manually ] cd gcc ; gmake CC=gcc CFLAGS="-O2 -pipe" LIBGCC1=libgcc1.a OLDCC="./xgcc -B./" libgcc.a gmake cross gmake install The first commands build pgcc in native mode inside /opt/egcs/bin, using /usr/bin/cc as first pass compiler. The other commands build pgcc in ELF mode using /opt/egcs/bin/gcc as compiler. 303 [0:16] roberto@keltia:pgcc-980122-elf/objdir> gcc -v Reading specs from /opt/egcs/lib/gcc-lib/i386-unknown-freebsd3.0/pgcc-2.91.05/specs gcc version pgcc-2.91.05 980122 (gcc-2.8.0 release) 304 [0:18] roberto@keltia:pgcc-980122-elf/objdir> elf-cc -v Reading specs from /opt/elf/lib/gcc-lib/i386-unknown-freebsdelf/pgcc-2.91.05/specs gcc version pgcc-2.91.05 980122 (gcc-2.8.0 release) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #53: Sun Jan 25 18:55:28 CET 1998 From owner-freebsd-current Mon Jan 26 16:33:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27872 for current-outgoing; Mon, 26 Jan 1998 16:33:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27864 for ; Mon, 26 Jan 1998 16:33:05 -0800 (PST) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id TAA11168; Mon, 26 Jan 1998 19:31:17 -0500 (EST) Message-ID: <19980126193116.20118@rtfm.net> Date: Mon, 26 Jan 1998 19:31:16 -0500 From: Nathan Dorfman To: current@FreeBSD.ORG Subject: select() in -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Is there any problem with select() in -current? After building a new kernel last Wednesday, a certain application has stopped working. This is a fairly reputably buggy application, however I've used it extensively without anything like this--Brian Malia has a 1/2/98 -current and says it's okay too. The nasty little critter here is XFrisk. A numerously patched XFrisk... XFrisk-0.99c0pl9+bpk2+pac3+argon4 but it doesn't matter. Anyway it will freeze and output many Warning: 22's about select() failing after the server tells it that it's its turn. It also takes 35% of the CPU, much like our friend the failing netscape (which takes more like 80% :>). Any ideas? I recompiled the binary with no success. Going to re-cvsup, maybe someone was committing while intoxicated, or yes > /usr/src'ing locally...gadzooks :-) -- ________________ _______________________________ / Nathan Dorfman V PGP: finger nathan@rtfm.net / / nathan@rtfm.net | http://www.rtfm.net / From owner-freebsd-current Mon Jan 26 17:14:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06700 for current-outgoing; Mon, 26 Jan 1998 17:14:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06687 for ; Mon, 26 Jan 1998 17:14:28 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id RAA25503; Mon, 26 Jan 1998 17:13:16 -0800 (PST) (envelope-from jdp) Message-Id: <199801270113.RAA25503@austin.polstra.com> To: eculp@ver1.telmex.net.mx Subject: Re: make release from 25/jan/98. In-Reply-To: <34CCF386.2482594D@ver1.telmex.net.mx> References: <20303.885843175@time.cdrom.com> <34CCF386.2482594D@ver1.telmex.net.mx> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Mon, 26 Jan 1998 17:13:16 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk In article <34CCF386.2482594D@ver1.telmex.net.mx>, Edwin Culp wrote: > In your cvs-supfile add a line something like this: > > doc-all > > It worked for me and I thank Jordan for the point in the > right direction. Although I didn't find the syntax any where. It's in cvsup(1). -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Mon Jan 26 17:57:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13172 for current-outgoing; Mon, 26 Jan 1998 17:57:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13139 for ; Mon, 26 Jan 1998 17:57:17 -0800 (PST) (envelope-from bartol@salk.edu) Received: from dale.salk.edu (dale [198.202.70.112]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id QAA13252 for ; Mon, 26 Jan 1998 16:31:49 -0800 (PST) Date: Mon, 26 Jan 1998 16:31:48 -0800 (PST) From: Tom Bartol Reply-To: Tom Bartol To: freebsd-current@FreeBSD.ORG Subject: Problems with NFS in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Hi all, With all the recent talk about -current possibly being stable enough to update to again I thought I'd give it a try. I've just made world and am -current as of ~10PM PST Jan 25 and, well, X seems to be running fine, and I can read my e-mail in pine via an NFS-mounted /var/mail, I'm sending this e-mail from the machine in question, and my home dir and all of /usr/local is NFS-mounted. However I just observed the following glitch -- I just ran a script which redirected it's standard out and standard error to a log file (i.e. blah >& logfile ) and did a tail -f on the log file where logfile was on an NFS-mounted filesystem. All looked fine so I quit from the tail process and then did the tail -f again a moment later but this time the file look corrupted at the end. I then did a cat on the file and it was indeed corrupted at the end of the file (full of ^@ characters inserted in the file during the time I was viewing the file with tail, but good data for the time when I was not viewing the file). I can replicate the problem reliably on NFS filesystems but the problem does not occur on local filesystems. I'd like to buy John a beer too, right along with the rest of you, but what I'd really like to do is buy John and every one of us a John Dyson clone! (I'm a scientist at the Salk Institute, I know what I'm talking about, we could really do this!) ;-) But until our Dyson clones mature (will they ever mature? Do I know John well enough to make such a statement?) and earn their Ph.D's in CS we'll all have to send positive thoughts to our one and only "real" John Dyson and the rest of the FreeBSD team. Is this the feedback on -current you were looking for, John? Tom From owner-freebsd-current Mon Jan 26 18:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14056 for current-outgoing; Mon, 26 Jan 1998 18:02:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14049 for ; Mon, 26 Jan 1998 18:02:48 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA25018; Mon, 26 Jan 1998 21:02:42 -0500 (EST) (envelope-from toor) Message-Id: <199801270202.VAA25018@dyson.iquest.net> Subject: Re: Problems with NFS in -current In-Reply-To: from Tom Bartol at "Jan 26, 98 04:31:48 pm" To: bartol@salk.edu Date: Mon, 26 Jan 1998 21:02:42 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk Tom Bartol said: > > Hi all, > > -- I just ran a script which redirected it's standard out and standard > error to a log file (i.e. blah >& logfile ) and did a tail -f on the log > file where logfile was on an NFS-mounted filesystem. All looked fine so I > quit from the tail process and then did the tail -f again a moment later > but this time the file look corrupted at the end. I then did a cat on the > file and it was indeed corrupted at the end of the file (full of ^@ > characters inserted in the file during the time I was viewing the file > with tail, but good data for the time when I was not viewing the file). I > can replicate the problem reliably on NFS filesystems but the problem does > not occur on local filesystems. > Thanks for the feedback. I'll see what else is wrong :-). Mmap and friends are still problematical on NFS, but they are definitely fixable. ... Wierd but funny stuff removed > > Is this the feedback on -current you were looking for, John? > yes, actually thanks for prompt feedback, while I still understand the code :-). -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Jan 26 19:06:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20996 for current-outgoing; Mon, 26 Jan 1998 19:06:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (root@haiti-104.ppp.hooked.net [206.169.228.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20986 for ; Mon, 26 Jan 1998 19:06:11 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id RAA00270; Mon, 26 Jan 1998 17:35:04 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 26 Jan 1998 17:35:04 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Ollivier Robert cc: freebsd-current@FreeBSD.ORG Subject: Re: Building EGCS. What am I missing? In-Reply-To: <19980127002052.38606@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On Tue, 27 Jan 1998, Ollivier Robert wrote: > I don't understand how you can have all these problems with egcs :-) It's amazing how doing something that looks like what someone emailed you to do isn't in actuality. ;-) > I've build pgcc-980122 in both native & ELF cross compiler just a few > minutes ago. I don't use the port though and I compile the snapshots, not > the released version. > > Here is what I did: > > cd pgcc-980122 > mkdir objdir > cd objdir > ../configure --host=i386-unknown-freebsd3.0 --enable-haifa --prefix=/opt/egcs > gmake bootstrap > gmake install I tried that, and it built just fine. However, I can't seem to get it to make shared libraries at all :/ I've mucked around with switching to ELF, however, the milding success I've had with that makes me wary of rebuilding the whole system (which I'd have to do if I wanted to do elf X programming). Any words of wisdom? Linux: The Microsoft Windows(tm) of the Unix(tm) world. - alex From owner-freebsd-current Mon Jan 26 19:45:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25226 for current-outgoing; Mon, 26 Jan 1998 19:45:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25221 for ; Mon, 26 Jan 1998 19:45:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA06765; Mon, 26 Jan 1998 19:45:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199801270345.TAA06765@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Tom Bartol cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with NFS in -current In-reply-to: Your message of "Mon, 26 Jan 1998 16:31:48 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jan 1998 19:45:11 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Me too, I want to buy Dyson a beer next time I see him . I tried to do some java and net surfing on Win95 -- lasted about 5 minutes and happily jump back to FreeBSD 8) >what I'd really like to do is buy John and every one of us a John Dyson >clone! (I'm a scientist at the Salk Institute, I know what I'm talking Perhaps you guys can help by way of modifying his DNA (telemeres) so Dyson(Tm) can last a bit longer 8) Thats a thought we may soon have to start trade marking ourselves 8) Cheers, Amancio From owner-freebsd-current Mon Jan 26 20:14:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27962 for current-outgoing; Mon, 26 Jan 1998 20:14:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27955 for ; Mon, 26 Jan 1998 20:14:13 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id UAA22542 for ; Mon, 26 Jan 1998 20:14:23 -0800 (PST) To: current@FreeBSD.ORG Subject: -current build failure in kernel Date: Mon, 26 Jan 1998 20:14:23 -0800 Message-ID: <22538.885874463@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk sh ../../conf/newvers.sh GENERIC -DFAILSAFE cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DFAILSAFE -DKERNEL -include opt_global.h -c vers.c loading kernel cd9660_vnops.o: Undefined symbol `__zget' referenced from text segment kern_fork.o: Undefined symbol `__zget' referenced from text segment kern_proc.o: Undefined symbol `_zinit' referenced from text segment sys_pipe.o: Undefined symbol `_zinit' referenced from text segment sys_pipe.o: Undefined symbol `__zget' referenced from text segment sys_pipe.o: Undefined symbol `__zget' referenced from text segment vfs_init.o: Undefined symbol `_zinit' referenced from text segment vfs_lookup.o: Undefined symbol `__zget' referenced from text segment From owner-freebsd-current Mon Jan 26 20:33:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00380 for current-outgoing; Mon, 26 Jan 1998 20:33:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA00370 for ; Mon, 26 Jan 1998 20:33:39 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 27950 invoked by uid 1000); 27 Jan 1998 04:35:48 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 26 Jan 1998 20:35:48 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: gnu/usr.bin/cvs/libdiff Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk This got me baffled. I just CVSuped a whole new tree and said src directory has a Makefile and nothing else, but the Makefile thinks there should be a lot more there. What have I done? Thanx Simon From owner-freebsd-current Mon Jan 26 20:35:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00788 for current-outgoing; Mon, 26 Jan 1998 20:35:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00780 for ; Mon, 26 Jan 1998 20:35:45 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id PAA27699 for ; Tue, 27 Jan 1998 15:05:29 +1030 (CST) Message-Id: <199801270435.PAA27699@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: Problems with include files Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jan 1998 15:05:29 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Hi, I was doing a build world, with sources as of the 20 Dec 1997, and I found that I had to install the include files before I did it, otherwise some things would break. (such as mount - couldn't find a symbol, which was a #define which hadn't been included). I assume this is Bad(tm), any ideas why, or is it just some old broken stuff that was fixed? I had the latest linux code though, but that compiled fine, so I didn't think it was a problem. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- From owner-freebsd-current Mon Jan 26 20:41:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01641 for current-outgoing; Mon, 26 Jan 1998 20:41:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01633 for ; Mon, 26 Jan 1998 20:41:33 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id UAA22701; Mon, 26 Jan 1998 20:40:57 -0800 (PST) To: shimon@simon-shapiro.org cc: freebsd-current@FreeBSD.ORG Subject: Re: gnu/usr.bin/cvs/libdiff In-reply-to: Your message of "Mon, 26 Jan 1998 20:35:48 PST." Date: Mon, 26 Jan 1998 20:40:57 -0800 Message-ID: <22697.885876057@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > This got me baffled. I just CVSuped a whole new tree and said src > directory has a Makefile and nothing else, but the Makefile thinks there > should be a lot more there. What have I done? "man make" Seriously. You simply need to bone up on your Makefile syntax a little - this is elementary usage of .PATH in action, and something already in use in a fair number of other locations in the tree. Jordan From owner-freebsd-current Mon Jan 26 21:02:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03687 for current-outgoing; Mon, 26 Jan 1998 21:02:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA03657 for ; Mon, 26 Jan 1998 21:01:55 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 28344 invoked by uid 1000); 27 Jan 1998 05:04:03 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980127002052.38606@keltia.freenix.fr> Date: Mon, 26 Jan 1998 21:04:03 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Ollivier Robert Subject: Re: Building EGCS. What am I missing? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On 26-Jan-98 Ollivier Robert wrote: > According to Simon Shapiro: >> -c `echo ./collect2.c | sed 's,^\./,,'` >> cpp: Usage: /usr/libexec/cpp [switches] input output >> gmake[1]: *** [collect2.o] Error 1 >> gmake[1]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.0.1/gcc' >> gmake: *** [all-gcc] Error 2 >> *** Error code 2 >> >> Stop. >> >> Now, I remember missing some configuration file. the only way to have >> it >> was to take the plain GNU 2.7.2.1, compile and install that, then use >> that >> as the first pass compiler to compile 2.8 or egcs (same problem). > > I don't understand how you can have all these problems with egcs :-) You see, you are smart and I am not. Besides, computers HATE me :-) Also, I did: cd /usr/ports/lang/egcs;make Which is not exactly what you have done. As soon as this small egcs snapshot gets here, I will follow your procedure. > I've build pgcc-980122 in both native & ELF cross compiler just a few > minutes ago. I don't use the port though and I compile the snapshots, not > the released version. > > Here is what I did: > > cd pgcc-980122 > mkdir objdir > cd objdir > ../configure --host=i386-unknown-freebsd3.0 --enable-haifa > --prefix=/opt/egcs > gmake bootstrap > gmake install > > cd ../../pgcc-980122-elf > set path=(/opt/egcs/bin /opt/elf/bin $path) > mkdir objdir > cd objdir > ../configure --enable-haifa --prefix=/opt/elf --host=i386-unknown-freebsd > --target=i386-unknown-freebsdelf > gmake cross > [ there, you have to build libgcc1.a manually ] > cd gcc ; gmake CC=gcc CFLAGS="-O2 -pipe" LIBGCC1=libgcc1.a OLDCC="./xgcc > -B./" libgcc.a > gmake cross > gmake install > > The first commands build pgcc in native mode inside /opt/egcs/bin, using > /usr/bin/cc as first pass compiler. The other commands build pgcc in ELF > mode using /opt/egcs/bin/gcc as compiler. > > 303 [0:16] roberto@keltia:pgcc-980122-elf/objdir> gcc -v > Reading specs from > /opt/egcs/lib/gcc-lib/i386-unknown-freebsd3.0/pgcc-2.91.05/specs > gcc version pgcc-2.91.05 980122 (gcc-2.8.0 release) > 304 [0:18] roberto@keltia:pgcc-980122-elf/objdir> elf-cc -v > Reading specs from > /opt/elf/lib/gcc-lib/i386-unknown-freebsdelf/pgcc-2.91.05/specs > gcc version pgcc-2.91.05 980122 (gcc-2.8.0 release) > > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- > roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #53: Sun Jan 25 18:55:28 CET 1998 ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 From owner-freebsd-current Mon Jan 26 21:10:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05155 for current-outgoing; Mon, 26 Jan 1998 21:10:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA05015 for ; Mon, 26 Jan 1998 21:10:03 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 28408 invoked by uid 1000); 27 Jan 1998 05:12:10 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <22697.885876057@time.cdrom.com> Date: Mon, 26 Jan 1998 21:12:10 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: gnu/usr.bin/cvs/libdiff Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On 27-Jan-98 Jordan K. Hubbard wrote: >> This got me baffled. I just CVSuped a whole new tree and said src >> directory has a Makefile and nothing else, but the Makefile thinks there >> should be a lot more there. What have I done? > > "man make" > > Seriously. You simply need to bone up on your Makefile syntax a > little - this is elementary usage of .PATH in action, and something > already in use in a fair number of other locations in the tree. > > Jordan While I know most of my shortcomings (thanx for the rminder :-), I still did nothing short of cvs update (or checkout - matters not), followed be make buildworld and poof - the compile failed. I read the man pages for make several times but do not see anywhere mentioned that I am supposed to know anything. It implies that what compiled yesterday should compile today. In othert words, here is the tail output of make buildworld of this afternoon: echo libcvs.so..: `LIBRARY_PATH=/usr/obj/usr/src/3.0/src/tmp/usr/lib:/usr/obj/usr/src/3.0/src/ tmp/usr/lib cc -nostdinc -shared -Wl,-f ` >> .depend ===> gnu/usr.bin/cvs/libdiff make: don't know how to make diff.c. Stop *** Error code 2 Now, about that kernel build that faild for you this nice evening. As I do not have the same failure... Oh, just kidding, never mind :-) Actually, I do not see the failure you see. Shrug... ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 From owner-freebsd-current Mon Jan 26 21:18:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06680 for current-outgoing; Mon, 26 Jan 1998 21:18:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06644 for ; Mon, 26 Jan 1998 21:17:54 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id AAA17376; Tue, 27 Jan 1998 00:17:46 -0500 (EST) (envelope-from toor) Message-Id: <199801270517.AAA17376@dyson.iquest.net> Subject: Re: -current build failure in kernel In-Reply-To: <22538.885874463@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 26, 98 08:14:23 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 27 Jan 1998 00:17:46 -0500 (EST) Cc: current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk Jordan K. Hubbard said: > sh ../../conf/newvers.sh GENERIC -DFAILSAFE > cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DFAILSAFE -DKERNEL -include opt_global.h -c vers.c > loading kernel > cd9660_vnops.o: Undefined symbol `__zget' referenced from text segment > kern_fork.o: Undefined symbol `__zget' referenced from text segment > kern_proc.o: Undefined symbol `_zinit' referenced from text segment > sys_pipe.o: Undefined symbol `_zinit' referenced from text segment > sys_pipe.o: Undefined symbol `__zget' referenced from text segment > sys_pipe.o: Undefined symbol `__zget' referenced from text segment > vfs_init.o: Undefined symbol `_zinit' referenced from text segment > vfs_lookup.o: Undefined symbol `__zget' referenced from text segment > I fixed it a few hours ago. Don't know how it happened. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Jan 26 21:26:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07948 for current-outgoing; Mon, 26 Jan 1998 21:26:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07932 for ; Mon, 26 Jan 1998 21:26:25 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id PAA20365 for ; Tue, 27 Jan 1998 15:55:58 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA09661; Tue, 27 Jan 1998 15:55:58 +1030 (CST) (envelope-from grog) Message-ID: <19980127155557.45414@lemis.com> Date: Tue, 27 Jan 1998 15:55:57 +1030 From: Greg Lehey To: FreeBSD current users Subject: Another observation on -current and NFS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk OK, I've build a new -current as well on my test machine. I haven't had long enough to decide if there are any differences from a kernel built a month ago, but I've seen one similarity: I build my kernels on an NFS-mounted file system and leave my /usr read-only (this speeds up reboots after panics :-). I find I *consistently* can't strip a debug kernel across the net. The connection hangs, the local keyboard hangs, and about the only thing that works is a ping from another system. I have dumps of this situation, and I'm sure I can create more. The relevant part of the stack trace looks like: #8 0xf01d98fd in Debugger (msg=0xf0225def "manual escape to debugger") at ../../i386/i386/db_interface.c:316 #9 0xf0226b42 in scgetc (flags=2) at ../../i386/isa/syscons.c:3715 #10 0xf0220fe3 in scintr (unit=0) at ../../i386/isa/syscons.c:891 #11 0xf01dbd0e in vec1 () #12 0xf0134384 in vfs_vmio_release (bp=0xf24e556c) at ../../kern/vfs_bio.c:756 #13 0xf0134080 in brelse (bp=0xf24e556c) at ../../kern/vfs_bio.c:647 #14 0xf0166316 in nfs_bioread (vp=0xf0508900, uio=0xf3a41e34, ioflag=8, cred=0xf0547b80, getpages=1) at ../../nfs/nfs_bio.c:346 #15 0xf0165b64 in nfs_getpages (ap=0xf3a41e70) at ../../nfs/nfs_bio.c:116 #16 0xf01d0468 in vnode_pager_getpages (object=0xf3cced80, m=0xf3a41f38, count=1, reqpage=0) at vnode_if.h:1011 #17 0xf01cf0b3 in vm_pager_get_pages (object=0xf3cced80, m=0xf3a41f38, count=1, reqpage=0) at ../../vm/vm_pager.c:184 #18 0xf01c4750 in vm_fault (map=0xf0520200, vaddr=538910720, fault_type=3 '\003', fault_flags=8) at ../../vm/vm_fault.c:419 #19 0xf01e6f9e in trap_pfault (frame=0xf3a41fbc, usermode=1) at ../../i386/i386/trap.c:715 #20 0xf01e6ab3 in trap (frame={tf_es = 39, tf_ds = 39, tf_edi = 541048152, tf_esi = 11, tf_ebp = -272642080, tf_isp = -207347740, tf_ebx = 538910712, tf_edx = -266048520, tf_ecx = 0, tf_eax = -546667883, tf_trapno = 12, tf_err = 6, tf_eip = 8138, tf_cs = 31, tf_eflags = 66054, tf_esp = -272642224, tf_ss = 39}) at ../../i386/i386/trap.c:286 The command in question is the strip. If anybody wants more information, or access to the machine to look at it more carefully, please contact me. As I said before, this does not appear to have anything to do with changes made in the last 6 weeks. Greg From owner-freebsd-current Mon Jan 26 21:41:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11601 for current-outgoing; Mon, 26 Jan 1998 21:41:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11596; Mon, 26 Jan 1998 21:41:17 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id WAA06946; Mon, 26 Jan 1998 22:41:16 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd006916; Mon Jan 26 22:41:12 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id WAA00264; Mon, 26 Jan 1998 22:41:08 -0700 (MST) From: Terry Lambert Message-Id: <199801270541.WAA00264@usr01.primenet.com> Subject: Re: stable current? To: dyson@FreeBSD.ORG Date: Tue, 27 Jan 1998 05:41:08 +0000 (GMT) Cc: tlambert@primenet.com, scottm@cs.ucla.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199801260248.VAA00479@dyson.iquest.net> from "John S. Dyson" at Jan 25, 98 09:48:29 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > > Well, you are right, and the code supports it. > > Following up my own comments: I'll follow up the other comments tomorrow, when I have time to grovel the code at the same time I am typing. This will, in brief, point to the specific issue I'm referencing inre: stacking. > The pager code has supported whatever the filesystems do. This becomes > more of an issue with the layered filesystems, and the major impediment > that we have had is that the VM object could not be shared across vnodes, > and now it can. (Theoretically, we could layer UFS onto other filesystems, > but I am not worried about that right now.) The existance of aliases (ie: the act of sharing the object across vnodes) is fraught with peril. You may, in fact, have corrected this in the most recent code; I haven't updated my experimental system for some time. The aliasing of objects is precisely what was causing the "nullfs is not very null" series of changes to be a *bad* idea. The problem here is that if an FS does not support a VOP_{GET|PUT}PAGES, you can't tell whether it's because the FS truly does not understand it, or if you should use the bypass. Until all physical media FS's natively support it (I'm willing to hack on this if you are willing to commit the code), then you can't know that a NULL descriptor value in, say, nullfs or unionfs, means that the FS itself can't handle it, and you need to back off to the algorithm with promiscuous knowledge of where the pages are hung off the vnode. This algorithm assumes the top level vnode; for any stack, this is guaranteed to be an alias. Aliases are bad because they are hard to get right. Again, you might have gotten them right; I don't know. Really, you want to be able to ask "does the vnode backing this object support these interfaces?". You can't really ask that right now. Once you can ask that, maybe I screwed up in recommeneding the use of VOP_{GET|PUT}PAGES; if you can ask for the backing object, you can then run the old vnode_pager on the backing object instead of on the top level vnode. You can also access your lock list through the backing vnode's lock list (if the advisory locks were hung there), so maybe this is a better approach. I don't know yet. But aliases are a problem because of downward synchronization; even if you've taken care of it, it's a problem becauses of unnecessary code bloat, such as was contemplated in nullfs and unionfs. > Sure there are some layering issues as you have suggested, but I have > also known about them. There has been alot more wrong than even you > have ever talked about (at least to me.) Well, come back to town and let me buy you a pizza and talk your ear off... ;-). I never said that I knew all of the answers; only some of the questions, and what I thought were some (a smaller number) of the answers. > If this was an easy thing to fix, I would have a long time ago. There > are few, if any revelations in what you have said, but damn it, it doesn't > hurt to work in parallel, until I hear complaints that don't solve them, > or someone who discounts the complexity of problems. > > Almost none of the problems that we have had are due to the conventional > filesystem implementations. I can write a native getpages or putpages in > a few hours. It is the layering, and the vnode pager is pretty much not > an issue, and hasn't been for the last 2yrs. If the vnode pager implements > a default getpages or putpages interface, who cares? The layered filesystems > will supply their own. The intermediate layers will *not* necessarily supply their own. This is the purpose of the bypass. But to do a bypass, you have to be able to be sure that there's something at the end of the detour before you go down the road, and find nothing but a "sever tire damage will result!" sign. 8-). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jan 26 21:49:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13005 for current-outgoing; Mon, 26 Jan 1998 21:49:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12999 for ; Mon, 26 Jan 1998 21:49:23 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id WAA07460; Mon, 26 Jan 1998 22:49:22 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd007438; Mon Jan 26 22:49:17 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id WAA00788; Mon, 26 Jan 1998 22:49:14 -0700 (MST) From: Terry Lambert Message-Id: <199801270549.WAA00788@usr01.primenet.com> Subject: Re: Building EGCS. What am I missing? To: garbanzo@hooked.net (Alex) Date: Tue, 27 Jan 1998 05:49:14 +0000 (GMT) Cc: roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG In-Reply-To: from "Alex" at Jan 26, 98 05:35:04 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > I tried that, and it built just fine. However, I can't seem to get it to > make shared libraries at all :/ I've mucked around with switching to ELF, > however, the milding success I've had with that makes me wary of > rebuilding the whole system (which I'd have to do if I wanted to do elf X > programming). Any words of wisdom? Make sure you use the new binutils. Also, you must use a gas that understands weak symbols. The libraries are implemented by statically linking a PLT out of the shared library image, and overriding the symbols via relocation on a dlopen(), so that a call through the PLT gets the function from the shared library of choice. The most recent one wins. This is somewhat of the substance of the discussion about dladdr(), at least with regards to ELf, wherein the test program, when given a libc function address, identified the stub in the PLT of the main image (argv[0]) instead of the symbol in the shared library, and the path to the shared library as it was loaded by ld.so. Admittedly, the subject of the discussion didn't match the subject line for that one; it was an easy miss. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jan 26 21:51:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13755 for current-outgoing; Mon, 26 Jan 1998 21:51:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13750 for ; Mon, 26 Jan 1998 21:51:55 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA18279; Mon, 26 Jan 1998 22:51:50 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA03992; Mon, 26 Jan 1998 22:51:43 -0700 Date: Mon, 26 Jan 1998 22:51:43 -0700 Message-Id: <199801270551.WAA03992@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: shimon@simon-shapiro.org Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: gnu/usr.bin/cvs/libdiff In-Reply-To: References: <22697.885876057@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk > >> This got me baffled. I just CVSuped a whole new tree and said src > >> directory has a Makefile and nothing else, but the Makefile thinks there > >> should be a lot more there. What have I done? > > > > "man make" ... > While I know most of my shortcomings (thanx for the rminder :-), I still did > nothing short of cvs update (or checkout - matters not), followed be make > buildworld and poof - the compile failed. Then you didn't update everything you needed. Did you update /usr/src/contrib, which is where the CVS stuff is gotten from? If not, then you didn't update everything, and if you would have looked at the Makefile you would have known that it was looking in /usr/src/contrib/cvs for the files in question. Nate From owner-freebsd-current Mon Jan 26 21:58:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14811 for current-outgoing; Mon, 26 Jan 1998 21:58:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA14802; Mon, 26 Jan 1998 21:58:30 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA07933; Tue, 27 Jan 1998 00:59:39 -0500 From: Bill Paul Message-Id: <199801270559.AAA07933@skynet.ctr.columbia.edu> Subject: Re: Another observation on -current and NFS To: grog@lemis.com (Greg Lehey) Date: Tue, 27 Jan 1998 00:59:37 -0500 (EST) Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG In-Reply-To: <19980127155557.45414@lemis.com> from "Greg Lehey" at Jan 27, 98 03:55:57 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Of all the gin joints in all the towns in all the world, Greg Lehey had to walk into mine and say: > OK, I've build a new -current as well on my test machine. I haven't > had long enough to decide if there are any differences from a kernel > built a month ago, but I've seen one similarity: > > I build my kernels on an NFS-mounted file system and leave my /usr > read-only (this speeds up reboots after panics :-). I find I > *consistently* can't strip a debug kernel across the net. The > connection hangs, the local keyboard hangs, and about the only thing > that works is a ping from another system. This is an indication that some kernel routine is caught in an infinite loop of some kind. In fact, this sounds suspiciously like the problem I had with mmap() and NFS. > I have dumps of this situation, and I'm sure I can create more. The > relevant part of the stack trace looks like: [...] > #12 0xf0134384 in vfs_vmio_release (bp=0xf24e556c) at ../../kern/vfs_bio.c:756 > #13 0xf0134080 in brelse (bp=0xf24e556c) at ../../kern/vfs_bio.c:647 > #14 0xf0166316 in nfs_bioread (vp=0xf0508900, uio=0xf3a41e34, ioflag=8, cred=0xf0547b80, getpages=1) > at ../../nfs/nfs_bio.c:346 > #15 0xf0165b64 in nfs_getpages (ap=0xf3a41e70) at ../../nfs/nfs_bio.c:116 > #16 0xf01d0468 in vnode_pager_getpages (object=0xf3cced80, m=0xf3a41f38, count=1, reqpage=0) at vnode_if.h:1011 > #17 0xf01cf0b3 in vm_pager_get_pages (object=0xf3cced80, m=0xf3a41f38, count=1, reqpage=0) at ../../vm/vm_pager.c:184 > #18 0xf01c4750 in vm_fault (map=0xf0520200, vaddr=538910720, fault_type=3 '\003', fault_flags=8) > at ../../vm/vm_fault.c:419 [...] Oh boy, does this look familiar. This is almost exactly what I saw with the mmap() problem. The problem is that nfs_bioread() is trying to evict a buffer from the buffer cache that it doesn't like for some reason, but in fact the buffer is not being flushed. In my case, the buffer in question was supposed to cover an 8K region, but only the first 4K was actually mapped. When my test program tried to touch the second 4K, it triggered a page fault, causing the system to try to load the new 4K page into memory. But when nfs_bioread() is called, it finds the cached buffer which says it covers the desired region but really only covers the first 4K. So nfs_bioread() calls brelse() thinking this will evict the buffer from the cache so that the next time through the loop it will perform an actual read from the server to fetch the desired block. In fact, brelse() doesn't actually free the buffer, so nfs_bioread() comes up with the same partially valid buffer (via nfs_getcacheblk()) all over again, and it tries to evict it again, then it gets it again, and it tries to evict it again, then it gets it again, and it tries to evict it again, then it gets it again, and it tries to evict it again, and so on, and so on, and so on... nfs_bioread() seems to think that setting the B_NOCACHE flag on the buffer is enough to make brelse() throw the buffer out of the cache, but this doesn't seem to be the case anymore. Since the loop carries through quite a few different functions, you're likely to get several stack traces that look quite different, except for nfs_bioread(). I know: I banged my head against this problem for a while myself. John Dyson made a couple of commits this weekend which I _thought_ would fix this thing; I gave him a sample program that triggers the bug to help him track it down. Assuming that he got my sample program to work, I'm guessing there's more than one way to trigger the condition. > The command in question is the strip. It appears that strip(1) uses mmap(), so it looks like the same bug. Either it isn't really fixed, or there's more than one way to trip it. I would have loved to have fixed it myself, but I don't understand enough about the VM system to do it: while I can understand the nature of the bug, I don't actually know the right way to flush a buffer from the cache so I have no idea how to correct it. I tried looking at the UFS code to see if I could spot any clues, but nothing jumped out at me. > If anybody wants more > information, or access to the machine to look at it more carefully, > please contact me. As I said before, this does not appear to have > anything to do with changes made in the last 6 weeks. Hmmm... well, the bug I encountered has been there for a couple months at least. If you've only started to encounter it now, then maybe John's attempted fix made it worse somehow. *sigh* -Bill PS: Based on some other traffic I've seen come through -current recently, I'd bet a quarter that the cd9660 filesystem has mmap() problems too. -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-current Mon Jan 26 22:01:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15444 for current-outgoing; Mon, 26 Jan 1998 22:01:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15431; Mon, 26 Jan 1998 22:01:33 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id QAA20394; Tue, 27 Jan 1998 16:31:21 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id QAA09797; Tue, 27 Jan 1998 16:31:20 +1030 (CST) (envelope-from grog) Message-ID: <19980127163120.30701@lemis.com> Date: Tue, 27 Jan 1998 16:31:20 +1030 From: Greg Lehey To: Bill Paul Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: Another observation on -current and NFS References: <19980127155557.45414@lemis.com> <199801270559.AAA07933@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199801270559.AAA07933@skynet.ctr.columbia.edu>; from Bill Paul on Tue, Jan 27, 1998 at 12:59:37AM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On Tue, Jan 27, 1998 at 12:59:37AM -0500, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Greg Lehey had > to walk into mine and say: (etc) Thanks for your feedback. I'll read it more carefully when I have time :-) >> If anybody wants more information, or access to the machine to look >> at it more carefully, please contact me. As I said before, this >> does not appear to have anything to do with changes made in the >> last 6 weeks. > > Hmmm... well, the bug I encountered has been there for a couple months > at least. If you've only started to encounter it now, then maybe John's > attempted fix made it worse somehow. *sigh* Watch my lips: I *don't* think it has anything to do with John's changes. I was just hoping it would have gone away after them. Greg From owner-freebsd-current Mon Jan 26 22:27:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18841 for current-outgoing; Mon, 26 Jan 1998 22:27:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18830; Mon, 26 Jan 1998 22:27:04 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA27440; Tue, 27 Jan 1998 01:26:45 -0500 (EST) (envelope-from toor) Message-Id: <199801270626.BAA27440@dyson.iquest.net> Subject: Re: Another observation on -current and NFS In-Reply-To: <199801270559.AAA07933@skynet.ctr.columbia.edu> from Bill Paul at "Jan 27, 98 00:59:37 am" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Tue, 27 Jan 1998 01:26:45 -0500 (EST) Cc: grog@lemis.com, current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk Bill Paul said: > > John Dyson made a couple of commits this weekend which I _thought_ would > fix this thing; I gave him a sample program that triggers the bug to help > him track it down. Assuming that he got my sample program to work, I'm > guessing there's more than one way to trigger the condition. > The fixes explicitly fixed the problem with the test code. There indeed must be more problems. I will look at it while it is still in my brain-cache. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Jan 26 22:31:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19570 for current-outgoing; Mon, 26 Jan 1998 22:31:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19565; Mon, 26 Jan 1998 22:31:17 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA27457; Tue, 27 Jan 1998 01:30:59 -0500 (EST) (envelope-from toor) Message-Id: <199801270630.BAA27457@dyson.iquest.net> Subject: Re: Another observation on -current and NFS In-Reply-To: <199801270559.AAA07933@skynet.ctr.columbia.edu> from Bill Paul at "Jan 27, 98 00:59:37 am" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Tue, 27 Jan 1998 01:30:59 -0500 (EST) Cc: grog@lemis.com, current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.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-current@FreeBSD.ORG Precedence: bulk Bill Paul said: > > [...] > > #12 0xf0134384 in vfs_vmio_release (bp=0xf24e556c) at ../../kern/vfs_bio.c:756 > > #13 0xf0134080 in brelse (bp=0xf24e556c) at ../../kern/vfs_bio.c:647 > > #14 0xf0166316 in nfs_bioread (vp=0xf0508900, uio=0xf3a41e34, ioflag=8, cred=0xf0547b80, getpages=1) > > at ../../nfs/nfs_bio.c:346 > > #15 0xf0165b64 in nfs_getpages (ap=0xf3a41e70) at ../../nfs/nfs_bio.c:116 > This is really wierd... nfs_getpages no-longer calls nfs_bioread, and handles the I/O on it's own. We must not be talking about -current, are we? :-). If you are running -stable, and have lots of nerve, you might want to grab a copy of the new nfs_getpages from -current and port it :-). -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Jan 26 22:39:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20881 for current-outgoing; Mon, 26 Jan 1998 22:39:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20749; Mon, 26 Jan 1998 22:39:21 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id RAA20427; Tue, 27 Jan 1998 17:09:06 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id RAA09976; Tue, 27 Jan 1998 17:09:05 +1030 (CST) (envelope-from grog) Message-ID: <19980127170905.39298@lemis.com> Date: Tue, 27 Jan 1998 17:09:05 +1030 From: Greg Lehey To: dyson@FreeBSD.ORG Cc: Bill Paul , current@FreeBSD.ORG Subject: Re: Another observation on -current and NFS References: <199801270559.AAA07933@skynet.ctr.columbia.edu> <199801270630.BAA27457@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199801270630.BAA27457@dyson.iquest.net>; from John S. Dyson on Tue, Jan 27, 1998 at 01:30:59AM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On Tue, Jan 27, 1998 at 01:30:59AM -0500, John S. Dyson wrote: > Bill Paul said: >> >> [...] >>> #12 0xf0134384 in vfs_vmio_release (bp=0xf24e556c) at ../../kern/vfs_bio.c:756 >>> #13 0xf0134080 in brelse (bp=0xf24e556c) at ../../kern/vfs_bio.c:647 >>> #14 0xf0166316 in nfs_bioread (vp=0xf0508900, uio=0xf3a41e34, ioflag=8, cred=0xf0547b80, getpages=1) >>> at ../../nfs/nfs_bio.c:346 >>> #15 0xf0165b64 in nfs_getpages (ap=0xf3a41e70) at ../../nfs/nfs_bio.c:116 >> > > This is really wierd... nfs_getpages no-longer calls nfs_bioread, and > handles the I/O on it's own. We must not be talking about -current, are > we? :-). Grrr. I *hate* CVS. Yes, this was a version of the 12th December. It was *supposed* to be -current. I'll get the *(&(^*&^& to do what I mean, and I'll report. Greg From owner-freebsd-current Mon Jan 26 22:50:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22662 for current-outgoing; Mon, 26 Jan 1998 22:50:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA22622; Mon, 26 Jan 1998 22:50:07 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA03783; Tue, 27 Jan 1998 15:49:23 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id PAA14809; Tue, 27 Jan 1998 15:56:42 +0900 (JST) Message-Id: <199801270656.PAA14809@zodiac.mech.utsunomiya-u.ac.jp> To: Randy Terbush Cc: dyson@FreeBSD.ORG, brian@worldcontrol.com, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Cyclades/Hylafax/SMP select problems? In-Reply-To: Your message of "Mon, 26 Jan 1998 05:20:32 CST." <19980126052032B.randy@covalent.net> References: <199801261014.FAA00431@dyson.iquest.net> <19980126052032B.randy@covalent.net> Date: Tue, 27 Jan 1998 15:56:41 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk >"John S. Dyson" wrote: >> > > The Hylafax faxgetty and faxq processes spin out of control >> > > chewing up nearly 100% CPU. The same configuration ran without >> > > problems on a single P5 machine running 2.2-STABLE. >> > > >> > > As I begin to dig deeper into this, are there any know problems >> > > with this mix? >> > >> > Just thought you'd like to know you are not alone. faxq on >> > my SMP system does the same thing. >> > >> Sometimes the output of ktrace or truss can be useful. Also the >> contents of /proc//map sometimes helps with hints as to >> what is going on. > >Seems that a change to open the FIFO O_RDWR solves the problem. >Apparently, select() is returning when it should not be. Or, select() is returning a wrong value.. Would try the following patch and see if it helps? It applies to /sys/kern/sys_generic.c and make select() correctly returns -1 if an error occurred. Kazu Index: sys_generic.c =================================================================== RCS file: /src/CVS/src/sys/kern/sys_generic.c,v retrieving revision 1.33 diff -u -r1.33 sys_generic.c --- sys_generic.c 1997/11/23 10:30:50 1.33 +++ sys_generic.c 1998/01/27 06:38:34 @@ -542,6 +542,7 @@ int s, ncoll, error, timo; u_int nbufbytes, ncpbytes, nfdbits; + p->p_retval[0] = -1; if (uap->nd < 0) return (EINVAL); if (uap->nd > p->p_fd->fd_nfiles) @@ -673,8 +674,10 @@ while ((j = ffs(bits)) && (fd = i + --j) < nfd) { bits &= ~(1 << j); fp = fdp->fd_ofiles[fd]; - if (fp == NULL) + if (fp == NULL) { + p->p_retval[0] = -1; return (EBADF); + } if ((*fp->f_ops->fo_poll)(fp, flag[msk], fp->f_cred, p)) { obits[msk][(fd)/NFDBITS] |= From owner-freebsd-current Mon Jan 26 22:55:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24024 for current-outgoing; Mon, 26 Jan 1998 22:55:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from merkur.dbft.daimlerbenz.com (merkur.DaimlerBenz.com [141.113.7.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24011 for ; Mon, 26 Jan 1998 22:55:42 -0800 (PST) (envelope-from andreas.strobel@dbag.ulm.DaimlerBenz.COM) Received: (from uucp@localhost) by merkur.dbft.daimlerbenz.com (8.7.1/8.7.1) id HAA19375 for ; Tue, 27 Jan 1998 07:59:40 +0100 (MET) Received: from sophie-scholl.dbag.ulm.daimlerbenz.com(53.16.8.3) by merkur.dbft.daimlerbenz.com via smap (3.2) id xma019373; Tue, 27 Jan 98 07:59:39 +0100 Received: from dagobert.dbag.ulm.DaimlerBenz.COM by sophie-scholl.dbag.ulm.DaimlerBenz.COM (5.x/SMI-SVR4-23.9.1997-e) id AA04514; Tue, 27 Jan 1998 07:54:31 +0100 Received: from gustav by dagobert.dbag.ulm.DaimlerBenz.COM (4.1/SMI-4.1-18.9.1995-gm) id AA24527; Tue, 27 Jan 98 07:52:03 +0100 Date: Tue, 27 Jan 98 07:52:03 +0100 From: andreas.strobel@dbag.ulm.DaimlerBenz.COM (Andreas Strobel) Message-Id: <9801270652.AA24527@dagobert.dbag.ulm.DaimlerBenz.COM> To: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk subscribe freebsd-smp From owner-freebsd-current Mon Jan 26 23:05:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25330 for current-outgoing; Mon, 26 Jan 1998 23:05:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA25285 for ; Mon, 26 Jan 1998 23:05:28 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 11467 invoked by uid 1000); 27 Jan 1998 07:07:38 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199801270551.WAA03992@mt.sri.com> Date: Mon, 26 Jan 1998 23:07:38 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Nate Williams Subject: Re: gnu/usr.bin/cvs/libdiff Cc: freebsd-current@FreeBSD.ORG, "Jordan K.Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk On 27-Jan-98 Nate Williams wrote: >> >> This got me baffled. I just CVSuped a whole new tree and said src >> >> directory has a Makefile and nothing else, but the Makefile thinks >> >> there >> >> should be a lot more there. What have I done? >> > >> > "man make" > ... >> While I know most of my shortcomings (thanx for the rminder :-), I still >> did >> nothing short of cvs update (or checkout - matters not), followed be >> make >> buildworld and poof - the compile failed. > > Then you didn't update everything you needed. Did you update > /usr/src/contrib, which is where the CVS stuff is gotten from? If not, > then you didn't update everything, and if you would have looked at the > Makefile you would have known that it was looking in > /usr/src/contrib/cvs for the files in question. I tend to make a very routine and rigid procedure, which is not in a shell script only due to lazynesss and desire to visually inspect each step: < cvsup of ALL of the sources, ALL of the ports and ALL of the docs > rm -rf /usr/obj/usr/src/3.0 chflags -R noschg /usr/obj/usr/src/3.0 rm -rf /usr/obj/usr/src/3.0 < Much fasterthan chflags followedby rm > cd /usr/src/{2,2,3.0}/src cvs update -P -d >& ../update.out xemac ../update.out < Correct any deviations and repeat until no more complaints (if any) > make buildworld >& ../build.out xemacs ../build.out < Repeat until perfect > < NFS mount /usr/src and /usr/obj form a sacrifice machine, make installworld and reboot > make installworld If the source tree is healthy and I do not miss something, it always works. This time I forgot the rm -rf /usr/obj/... which in my stubborn, make-neophite mind is unnecessary step which renders make an awkward shell instead of an incremental system builder. Now, I know all the reasons why this should be necessary, but in my slow brain, they simply do not register well :-) My apologies for consuming this bandwidth with an obvious cocpit error. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 From owner-freebsd-current Mon Jan 26 23:08:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26231 for current-outgoing; Mon, 26 Jan 1998 23:08:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26223 for ; Mon, 26 Jan 1998 23:08:31 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id RAA20456 for ; Tue, 27 Jan 1998 17:38:27 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id RAA11907; Tue, 27 Jan 1998 17:38:26 +1030 (CST) (envelope-from grog) Message-ID: <19980127173826.47596@lemis.com> Date: Tue, 27 Jan 1998 17:38:26 +1030 From: Greg Lehey To: FreeBSD current users Subject: NFS and strip: false alarm Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Referring to my report of NFS hangs under -current: mea culpa. It seems that I somehow convinced cvs not to update my source tree any more. I've done so now with a *really* up-to-date version, and the problem no longer occurs. Now to live down the shame... Greg From owner-freebsd-current Mon Jan 26 23:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27417 for current-outgoing; Mon, 26 Jan 1998 23:13:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27407 for ; Mon, 26 Jan 1998 23:13:35 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id XAA23094; Mon, 26 Jan 1998 23:00:54 -0800 (PST) To: shimon@simon-shapiro.org cc: freebsd-current@FreeBSD.ORG Subject: Re: gnu/usr.bin/cvs/libdiff In-reply-to: Your message of "Mon, 26 Jan 1998 21:12:10 PST." Date: Mon, 26 Jan 1998 23:00:54 -0800 Message-ID: <23090.885884454@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk [First Simon says: ] > >> This got me baffled. I just CVSuped a whole new tree and said src > >> directory has a Makefile and nothing else, but the Makefile thinks there > >> should be a lot more there. What have I done? [and then] > While I know most of my shortcomings (thanx for the rminder :-), I still did > nothing short of cvs update (or checkout - matters not), followed be make > buildworld and poof - the compile failed. I read the man pages for make Aha! Nowhere in your first message did you even indicate that it *wasn't building* for you, you simply implied that you were confused at the apparent absence of source files where I knew none needed to exist, so I mailed my correction. If you are NOW saying that it doesn't build and furthermore suggests that /usr/src/contrib/cvs/diff is somehow missing from your system. Maybe you don't have src-contrib in your cvsup file? How the heck should I know? It works for me! :) > several times but do not see anywhere mentioned that I am supposed to know > anything. It implies that what compiled yesterday should compile today. Well, you should have known this one just from the cvs-all mail which showed a rather large import of new CVS bits from Peter! :) Seeing the files affected could then have led to a hunt for them on your own system following your last cvsup/ctm/whatever and, when you didn't see them, would have pointed you pretty squarely in the right direction I'd say. 8-) JOrdan From owner-freebsd-current Mon Jan 26 23:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28877 for current-outgoing; Mon, 26 Jan 1998 23:21:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28869; Mon, 26 Jan 1998 23:21:43 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id AAA05609; Tue, 27 Jan 1998 00:21:42 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id AAA02087; Tue, 27 Jan 1998 00:21:36 -0700 (MST) Message-Id: <199801270721.AAA02087@panzer.plutotech.com> Subject: Re: Another observation on -current and NFS In-Reply-To: <199801270626.BAA27440@dyson.iquest.net> from "John S. Dyson" at "Jan 27, 98 01:26:45 am" To: dyson@FreeBSD.ORG Date: Tue, 27 Jan 1998 00:21:36 -0700 (MST) Cc: wpaul@skynet.ctr.columbia.edu, grog@lemis.com, current@FreeBSD.ORG, dyson@FreeBSD.ORG From: Kenneth Merry X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk John S. Dyson wrote... > Bill Paul said: > > > > John Dyson made a couple of commits this weekend which I _thought_ would > > fix this thing; I gave him a sample program that triggers the bug to help > > him track it down. Assuming that he got my sample program to work, I'm > > guessing there's more than one way to trigger the condition. > > > The fixes explicitly fixed the problem with the test code. There indeed > must be more problems. I will look at it while it is still in my brain-cache. Well, FWIW, I'll share my experiences with -current's NFS today. I have noticed the 'strip' problem happening as well for the past couple of months at least. In my experience, the client machine (i.e. the one doing the strip) wouldn't hang, but the kernel it generated wouldn't boot. I tried stripping a kernel today over NFS (between a client and server that are both current as of today) and the kernel booted just fine. I have also been having link troubles when compiling/linking programs over NFS. (the linker wouldn't find functions that were indeed in the libraries..) Those problems are gone as of today. There is one interesting NFS problem I can report, though. Apparantly there is a problem with access(2) and files on NFS mounted filesystems. (one of my co-workers discovered it) Here is a program to test permissions: (I didn't write it, I just made a minor modification...) ======================================================================== #include #include void usage ( void ) { fprintf(stderr, "usage: testAccess \n"); fprintf(stderr, "Where the inclusive or of some of\n"); fprintf(stderr, "F_OK, R_OK, W_OK, or X_OK\n"); exit(1); } main ( int argc, char *argv[] ) { int indx; int mode = 0; char *tmpPtr; if (3 != argc) { usage(); } for (tmpPtr = argv[1]; 0 != *tmpPtr; tmpPtr++) { int digit; if (!isdigit(*tmpPtr)) { usage(); } digit = *tmpPtr - '0'; if (7 < digit) { usage(); } mode = (mode << 3) + digit; } printf("Access returns %d for file %s and mode %o\n", access(argv[2], mode), argv[2], mode); } ======================================================================== And here is what happens: On a local filesystem, the program behaves as expected: ==================================================== {roadwarrior:/usr/home/ken/src/yates:162:0} ls -la foo ---------- 1 ken wheel 0 Jan 26 18:35 foo {roadwarrior:/usr/home/ken/src/yates:163:0} ./testAccess 777 foo Access returns -1 for file foo and mode 777 ==================================================== The file foo has no permissions, so access(2) should return -1. When the same filesystem is NFS mounted, the program does not behave as expected: ==================================================== {bladerunner:/usr2/home/ken/src/yates:34:0} ls -la foo ---------- 1 ken wheel 0 Jan 26 18:35 foo {bladerunner:/usr2/home/ken/src/yates:35:0} ./testAccess 777 foo Access returns 0 for file foo and mode 777 ==================================================== In any case, this looks like a bug to me, but if it's just operator error, please let me know. As far as I can tell, though, the major (and in some cases show stopping) NFS bugs in -current have been fixed. Thanks John! Ken -- Kenneth Merry ken@plutotech.com From owner-freebsd-current Mon Jan 26 23:50:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04699 for current-outgoing; Mon, 26 Jan 1998 23:50:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04683 for ; Mon, 26 Jan 1998 23:50:05 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id IAA07472 for freebsd-current@FreeBSD.ORG; Tue, 27 Jan 1998 08:50:02 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id IAA17715; Tue, 27 Jan 1998 08:45:05 +0100 (CET) (envelope-from roberto) Message-ID: <19980127084505.42012@keltia.freenix.fr> Date: Tue, 27 Jan 1998 08:45:05 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Building EGCS. What am I missing? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19980127002052.38606@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: ; from Alex on Mon, Jan 26, 1998 at 05:35:04PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4016 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk According to Alex: > I tried that, and it built just fine. However, I can't seem to get it to > make shared libraries at all :/ I've mucked around with switching to ELF, You probably get the same error as I do: /opt/egcs/bin/gcc -fpic -DPIC -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm/../../sys -c /src/src/lib/libkvm/kvm_proc.c -o kvm_proc.so building shared kvm library (version 2.0) ld: No reference to __DYNAMIC collect2: ld returned 1 exit status *** Error code 1 Stop. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #53: Sun Jan 25 18:55:28 CET 1998 From owner-freebsd-current Tue Jan 27 01:21:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16326 for current-outgoing; Tue, 27 Jan 1998 01:21:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from p-voyageur.issy.cnet.fr (p-voyageur.issy.cnet.fr [139.100.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16319 for ; Tue, 27 Jan 1998 01:21:23 -0800 (PST) (envelope-from dominique.alglave@cnet.francetelecom.fr) Received: by p-voyageur.issy.cnet.fr with Internet Mail Service (5.0.1458.49) id ; Tue, 27 Jan 1998 10:23:51 +0100 Message-ID: <33C73673A9D6D0119A8800805FBE0C1C09175E@p-colombin.issy.cnet.fr> From: ALGLAVE Dominique CNET/DTL/ISS To: "'freebsd-current@FreeBSD.ORG'" Subject: UNSUBSCRIBE Date: Tue, 27 Jan 1998 10:23:50 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk UNSUBCRIBE From owner-freebsd-current Tue Jan 27 01:57:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20664 for current-outgoing; Tue, 27 Jan 1998 01:57:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20659 for ; Tue, 27 Jan 1998 01:57:42 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id CAA12333 for ; Tue, 27 Jan 1998 02:57:38 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd012320; Tue Jan 27 02:57:34 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id CAA04106 for freebsd-current@FreeBSD.ORG; Tue, 27 Jan 1998 02:57:33 -0700 (MST) From: Terry Lambert Message-Id: <199801270957.CAA04106@usr09.primenet.com> Subject: PATCH: Fixes for annoying VOP_LEASE bugs for NFS To: freebsd-current@FreeBSD.ORG Date: Tue, 27 Jan 1998 09:57:33 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Here are some of the obvious patches I am always on about. This should be a tiny enough chunk that even an application programmer can understand them. Someone please commit them. They should help with a few cases where NFSv3 is wierded out. The utility should be obvious. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. ========================================================================== Index: kern/kern_exec.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/kern/kern_exec.c,v retrieving revision 1.68 diff -c -r1.68 kern_exec.c *** 1.68 1997/11/06 19:29:08 --- kern_exec.c 1998/01/27 09:24:25 *************** *** 183,188 **** --- 183,189 ---- * header into it. */ imgp->image_header = malloc(PAGE_SIZE, M_TEMP, M_WAITOK); + VOP_LEASE(imgp->vp, p, p->p_ucred, LEASE_READ); error = vn_rdwr(UIO_READ, imgp->vp, (void *)imgp->image_header, PAGE_SIZE, 0, UIO_SYSSPACE, IO_NODELOCKED, p->p_ucred, &resid, p); /* Index: kern/kern_ktrace.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/kern/kern_ktrace.c,v retrieving revision 1.21 diff -c -r1.21 kern_ktrace.c *** 1.21 1997/11/06 19:29:10 --- kern_ktrace.c 1998/01/27 09:35:40 *************** *** 478,483 **** --- 478,484 ---- aiov[1].iov_len = kth->ktr_len; auio.uio_resid += kth->ktr_len; } + VOP_LEASE(vp, p, p->p_cred, LEASE_WRITE); vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); error = VOP_WRITE(vp, &auio, IO_UNIT|IO_APPEND, p->p_ucred); VOP_UNLOCK(vp, 0, p); Index: kern/link_aout.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/kern/link_aout.c,v retrieving revision 1.4 diff -c -r1.4 link_aout.c *** 1.4 1997/11/07 08:52:59 --- link_aout.c 1998/01/27 09:27:23 *************** *** 116,121 **** --- 116,122 ---- /* * Read the a.out header from the file. */ + VOP_LEASE(nd.ni_vp, p, p->p_ucred, LEASE_READ); error = vn_rdwr(UIO_READ, nd.ni_vp, (void*) &header, sizeof header, 0, UIO_SYSSPACE, IO_NODELOCKED, p->p_ucred, &resid, p); if (error) Index: kern/tty_tty.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/kern/tty_tty.c,v retrieving revision 1.19 diff -c -r1.19 tty_tty.c *** 1.19 1997/09/16 11:43:35 --- tty_tty.c 1998/01/27 09:06:19 *************** *** 128,133 **** --- 128,134 ---- if (ttyvp == NULL) return (EIO); + VOP_LEASE(ttyvp, p, NOCRED, LEASE_WRITE); vn_lock(ttyvp, LK_EXCLUSIVE | LK_RETRY, p); error = VOP_WRITE(ttyvp, uio, flag, NOCRED); VOP_UNLOCK(ttyvp, 0, p); Index: kern/vfs_vnops.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/kern/vfs_vnops.c,v retrieving revision 1.41 diff -c -r1.41 vfs_vnops.c *** 1.41 1997/11/07 08:53:11 --- vfs_vnops.c 1998/01/27 09:08:27 *************** *** 216,221 **** --- 216,224 ---- /* * Package up an I/O request on a vnode into a uio and do it. + * + * This function assumes the caller has done the appropriate + * VOP_LEASE() call prior to calling it. */ int vn_rdwr(rw, vp, base, len, offset, segflg, ioflg, cred, aresid, p) ========================================================================== From owner-freebsd-current Tue Jan 27 02:08:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22221 for current-outgoing; Tue, 27 Jan 1998 02:08:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22195 for ; Tue, 27 Jan 1998 02:08:52 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id DAA02848 for ; Tue, 27 Jan 1998 03:08:50 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd002838; Tue Jan 27 03:08:45 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id DAA04483 for current@freebsd.org; Tue, 27 Jan 1998 03:08:45 -0700 (MST) From: Terry Lambert Message-Id: <199801271008.DAA04483@usr09.primenet.com> Subject: PATCH: if_de.c #ifdef based version encoding To: current@FreeBSD.ORG Date: Tue, 27 Jan 1998 10:08:45 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk The value of the manifest constant __FreeBSD__ is derived from the compiler tools and not from the kernel being built. In other words, the value of __FreeBSD__ comes from the version of the OS the tools were built on, not from the OS that's running or the one that is being targeted. This means that if I build a v3 kernel using a v2 system's tools, the "#if __FreeBSD__ >= 3" and "#if defined(__FreeBSD__) && __FreeBSD__ >= 3" will not test true, even though that is, in fact, what I am building. Version information should not be encoded in #ifdef's; that is what branch tags are for. If I can check this code out, implicitly, I am building a 3+ system. The "#if" tests are bogus. This patch allows people to compile v3 kernels containing if_de.c on v2 systems. Please commit it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. ============================================================================= Index: pci/if_de.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/pci/if_de.c,v retrieving revision 1.74 diff -c -r1.74 if_de.c *** 1.74 1997/11/08 14:46:53 --- if_de.c 1998/01/27 10:02:02 *************** *** 3024,3035 **** tulip_addr_filter( tulip_softc_t * const sc) { ! #if defined(__FreeBSD__) && __FreeBSD__ >= 3 struct ifmultiaddr *ifma; u_char *addrp; - #else - struct ether_multistep step; - struct ether_multi *enm; #endif int multicnt; --- 3024,3032 ---- tulip_addr_filter( tulip_softc_t * const sc) { ! #if defined(__FreeBSD__) struct ifmultiaddr *ifma; u_char *addrp; #endif int multicnt; *************** *** 3041,3047 **** sc->tulip_if.if_flags &= ~IFF_ALLMULTI; #endif ! #if defined(__FreeBSD__) && __FreeBSD__ >= 3 multicnt = 0; for (ifma = sc->tulip_if.if_multiaddrs.lh_first; ifma != NULL; ifma = ifma->ifma_link.le_next) { --- 3038,3044 ---- sc->tulip_if.if_flags &= ~IFF_ALLMULTI; #endif ! #if defined(__FreeBSD__) multicnt = 0; for (ifma = sc->tulip_if.if_multiaddrs.lh_first; ifma != NULL; ifma = ifma->ifma_link.le_next) { *************** *** 3049,3056 **** if (ifma->ifma_addr->sa_family == AF_LINK) multicnt++; } - #else - multicnt = sc->tulip_multicnt; #endif sc->tulip_if.if_start = tulip_ifstart; /* so the setup packet gets queued */ --- 3046,3051 ---- *************** *** 3075,3081 **** */ bzero(sc->tulip_setupdata, sizeof(sc->tulip_setupdata)); ! #if defined(__FreeBSD__) && __FreeBSD__ >= 3 for (ifma = sc->tulip_if.if_multiaddrs.lh_first; ifma != NULL; ifma = ifma->ifma_link.le_next) { --- 3070,3076 ---- */ bzero(sc->tulip_setupdata, sizeof(sc->tulip_setupdata)); ! #if defined(__FreeBSD__) for (ifma = sc->tulip_if.if_multiaddrs.lh_first; ifma != NULL; ifma = ifma->ifma_link.le_next) { *************** *** 3085,3103 **** hash = tulip_mchash(LLADDR((struct sockaddr_dl *)ifma->ifma_addr)); sp[hash >> 4] |= 1 << (hash & 0xF); } - #else - ETHER_FIRST_MULTI(step, TULIP_ETHERCOM(sc), enm); - while (enm != NULL) { - if (bcmp(enm->enm_addrlo, enm->enm_addrhi, 6) == 0) { - hash = tulip_mchash(enm->enm_addrlo); - sp[hash >> 4] |= 1 << (hash & 0xF); - } else { - sc->tulip_flags |= TULIP_ALLMULTI; - sc->tulip_flags &= ~(TULIP_WANTHASHONLY|TULIP_WANTHASHPERFECT); - break; - } - ETHER_NEXT_MULTI(step, enm); - } #endif /* * No reason to use a hash if we are going to be --- 3080,3085 ---- *************** *** 3123,3129 **** /* * Else can get perfect filtering for 16 addresses. */ ! #if defined(__FreeBSD__) && __FreeBSD__ >= 3 for (ifma = sc->tulip_if.if_multiaddrs.lh_first; ifma != NULL; ifma = ifma->ifma_link.le_next) { if (ifma->ifma_addr->sa_family != AF_LINK) --- 3105,3111 ---- /* * Else can get perfect filtering for 16 addresses. */ ! #if defined(__FreeBSD__) for (ifma = sc->tulip_if.if_multiaddrs.lh_first; ifma != NULL; ifma = ifma->ifma_link.le_next) { if (ifma->ifma_addr->sa_family != AF_LINK) *************** *** 3134,3152 **** *sp++ = ((u_int16_t *) addrp)[2]; idx++; } - #else - ETHER_FIRST_MULTI(step, TULIP_ETHERCOM(sc), enm); - for (; enm != NULL; idx++) { - if (bcmp(enm->enm_addrlo, enm->enm_addrhi, 6) == 0) { - *sp++ = ((u_int16_t *) enm->enm_addrlo)[0]; - *sp++ = ((u_int16_t *) enm->enm_addrlo)[1]; - *sp++ = ((u_int16_t *) enm->enm_addrlo)[2]; - } else { - sc->tulip_flags |= TULIP_ALLMULTI; - break; - } - ETHER_NEXT_MULTI(step, enm); - } #endif /* * Add the broadcast address. --- 3116,3121 ---- *************** *** 4459,4479 **** /* * Update multicast listeners */ ! #if defined(__FreeBSD__) && __FreeBSD__ >= 3 tulip_addr_filter(sc); /* reset multicast filtering */ tulip_init(sc); error = 0; - #else - if (cmd == SIOCADDMULTI) - error = ether_addmulti(ifr, TULIP_ETHERCOM(sc)); - else - error = ether_delmulti(ifr, TULIP_ETHERCOM(sc)); - - if (error == ENETRESET) { - tulip_addr_filter(sc); /* reset multicast filtering */ - tulip_init(sc); - error = 0; - } #endif break; } --- 4428,4437 ---- /* * Update multicast listeners */ ! #if defined(__FreeBSD__) tulip_addr_filter(sc); /* reset multicast filtering */ tulip_init(sc); error = 0; #endif break; } *************** *** 5112,5124 **** tulip_softc_t *sc; #define PCI_CONF_WRITE(r, v) pci_conf_write(config_id, (r), (v)) #define PCI_CONF_READ(r) pci_conf_read(config_id, (r)) - #if __FreeBSD__ >= 3 #define PCI_GETBUSDEVINFO(sc) ((void)((sc)->tulip_pci_busno = (config_id->bus), /* XXX */ \ (sc)->tulip_pci_devno = (config_id->slot))) /* XXX */ - #else - #define PCI_GETBUSDEVINFO(sc) ((void)((sc)->tulip_pci_busno = ((config_id.cfg1 >> 16) & 0xFF), /* XXX */ \ - (sc)->tulip_pci_devno = ((config_id.cfg1 >> 11) & 0x1F))) /* XXX */ - #endif #endif #if defined(__bsdi__) tulip_softc_t * const sc = (tulip_softc_t *) self; --- 5070,5077 ---- ============================================================================= From owner-freebsd-current Tue Jan 27 02:58:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28229 for current-outgoing; Tue, 27 Jan 1998 02:58:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28224 for ; Tue, 27 Jan 1998 02:58:57 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id DAA25275; Tue, 27 Jan 1998 03:01:07 -0800 (PST) Message-Id: <199801271101.DAA25275@implode.root.com> To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: PATCH: if_de.c #ifdef based version encoding In-reply-to: Your message of "Tue, 27 Jan 1998 10:08:45 GMT." <199801271008.DAA04483@usr09.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 27 Jan 1998 03:01:07 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk >The value of the manifest constant __FreeBSD__ is derived from the >compiler tools and not from the kernel being built. > >In other words, the value of __FreeBSD__ comes from the version of the >OS the tools were built on, not from the OS that's running or the one >that is being targeted. > >This means that if I build a v3 kernel using a v2 system's tools, the >"#if __FreeBSD__ >= 3" and "#if defined(__FreeBSD__) && __FreeBSD__ >= 3" >will not test true, even though that is, in fact, what I am building. > > >Version information should not be encoded in #ifdef's; that is what >branch tags are for. If I can check this code out, implicitly, I am >building a 3+ system. The "#if" tests are bogus. > >This patch allows people to compile v3 kernels containing if_de.c on v2 >systems. > >Please commit it. In theory, the de driver is maintained by Matt Thomas and he supports multiple OS's and OS versions in the code. You'll notice that there are #ifdef's for NetBSD and BSD/OS in there as well. If we were going to do as you suggest, then it would only make sense if all of the OS #ifdef's were removed. This will only make it more difficult for Matt to support FreeBSD, so I think it's a bad idea. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Jan 27 04:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10774 for current-outgoing; Tue, 27 Jan 1998 04:49:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10769 for ; Tue, 27 Jan 1998 04:49:03 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id GAA00775; Tue, 27 Jan 1998 06:48:51 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199801271101.DAA25275@implode.root.com> References: Your message of "Tue, 27 Jan 1998 10:08:45 GMT." <199801271008.DAA04483@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 27 Jan 1998 06:44:25 -0600 To: dg@root.com From: Richard Wackerbarth Subject: Re: PATCH: if_de.c #ifdef based version encoding Cc: Terry Lambert , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk In response to Terry Lambert, At 5:01 AM -0600 1/27/98, David Greenman wrote: >>The value of the manifest constant __FreeBSD__ is derived from the >>compiler tools and not from the kernel being built. >> >>In other words, the value of __FreeBSD__ comes from the version of the >>OS the tools were built on, not from the OS that's running or the one >>that is being targeted. >> >>This means that if I build a v3 kernel using a v2 system's tools, the >>"#if __FreeBSD__ >= 3" and "#if defined(__FreeBSD__) && __FreeBSD__ >= 3" >>will not test true, even though that is, in fact, what I am building. >> >> >>Version information should not be encoded in #ifdef's; that is what >>branch tags are for. If I can check this code out, implicitly, I am >>building a 3+ system. The "#if" tests are bogus. [...] > In theory, the de driver is maintained by Matt Thomas and he supports >multiple OS's and OS versions in the code. You'll notice that there are >#ifdef's for NetBSD and BSD/OS in there as well. If we were going to do >as you suggest, then it would only make sense if all of the OS #ifdef's >were removed. This will only make it more difficult for Matt to support >FreeBSD, so I think it's a bad idea. In a sense, you are both right. The code SHOULD contain #if tests to allow the unification of multiple branches into a single vendor file. At the same time, Terry is correct that the test is being derived from a bogus source. The only definition that should be derived from the compiler is that which relates to the compiler itself. For example, "Is this a 'C' compiler or a 'C++' compiler?" might be such a distinction. The OS Target should be defined in the SOURCE tree of the system. This is what .../include/machine and .../include/sys should define. Now, unless you are using the default case of compiling for "this OS on this machine", those values are NOT in /usr/include/sys/ but rather some $TARGET/include/sys/. Richard Wackerbarth From owner-freebsd-current Tue Jan 27 05:29:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16043 for current-outgoing; Tue, 27 Jan 1998 05:29:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA16035 for ; Tue, 27 Jan 1998 05:28:57 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA05130; Tue, 27 Jan 1998 22:28:44 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA28956; Tue, 27 Jan 1998 22:36:21 +0900 (JST) Message-Id: <199801271336.WAA28956@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: HEADS UP: Keymap file reorganization Date: Tue, 27 Jan 1998 22:36:00 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk There will be a bit of reorganization in share/syscons/keymaps in -current. It will be done in two stages: Stage 1: Correct inconsistency among keymap files and fixe minor gliches - Define CTL-ALT-ESC as the `debug' key sequence in all keymaps. (FAQ mentions this key sequence.) Some keymaps already have it, the others don't. It is NOP if the kernel isn't compiled with the kernel debugger. - Define CTL-SPACE to generate NUL. Again only some keymaps have this. - Define CTL-ALT-SPACE as the `suspend' key sequence in all but Russiun keymaps. (Some keymaps had typo: numerical value 135 is written instead of the `suspend' keyword.) This sequecne will be NOP if the apm driver is not installed or disabled. - Fix Japanese keymaps. - Remove accent (dead) key definitions from spanish.iso.kbd, fr.iso.kbd and icelandic.iso.kbd. Create spanish.iso.acc.kbd, fr.iso.acc.kbd and icelandic.iso.acc.kbd with accent key definitions instead. - Update INDEX.kbdmap for kbdmap(1). - Update keymap menus in release/sysinstall. [At this point, I intend to merge dead key support (in syscons and kbdcontrol) and modified keymap files from the -current to the -stable branch.] Stage 2: ALL keymap files will be renamed so that they conform to more canonical naming convention The new name will look _.[.