From owner-freebsd-current Sun Apr 6 00:38:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA02014 for current-outgoing; Sun, 6 Apr 1997 00:38:35 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA01980 for ; Sun, 6 Apr 1997 00:38:27 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA00449; Sun, 6 Apr 1997 10:38:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id QAA09144; Sat, 5 Apr 1997 16:37:31 +0200 (MET DST) Message-ID: <19970405163731.AI51903@uriah.heep.sax.de> Date: Sat, 5 Apr 1997 16:37:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Cc: rlb@mindspring.com (Ron Bolin) Subject: Re: CVSUP RELENG_2_2 Question References: <33464317.2E0F@mindspring.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Richard Wackerbarth on Apr 5, 1997 06:49:08 -0600 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Richard Wackerbarth wrote: > No. You have the correct tag for the 2.2 tree. > However, it is likely that the current ipfilter stuff has not > been placed in that tree yet. Indeed. I've considered to merge it into 2.2, but eventually gave up. It was (and IMHO still is) in a defunct state as it's in the tree now. You need a lot of handwork in order to get it going. The source is in src/contrib, sure, but that's about almost all. It cannot be built as part of the kernel, only as an LKM yet. However, the LKM hooks to build it (under src/lkm) are missing, so it won't be build as an LKM by default. Likewise, the entire command hierarchy hooks that are finally expected to reference src/contrib/ipfilter are missing, too. (This probably requires a bunch of stub Makefiles, maybe with a few -D options in their CFLAGS, that reference the contrib stuff via .PATH statements.) The kernel sources can be compiled into a kernel, but not used, since they don't generate cdevsw entries. The required options to get ipfilter statically compiled into your kernel aren't described in LINT and src/sys/conf/options either. Once these points are fixed (which requires someone who's got a clue about how ipfilter is working, and who can test it -- thus not me), ipfilter can be tagged/merged into RELENG_2_2 as well. Note that the above is in no way ment to put somebody/something down here, only as a realistic status report about which things still need to be done (not necessarily by Darren himself) before we can consider it `ready to go'. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 6 00:39:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA02089 for current-outgoing; Sun, 6 Apr 1997 00:39:12 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA02080 for ; Sun, 6 Apr 1997 00:39:07 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA00615 for current@freebsd.org; Sun, 6 Apr 1997 10:39:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id QAA09173; Sat, 5 Apr 1997 16:44:27 +0200 (MET DST) Message-ID: <19970405164426.HQ39984@uriah.heep.sax.de> Date: Sat, 5 Apr 1997 16:44:26 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa sio.c References: <199704051348.XAA08067@godzilla.zeta.org.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199704051348.XAA08067@godzilla.zeta.org.au>; from Bruce Evans on Apr 5, 1997 23:48:48 +1000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > You must use `flags 0x10' for sio0 to recover the current default behaviour, > or `flags 0x30' for sio0 instead of `options COMCONSOLE'. The flags work > on any (one) sio unit. Somehow your commit to src/share/man/man4/man4.i386/sio.4 must have not made it through, can you redo it? :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 6 01:34:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA06296 for current-outgoing; Sun, 6 Apr 1997 01:34:39 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA06272 for ; Sun, 6 Apr 1997 01:34:33 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id BAA29834 for ; Sun, 6 Apr 1997 01:36:55 -0800 (PST) Received: (qmail 3596 invoked by uid 110); 6 Apr 1997 09:34:02 -0000 Message-ID: <19970406093402.3595.qmail@suburbia.net> Subject: ipfilter compilation In-Reply-To: <19970405163731.AI51903@uriah.heep.sax.de> from J Wunsch at "Apr 5, 97 04:37:31 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 6 Apr 1997 19:34:02 +1000 (EST) Cc: freebsd-current@freebsd.org, rlb@mindspring.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Indeed. > > I've considered to merge it into 2.2, but eventually gave up. It was > (and IMHO still is) in a defunct state as it's in the tree now. You > need a lot of handwork in order to get it going. The source is in > src/contrib, sure, but that's about almost all. It cannot be built as > part of the kernel, only as an LKM yet. However, the LKM hooks to > build it (under src/lkm) are missing, so it won't be build as an LKM > by default. Likewise, the entire command hierarchy hooks that are > finally expected to reference src/contrib/ipfilter are missing, too. > (This probably requires a bunch of stub Makefiles, maybe with a few -D > options in their CFLAGS, that reference the contrib stuff via .PATH > statements.) The kernel sources can be compiled into a kernel, but > not used, since they don't generate cdevsw entries. The required > options to get ipfilter statically compiled into your kernel aren't > described in LINT and src/sys/conf/options either. > > Once these points are fixed (which requires someone who's got a clue > about how ipfilter is working, and who can test it -- thus not me), > ipfilter can be tagged/merged into RELENG_2_2 as well. > > -- > cheers, J"org I've addressed all of these points appart from in-kernel compilation (see my kern pr). I don't believe that the ipfilter kernel code should have ever been placed in sys/netinet. This will cause no-end of future code-management trouble. sys/netinet/Makefile should be be modifed to union contrib/ipfilter and netinet transparently. Cherrs, Julian -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@suburbia.net |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-current Sun Apr 6 01:44:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA10025 for current-outgoing; Sun, 6 Apr 1997 01:44:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA09983 for ; Sun, 6 Apr 1997 01:44:22 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA01752 for freebsd-current@freebsd.org; Sun, 6 Apr 1997 11:44:20 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id LAA16355; Sun, 6 Apr 1997 11:42:12 +0200 (MET DST) Message-ID: <19970406114210.NQ47928@uriah.heep.sax.de> Date: Sun, 6 Apr 1997 11:42:10 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org Subject: Re: ipfilter compilation References: <19970405163731.AI51903@uriah.heep.sax.de> <19970406093402.3595.qmail@suburbia.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970406093402.3595.qmail@suburbia.net>; from proff@suburbia.net on Apr 6, 1997 19:34:02 +1000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As proff@suburbia.net wrote: > sys/netinet/Makefile should be > be modifed to union contrib/ipfilter and netinet transparently. sys/netinet/Makefile: No such file or directory. If there were any, it would be irrelevant for the kernel build, since the sys/compile//Makefile does this job. The sys/ tree is not supposed to have references to outside. I've been asking the very same question (about how to maintain the sys/netinet part of this code) when the discussion came up about importing ipfilter, but nobody seemed to be much interested in this point. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 6 01:58:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA12421 for current-outgoing; Sun, 6 Apr 1997 01:58:33 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA12412 for ; Sun, 6 Apr 1997 01:58:30 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id TAA07138; Sun, 6 Apr 1997 19:53:48 +1000 Date: Sun, 6 Apr 1997 19:53:48 +1000 From: Bruce Evans Message-Id: <199704060953.TAA07138@godzilla.zeta.org.au> To: current@freebsd.org, j@uriah.heep.sax.de Subject: Re: cvs commit: src/sys/i386/isa sio.c Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> You must use `flags 0x10' for sio0 to recover the current default behaviour, >> or `flags 0x30' for sio0 instead of `options COMCONSOLE'. The flags work >> on any (one) sio unit. > >Somehow your commit to src/share/man/man4/man4.i386/sio.4 must have >not made it through, can you redo it? Fortunately, the options weren't documented there, so there is nothing to change :-). I also want to do the configuration right before docmenting it properly. Joerg apparently had the same idea when he didn't put option BREAK_TO_DEBUGGER in sio.4 :-). Bruce From owner-freebsd-current Sun Apr 6 03:01:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA12639 for current-outgoing; Sun, 6 Apr 1997 03:01:08 -0700 (PDT) Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA12627 for ; Sun, 6 Apr 1997 03:00:59 -0700 (PDT) Received: (from davidn@localhost) by unique.usn.blaze.net.au (8.8.5/8.8.5) id UAA00890; Sun, 6 Apr 1997 20:00:57 +1000 (EST) Message-ID: <19970406200057.41951@usn.blaze.net.au> Date: Sun, 6 Apr 1997 20:00:57 +1000 From: David Nugent To: freebsd-current@freebsd.org Subject: Midnight Commander Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've verified this on two machines recently, but it seems that at least since the lite2 merge, "mc" seems broken. It mostly works, but is prone to hanging, and will *always* hang when type ^O to get to the background/pty shell. I tried both the pre-compiled port, then building it fresh from sources (not that I expected this to make a difference, but this was the road of Least Effort :-)). Before I waste a couple of hours looking into this, does anyone have any ideas? According to ps, it seems to be hung in "sbwait". Yes, yes, "real programmers" don't need a wimpy shell, but mc does some particular tasks very neatly and takes a lot less time to type than a multiline commandline (namely renaming using shell patterns). Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Sun Apr 6 03:06:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA12895 for current-outgoing; Sun, 6 Apr 1997 03:06:12 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA12890 for ; Sun, 6 Apr 1997 03:06:07 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA03627 for current@freebsd.org; Sun, 6 Apr 1997 12:06:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id MAA16638; Sun, 6 Apr 1997 12:04:47 +0200 (MET DST) Message-ID: <19970406120447.KM44522@uriah.heep.sax.de> Date: Sun, 6 Apr 1997 12:04:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa sio.c References: <199704060953.TAA07138@godzilla.zeta.org.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199704060953.TAA07138@godzilla.zeta.org.au>; from Bruce Evans on Apr 6, 1997 19:53:48 +1000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > I also want to do the configuration right before > docmenting it properly. Joerg apparently had the same idea when he > didn't put option BREAK_TO_DEBUGGER in sio.4 :-). Hmm, joerg never committed anything to sio.c. ;-) But you're probably right... we need three places to document options, sys/conf/options or sys//conf/options., plus LINT, plus the chapter 4 man pages... Sigh. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 6 04:08:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA16240 for current-outgoing; Sun, 6 Apr 1997 04:08:57 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA16235 for ; Sun, 6 Apr 1997 04:08:53 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id MAA03879; Sun, 6 Apr 1997 12:08:40 +0100 (BST) Date: Sun, 6 Apr 1997 12:08:40 +0100 (BST) From: Doug Rabson To: David Nugent cc: freebsd-current@freebsd.org Subject: Re: Midnight Commander In-Reply-To: <19970406200057.41951@usn.blaze.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Apr 1997, David Nugent wrote: > I've verified this on two machines recently, but it seems that > at least since the lite2 merge, "mc" seems broken. It mostly > works, but is prone to hanging, and will *always* hang when > type ^O to get to the background/pty shell. I tried both the > pre-compiled port, then building it fresh from sources (not that > I expected this to make a difference, but this was the road of > Least Effort :-)). > > Before I waste a couple of hours looking into this, does anyone > have any ideas? According to ps, it seems to be hung in "sbwait". Hmm. I have noticed that man(1) sometimes hangs in sbwait on one of my systems. It always comes back after 20 seconds or so. Maybe this is related? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Sun Apr 6 04:33:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA17465 for current-outgoing; Sun, 6 Apr 1997 04:33:37 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA17459 for ; Sun, 6 Apr 1997 04:33:33 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA10282 for current@freebsd.org; Sun, 6 Apr 1997 07:31:08 -0400 (EDT) From: Peter Dufault Message-Id: <199704061131.HAA10282@hda.hda.com> Subject: LKM's DISPATCH source interface changed To: current@freebsd.org Date: Sun, 6 Apr 1997 07:31:07 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The DISPATCH macro in lkm.h is now MOD_DISPATCH and you must pass in the name as the first argument: DISPATCH(lkmtp, cmd, ver, joy_load, joy_unload, joy_stat); is now: MOD_DISPATCH(joy, lkmtp, cmd, ver, joy_load, joy_unload, joy_stat); This is a source-only incompatability. I fixed the system files. Peter -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-current Sun Apr 6 05:29:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA19095 for current-outgoing; Sun, 6 Apr 1997 05:29:08 -0700 (PDT) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19085 for ; Sun, 6 Apr 1997 05:29:05 -0700 (PDT) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id FAA02063 for ; Sun, 6 Apr 1997 05:31:26 -0700 (PDT) Received: (qmail 5272 invoked by uid 110); 6 Apr 1997 12:28:33 -0000 Message-ID: <19970406122832.5270.qmail@suburbia.net> Subject: Re: ipfilter compilation In-Reply-To: <19970406114210.NQ47928@uriah.heep.sax.de> from J Wunsch at "Apr 6, 97 11:42:10 am" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 6 Apr 1997 22:28:32 +1000 (EST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As proff@suburbia.net wrote: > > sys/netinet/Makefile: No such file or directory. Yes, the situation isn't as simple as I had initially assumed. What actually takes place is config(8) builds a one-for-all Makefile in sys/compile/kernel_name based on path to option relationships specified in sys/conf/files and i386/conf/files. You could symlink the files back up to /usr/src/contrib/ipfilter/*, or symlink these down to sys/netinet, but cvs doesn't appear able to manage symlinks. There seems to be nothing preventing config(8) handling the following type of construct in sys/conf/files (which I think is the only reasonable solution, given how the kernel build is performed). ../../contrib/ipfilter/ip_fil.c optional ipfilter inet ../../contrib/ipfilter/fil.c optional ipfilter inet ../../contrib/ipfilter/ip_nat.c optional ipfilter inet ../../contrib/ipfilter/ip_frag.c optional ipfilter inet ../../contrib/ipfilter/ip_state.c optional ipfilter inet instead of: netinet/ip_fil.c optional ipfilter inet netinet/fil.c optional ipfilter inet netinet/ip_nat.c optional ipfilter inet netinet/ip_frag.c optional ipfilter inet netinet/ip_state.c optional ipfilter inet > The sys/ tree is not supposed to have references to outside. I've > been asking the very same question (about how to maintain the > > -- > cheers, J"org I don't see that outside references are a problem, provided the user is kept aware of them. The kernel does depend on some outside references i.e /usr/include and the all the tools used to build it. LINT/generic can simple be given this comment # you need src/contrib/ipfilter accessable to compile # ipfilter into the kernel options IPFILTER #options IPFITLER_LKM options IPFILTER_LOG This seems greatly perferable to me than splitting up a contributed package in such a way that it will be effectively unmaintainable. -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@suburbia.net |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-current Sun Apr 6 05:33:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA19256 for current-outgoing; Sun, 6 Apr 1997 05:33:48 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19245 for ; Sun, 6 Apr 1997 05:33:45 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id NAA13601; Sun, 6 Apr 1997 13:30:12 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 6 Apr 1997 13:26:39 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: <19970406200057.41951@usn.blaze.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 6 Apr 1997 13:24:20 +0100 To: Doug Rabson , David Nugent From: Bob Bishop Subject: Re: Midnight Commander Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:08 pm +0100 6/4/97, Doug Rabson wrote: >On Sun, 6 Apr 1997, David Nugent wrote: > >> I've verified this on two machines recently, but it seems that >> at least since the lite2 merge, "mc" seems broken. It mostly >> works, but is prone to hanging, and will *always* hang when >> type ^O to get to the background/pty shell. I tried both the >> pre-compiled port, then building it fresh from sources (not that >> I expected this to make a difference, but this was the road of >> Least Effort :-)). >> >> Before I waste a couple of hours looking into this, does anyone >> have any ideas? According to ps, it seems to be hung in "sbwait". > >Hmm. I have noticed that man(1) sometimes hangs in sbwait on one of my >systems. It always comes back after 20 seconds or so. Maybe this is >related? I've seen something similar with ftp(1) on -current. I'll check it again when it's finished building... -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Sun Apr 6 06:21:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA20782 for current-outgoing; Sun, 6 Apr 1997 06:21:41 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA20771 for ; Sun, 6 Apr 1997 06:21:36 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA05690 for freebsd-current@freebsd.org; Sun, 6 Apr 1997 15:21:24 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA17417; Sun, 6 Apr 1997 15:07:53 +0200 (MET DST) Message-ID: <19970406150753.SQ24384@uriah.heep.sax.de> Date: Sun, 6 Apr 1997 15:07:53 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org Subject: Re: ipfilter compilation References: <19970406114210.NQ47928@uriah.heep.sax.de> <19970406122832.5270.qmail@suburbia.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970406122832.5270.qmail@suburbia.net>; from proff@suburbia.net on Apr 6, 1997 22:28:32 +1000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As proff@suburbia.net wrote: > I don't see that outside references are a problem, provided the > user is kept aware of them. That's probably the best solution to handle src/contrib code for kernel-land, yes. But it makes packaging the distributions harder. Right now, it's sufficient to install the `ssys' distribution if you wanna rebuild your kernel. If we simply reference through ../../contrib in sys/conf/files, this will require the luser to install the entire contrib distribution bloat as it stands now. So this obviously needs a little more thoughts, and i hoped to get some thoughts from those people who were actually _asking_ for ipfilter. Well, that's certainly not me, i don't have any opportunity to use it. My only concern was as the 2.2 release engineer, to possibly get it into 2.2, but that's too late. > The kernel does depend on some outside > references i.e /usr/include... It only relies on /usr/include in order to compile an auxiliary binary, not to compile the kernel itself. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 6 07:14:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA22704 for current-outgoing; Sun, 6 Apr 1997 07:14:55 -0700 (PDT) Received: from mailhost (user-37kb44b.dialup.mindspring.com [207.69.144.139]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA22688 for ; Sun, 6 Apr 1997 07:14:52 -0700 (PDT) Received: from rlb by mailhost with smtp (Smail3.1.29.1 #1) id m0wDsiq-000G06C; Sun, 6 Apr 97 10:15 EDT Message-ID: <3347AFDF.14D9@mindspring.com> Date: Sun, 06 Apr 1997 10:14:55 -0400 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: CVSUP and Release Question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am using cvsup on tag=RELENG_2_2, but my build says 2.2-STABLE. What tag needs to be used for 2.2.1-RELEASE? Or do I just need to do a full download from the src tree on freebsd.org? Thank's Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ http://rlb.users.mindspring.com gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 Work: 770-246-5404 From owner-freebsd-current Sun Apr 6 07:18:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA22868 for current-outgoing; Sun, 6 Apr 1997 07:18:15 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA22861 for ; Sun, 6 Apr 1997 07:18:11 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id JAA15615; Sun, 6 Apr 1997 09:17:57 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <19970405163731.AI51903@uriah.heep.sax.de> References: ; from Richard Wackerbarth on Apr 5, 1997 06:49:08 -0600 <33464317.2E0F@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 6 Apr 1997 09:14:36 -0500 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: Richard Wackerbarth Subject: Re: CVSUP RELENG_2_2 Question Cc: freebsd-current@freebsd.org (FreeBSD-current users), rlb@mindspring.com (Ron Bolin) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 9:37 AM -0500 4/5/97, J Wunsch wrote: >As Richard Wackerbarth wrote: > >> No. You have the correct tag for the 2.2 tree. >> However, it is likely that the current ipfilter stuff has not >> been placed in that tree yet. > >Indeed. > >I've considered to merge it into 2.2, but eventually gave up. It was >(and IMHO still is) in a defunct state [...] >Once these points are fixed (which requires someone who's got a clue >about how ipfilter is working, and who can test it -- thus not me), >ipfilter can be tagged/merged into RELENG_2_2 as well. Note that, IMHO, this is as it should be. All of us who clammor that it is too early to really kill the 2.1 branch will have even more ammunition if things were still going into the 2.2 branch "before they are ready". The head branch is the development ground. If things are not quite right there, it is understood. However, the other branches should be protected from such problems. From owner-freebsd-current Sun Apr 6 08:21:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA00781 for current-outgoing; Sun, 6 Apr 1997 08:21:51 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA00775 for ; Sun, 6 Apr 1997 08:21:42 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.8.5/8.6.9) with ESMTP id RAA12626 for ; Sun, 6 Apr 1997 17:21:51 GMT Message-Id: <199704061721.RAA12626@peedub.gj.org> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-current@freebsd.org Subject: Re: ipfilter compilation Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 06 Apr 1997 19:34:02 +1000." <19970406093402.3595.qmail@suburbia.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Apr 1997 17:21:50 +0000 From: Gary Jennejohn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk proff@suburbia.net writes: >> -- [Joerg's comments deleted] >> cheers, J"org > >I've addressed all of these points appart from in-kernel compilation >(see my kern pr). I don't believe that the ipfilter kernel code >should have ever been placed in sys/netinet. This will cause no-end >of future code-management trouble. sys/netinet/Makefile should be >be modifed to union contrib/ipfilter and netinet transparently. > I grabbed the kern pr and managed to get ipfilter to compile into the kernel (under both -current and 2.2.1) with some rather trivial modifications. ipfilter still compiles as an LKM with my mods. The biggest problem was that Julian only patched the files in contrib. But it's easy to copy the files needed to make a kernel into netinet. One thing I had to do which I didn't care for too much was make mlf_ipl.c part of the kernel, since this is where the DEVFS and SYSINIT stuff gets handled. Regarding whether the kernel build should reference files outside the kernel src tree, note that Darren did import the apropriate files into netinet. In my opinion we should make sure that these files are kept up-to-date with what's in contrib, rather than referencing ../../contrib/ipfilter in /sys/conf/files (although I _did_ do this for my tests :). I'd say that, pending review, we now have the necessary scaffolding to make ipfilter an integral part of FreeBSD. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-current Sun Apr 6 09:12:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA08889 for current-outgoing; Sun, 6 Apr 1997 09:12:27 -0700 (PDT) Received: from alpha.risc.org (taob@trt-on23-04.netcom.ca [207.181.99.68]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA08884 for ; Sun, 6 Apr 1997 09:12:22 -0700 (PDT) Received: from localhost (taob@localhost) by alpha.risc.org (8.8.4/8.8.4) with SMTP id MAA13865 for ; Sun, 6 Apr 1997 12:12:15 -0400 (EDT) Date: Sun, 6 Apr 1997 12:12:15 -0400 (EDT) From: Brian Tao To: FREEBSD-CURRENT-L Subject: XFree86 3.2 causes constant 1.0 load average? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone else noticed that XFree86 3.2 will in many cases (but not always) cause a 2.2 or 3.0 system to report a load average of at least 1.0? ps/top both indicate little or no CPU activity, but the load average does not fall below 1.0 unless I kill off X. I'm running AfterStep 1.0pre6 as the window manager, but the X application mix can vary (with or without Netscape running, xterm windows with very little update activity, etc.) What would cause FreeBSD to report a load average of 1+ when there is no system load? last pid: 13859; load averages: 1.31, 1.42, 1.45 12:09:25 50 processes: 1 running, 49 sleeping CPU states: 0.4% user, 0.0% nice, 1.2% system, 0.0% interrupt, 98.5% idle Mem: 33M Active, 3592K Inact, 15M Wired, 8280K Cache, 7644K Buf, 2364K Free Swap: 128M Total, 24M Used, 104M Free, 19% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 8121 root 2 0 7788K 16368K select 831:43 1.53% 1.53% XF86_Mach64 12566 taob 2 0 564K 1484K select 0:18 0.99% 0.99% xterm 13859 taob 28 0 324K 828K RUN 0:00 0.46% 0.38% top 8182 taob 2 0 3140K 2112K select 0:21 0.11% 0.11% screen-3.7.1 13857 taob 2 0 600K 964K select 0:00 0.12% 0.11% vim -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" From owner-freebsd-current Sun Apr 6 09:24:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA09392 for current-outgoing; Sun, 6 Apr 1997 09:24:46 -0700 (PDT) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09385 for ; Sun, 6 Apr 1997 09:24:42 -0700 (PDT) Received: from dual (DUAL [192.187.167.136]) by mantar.slip.netcom.com (8.8.5/8.8.5) with SMTP id JAA03048; Sun, 6 Apr 1997 09:24:06 -0700 (PDT) Message-Id: <3.0.1.32.19970406092409.009459e0@mantar.slip.netcom.com> X-Sender: guest@mantar.slip.netcom.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Sun, 06 Apr 1997 09:24:09 -0700 To: David Nugent , freebsd-current@freebsd.org From: Manfred Antar Subject: Re: Midnight Commander In-Reply-To: <19970406200057.41951@usn.blaze.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:00 PM 4/6/97 +1000, David Nugent wrote: >I've verified this on two machines recently, but it seems that >at least since the lite2 merge, "mc" seems broken. It mostly >works, but is prone to hanging, and will *always* hang when >type ^O to get to the background/pty shell. I tried both the >pre-compiled port, then building it fresh from sources (not that >I expected this to make a difference, but this was the road of >Least Effort :-)). > >Before I waste a couple of hours looking into this, does anyone >have any ideas? According to ps, it seems to be hung in "sbwait". > >Yes, yes, "real programmers" don't need a wimpy shell, but mc >does some particular tasks very neatly and takes a lot less time >to type than a multiline commandline (namely renaming using >shell patterns). The only way i can get it to not hang is to build it manually with these args. configure --without-subshell then make it works fine then Manfred |==============================| | mantar@netcom.com | | Ph. (415) 681-6235 | |==============================| From owner-freebsd-current Sun Apr 6 09:40:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA10926 for current-outgoing; Sun, 6 Apr 1997 09:40:12 -0700 (PDT) Received: from vital.bleeding.com (flea.bleeding.com [205.166.195.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA10919 for ; Sun, 6 Apr 1997 09:40:06 -0700 (PDT) Received: from crimson (crimson.bleeding.com [205.166.254.2]) by vital.bleeding.com (8.8.5/8.8.5) with SMTP id JAA02555; Sun, 6 Apr 1997 09:37:20 -0700 (PDT) Received: by crimson with Microsoft Mail id <01BC426E.D624C120@crimson>; Sun, 6 Apr 1997 09:42:26 -0700 Message-ID: <01BC426E.D624C120@crimson> From: Justin Wolf To: FREEBSD-CURRENT-L , "'Brian Tao'" Subject: RE: XFree86 3.2 causes constant 1.0 load average? Date: Sun, 6 Apr 1997 09:42:25 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id JAA10920 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To expand on this a little... what would cause 2.2 to report 1.0 loadavgs when there's nothing going on? I've noticed this happening after killing threads and such and rebooting is the only way to get it back to 0. Is this a bug under 2.2? (Although I first noticed it after running X, it's now happening even without.) -Justin Wolf ---------- From: Brian Tao[SMTP:taob@risc.org] Sent: Sunday, April 06, 1997 5:12 AM To: FREEBSD-CURRENT-L Subject: XFree86 3.2 causes constant 1.0 load average? Has anyone else noticed that XFree86 3.2 will in many cases (but not always) cause a 2.2 or 3.0 system to report a load average of at least 1.0? ps/top both indicate little or no CPU activity, but the load average does not fall below 1.0 unless I kill off X. I'm running AfterStep 1.0pre6 as the window manager, but the X application mix can vary (with or without Netscape running, xterm windows with very little update activity, etc.) What would cause FreeBSD to report a load average of 1+ when there is no system load? last pid: 13859; load averages: 1.31, 1.42, 1.45 12:09:25 50 processes: 1 running, 49 sleeping CPU states: 0.4% user, 0.0% nice, 1.2% system, 0.0% interrupt, 98.5% idle Mem: 33M Active, 3592K Inact, 15M Wired, 8280K Cache, 7644K Buf, 2364K Free Swap: 128M Total, 24M Used, 104M Free, 19% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 8121 root 2 0 7788K 16368K select 831:43 1.53% 1.53% XF86_Mach64 12566 taob 2 0 564K 1484K select 0:18 0.99% 0.99% xterm 13859 taob 28 0 324K 828K RUN 0:00 0.46% 0.38% top 8182 taob 2 0 3140K 2112K select 0:21 0.11% 0.11% screen-3.7.1 13857 taob 2 0 600K 964K select 0:00 0.12% 0.11% vim -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" From owner-freebsd-current Sun Apr 6 10:00:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA14212 for current-outgoing; Sun, 6 Apr 1997 10:00:29 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14201 for ; Sun, 6 Apr 1997 10:00:25 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id KAA12364; Sun, 6 Apr 1997 10:00:22 -0700 (PDT) Message-Id: <199704061700.KAA12364@austin.polstra.com> To: rlb@mindspring.com Subject: Re: CVSUP and Release Question Newsgroups: polstra.freebsd.current In-Reply-To: <3347AFDF.14D9@mindspring.com> References: <3347AFDF.14D9@mindspring.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Sun, 06 Apr 1997 10:00:21 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <3347AFDF.14D9@mindspring.com>, Ron Bolin wrote: > I am using cvsup on tag=RELENG_2_2, but my build says 2.2-STABLE. > > What tag needs to be used for 2.2.1-RELEASE? I guess I need to update the documentation again. :-} tag=RELENG_2_2_1_RELEASE Unless you're trying to build some kind of reference platform, you'd be better off continuing to use RELENG_2_2. 2.2-stable already contains bugfixes that were not present when 2.2.1 was released. Here's a complete list of tags from the top-level Makefile: RELENG_2_2_1_RELEASE RELENG_2_2_0_RELEASE RELENG_2_1_7_RELEASE RELENG_2_1_6_1_RELEASE RELENG_2_1_6_RELEASE RELENG_2_2 RELENG_2_2_BP RELENG_2_1_5_RELEASE RELENG_2_1_0_RELEASE RELENG_2_1_0 RELENG_2_1_0_BP RELENG_2_0_5_RELEASE RELENG_2_0_5 RELENG_2_0_5_BP RELENG_2_0_5_ALPHA RELEASE_2_0 BETA_2_0 ALPHA_2_0 bsd_44_lite CSRG The ones ending in "RELEASE" are specific released versions. The ones ending in a digit are generally the corresponding -stable branches. I'd stay away from the others, if I were you. John -- 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 Sun Apr 6 11:09:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA23978 for current-outgoing; Sun, 6 Apr 1997 11:09:02 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23973 for ; Sun, 6 Apr 1997 11:08:59 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id LAA03330; Sun, 6 Apr 1997 11:08:55 -0700 (PDT) To: Ron Bolin cc: FreeBSD Current Mailing List Subject: Re: CVSUP and Release Question In-reply-to: Your message of "Sun, 06 Apr 1997 10:14:55 EDT." <3347AFDF.14D9@mindspring.com> Date: Sun, 06 Apr 1997 11:08:54 -0700 Message-ID: <3327.860350134@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am using cvsup on tag=RELENG_2_2, but my build says 2.2-STABLE. Joerg jumped the gun on calling it -stable, but now I don't want to switch it back because there will end up being two sets of people with "2.2-STABLE" in their uname line - the pre-stables and the real-stables. :-) I guess we'd just better hurry up and make it stable. :-) In any case, you're grabbing the right tag if you're just trying to stay up to date with 2.2. If you grabbed RELENG_2_2_1_RELEASE then you'd have the 2.2.1 release itself, but I don't see the point? Jordan From owner-freebsd-current Sun Apr 6 13:59:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA00921 for current-outgoing; Sun, 6 Apr 1997 13:59:52 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA00915; Sun, 6 Apr 1997 13:59:49 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199704062059.NAA00915@freefall.freebsd.org> Subject: Re: Hello To: cgagnon@xoca-160.ssg.gunter.af.mil (Chuck Gagnon) Date: Sun, 6 Apr 1997 13:59:48 -0700 (PDT) Cc: freebsd-current@freebsd.org In-Reply-To: <3343E8FB.2CAE@xoca-160.ssc.af.mil> from "Chuck Gagnon" at Apr 3, 97 11:29:31 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chuck Gagnon wrote: > > I'm Sorry about this but for some reason I am no longer getting any > mail from this list. I got a reply from both my unsubscribe and > subscribe (in that order), but nothing else. If anyone gets this > could you please let me know (I feel so alone). > -- > SrA Charles G. Gagnon Jr. | Email:cgagnon@xoca-160.ssg.gunter.af.mil > Chuck, your site was bouncing mail. enough mail that i removed you from the mailing list. please resubscribe. your host "xoca-160.ssg.gunter.af.mil" is not well supported in the Domain Name System (DNS). it has a address record only. it should have an MX record as well, if not two. jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB From owner-freebsd-current Sun Apr 6 21:31:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA18076 for current-outgoing; Sun, 6 Apr 1997 21:31:51 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18042 for ; Sun, 6 Apr 1997 21:31:46 -0700 (PDT) Received: from waru.life.nthu.edu.tw (root@waru.feminism.net [140.114.98.107]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id RAA27461 for ; Sun, 6 Apr 1997 17:11:47 -0700 (PDT) Received: from waru.life.nthu.edu.tw (frankch@waru.feminism.net [140.114.98.107]) by waru.life.nthu.edu.tw (8.8.5/8.8.5) with SMTP id IAA05209; Mon, 7 Apr 1997 08:13:02 +0800 (CST) Date: Mon, 7 Apr 1997 08:13:02 +0800 (CST) From: Frank Chen Hsiung Chan To: Brian Tao cc: FREEBSD-CURRENT-L Subject: Re: XFree86 3.2 causes constant 1.0 load average? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Apr 1997, Brian Tao wrote: > Has anyone else noticed that XFree86 3.2 will in many cases (but > not always) cause a 2.2 or 3.0 system to report a load average of at > least 1.0? ps/top both indicate little or no CPU activity, but the > load average does not fall below 1.0 unless I kill off X. We had this problem here. We then found that the asclock is responsible for this. Try not running asclock and/or other asstuff, that might help. --frank From owner-freebsd-current Sun Apr 6 21:32:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA18304 for current-outgoing; Sun, 6 Apr 1997 21:32:27 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18287 for ; Sun, 6 Apr 1997 21:32:23 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-4-80.mu.de.ibm.net [139.92.4.80]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id RAA27562 ; Sun, 6 Apr 1997 17:21:22 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id CAA26159; Mon, 7 Apr 1997 02:20:43 +0200 (MET DST) Message-Id: <199704070020.CAA26159@vector.jhs.no_domain> To: Ron Bolin cc: FreeBSD Current Mailing List Subject: Re: CVSUP and Release Question From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" X-Email: jhs@freebsd.org, Fallback: jhs@gil.physik.rwth-aachen.de X-Organization: Vector Systems Ltd. X-Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Tel: Phone +49.89.268616, Fax +49.89.2608126, Data +49.89.26023276 X-Web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Sun, 06 Apr 1997 10:14:55 EDT." <3347AFDF.14D9@mindspring.com> Date: Mon, 07 Apr 1997 02:20:39 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Ron Bolin > > I am using cvsup on tag=RELENG_2_2, but my build says 2.2-STABLE. > > What tag needs to be used for 2.2.1-RELEASE? RELENG_2_2_1_RELEASE as listed in /usr/cvs/src/Makefile,v AFAIK, but don't take my word for it, I'm just a cvs-stumbler-in-the-dark :-) > Or do I just > need to do a full download from the src tree on freebsd.org? The beauty of having the cvs tree is you can extract anything, so no. > > Thank's > Ron > -- > **************************************************************************** > Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ > http://rlb.users.mindspring.com gs01rlb@panther.gsu.edu > matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 Work: 770-246-5404 > > Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sun Apr 6 21:33:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA18809 for current-outgoing; Sun, 6 Apr 1997 21:33:43 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18754 for ; Sun, 6 Apr 1997 21:33:35 -0700 (PDT) Received: from alpha.risc.org (taob@trt-on8-10.netcom.ca [207.181.82.202]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id QAA27058 for ; Sun, 6 Apr 1997 16:11:00 -0700 (PDT) Received: from localhost (taob@localhost) by alpha.risc.org (8.8.4/8.8.4) with SMTP id TAA14111; Sun, 6 Apr 1997 19:10:32 -0400 (EDT) Date: Sun, 6 Apr 1997 19:10:31 -0400 (EDT) From: Brian Tao To: Justin Wolf cc: FREEBSD-CURRENT-L Subject: RE: XFree86 3.2 causes constant 1.0 load average? In-Reply-To: <01BC426E.D624C120@crimson> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Apr 1997, Justin Wolf wrote: > > To expand on this a little... what would cause 2.2 to report 1.0 > loadavgs when there's nothing going on? I've noticed this happening > after killing threads and such and rebooting is the only way to get > it back to 0. Is this a bug under 2.2? (Although I first noticed it > after running X, it's now happening even without.) I'm always in X, so I don't notice if the problem persists without it, but it seems to come and go on its own under X. Right now, for example, the load average is at a more sensible level, but I'm running the same application mix as before. I think I may have run xlock a couple of times and acroread in between. last pid: 14108; load averages: 0.17, 0.32, 0.60 19:09:38 52 processes: 4 running, 48 sleeping CPU states: 2.2% user, 0.0% nice, 1.5% system, 0.0% interrupt, 96.4% idle Mem: 30M Active, 8856K Inact, 15M Wired, 7372K Cache, 7602K Buf, 1128K Free Swap: 128M Total, 21M Used, 107M Free, 16% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 8121 root 28 0 7788K 16968K RUN 851:41 0.99% 0.99% XF86_Mach64 14108 root 28 0 324K 804K RUN 0:00 3.36% 0.61% top 14099 taob 28 0 564K 1936K RUN 0:01 0.11% 0.11% xterm 8182 taob 28 0 3140K 800K RUN 0:31 0.04% 0.04% screen-3.7.1 12299 taob 18 0 1140K 1620K pause 21:01 0.00% 0.00% xearth [...] -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" From owner-freebsd-current Sun Apr 6 21:44:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA21435 for current-outgoing; Sun, 6 Apr 1997 21:44:58 -0700 (PDT) Received: from zeus.xtalwind.net (slipper7a.xtalwind.net [205.160.242.63]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA21423 for ; Sun, 6 Apr 1997 21:44:53 -0700 (PDT) Received: from localhost (zeus.xtalwind.net [127.0.0.1]) by zeus.xtalwind.net (8.8.5/8.8.5) with SMTP id AAA03521; Mon, 7 Apr 1997 00:31:09 -0400 (EDT) Date: Mon, 7 Apr 1997 00:31:09 -0400 (EDT) From: jack X-Sender: jack@zeus.xtalwind.net To: Justin Wolf cc: FREEBSD-CURRENT-L , "'Brian Tao'" Subject: RE: XFree86 3.2 causes constant 1.0 load average? In-Reply-To: <01BC426E.D624C120@crimson> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Apr 1997, Justin Wolf wrote: > To expand on this a little... what would cause 2.2 to report 1.0 > loadavgs when there's nothing going on? I've noticed this happening > after killing threads and such and rebooting is the only way to get it > back to 0. Is this a bug under 2.2? (Although I first noticed it after > running X, it's now happening even without.) > > -Justin Wolf > > ---------- > From: Brian Tao[SMTP:taob@risc.org] > Sent: Sunday, April 06, 1997 5:12 AM > To: FREEBSD-CURRENT-L > Subject: XFree86 3.2 causes constant 1.0 load average? > > Has anyone else noticed that XFree86 3.2 will in many cases (but > not always) cause a 2.2 or 3.0 system to report a load average of at > least 1.0? ps/top both indicate little or no CPU activity, but the > load average does not fall below 1.0 unless I kill off X. > > I'm running AfterStep 1.0pre6 as the window manager, but the X > application mix can vary (with or without Netscape running, xterm > windows with very little update activity, etc.) What would cause > FreeBSD to report a load average of 1+ when there is no system load? I've yet to notice that here with 2.2.1-RELEASE, and AfterStep. ????? last pid: 3510; load averages: 0.31, 0.44, 0.49 00:26:59 43 processes: 1 running, 42 sleeping CPU states: 0.8% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.2% idle Mem:14M Active, 4372K Inact, 7728K Wired, 3848K Cache, 3540K Buf, 888K Free Swap: 128M Total, 28M Used, 100M Free, 22% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 3203 jack 2 0 4536K 7064K select 1:41 2.48% 2.48% XF86_S3 3495 jack 18 0 672K 776K pause 0:00 0.00% 0.00% tcsh 3220 jack 18 0 620K 516K pause 0:03 0.00% 0.00% xearth 3211 jack 18 0 212K 460K pause 0:09 0.00% 0.00% asclock 165 root 18 0 432K 180K pause 0:14 0.00% 0.00% httpd 2414 root 18 0 692K 168K pause 0:00 0.00% 0.00% tcsh -------------------------------------------------------------------------- Jack O'Neill Finger jacko@diamond.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD -------------------------------------------------------------------------- From owner-freebsd-current Sun Apr 6 22:07:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA22294 for current-outgoing; Sun, 6 Apr 1997 22:07:48 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA22288 for ; Sun, 6 Apr 1997 22:07:46 -0700 (PDT) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id WAA16178; Sun, 6 Apr 1997 22:03:04 -0700 (PDT) Date: Sun, 6 Apr 1997 22:13:18 -0700 (PDT) From: Tom Samplonius To: Ron Bolin cc: FreeBSD Current Mailing List Subject: Re: CVSUP and Release Question In-Reply-To: <3347AFDF.14D9@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Apr 1997, Ron Bolin wrote: > I am using cvsup on tag=RELENG_2_2, but my build says 2.2-STABLE. That's right. Things have moved on since 2.2.1 already... > What tag needs to be used for 2.2.1-RELEASE? Or do I just > need to do a full download from the src tree on freebsd.org? That would work. If you have cvs tree (sounds like you don't, and it would a lot of work to get), you could co that tag. > Thank's > Ron > -- > **************************************************************************** > Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ > http://rlb.users.mindspring.com gs01rlb@panther.gsu.edu > matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 Work: 770-246-5404 > Tom From owner-freebsd-current Sun Apr 6 23:47:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA26148 for current-outgoing; Sun, 6 Apr 1997 23:47:27 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA26142 for ; Sun, 6 Apr 1997 23:47:19 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.5) id QAA17440 for freebsd-current@freebsd.org; Mon, 7 Apr 1997 16:47:16 +1000 Received: from troll.devetir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id QAA14650 for ; Mon, 7 Apr 1997 16:51:20 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.devetir.qld.gov.au (8.8.5/8.8.5) with SMTP id QAA10546; Mon, 7 Apr 1997 16:46:37 +1000 (EST) Message-Id: <199704070646.QAA10546@troll.devetir.qld.gov.au> X-Authentication-Warning: troll.devetir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: freebsd-current@freebsd.org cc: syssgm@dtir.qld.gov.au Subject: Hang during NFS stress test Date: Mon, 07 Apr 1997 16:46:37 +1000 From: Stephen McKay Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Setup: 386DX20 with 8Mb ram running 2.2.1 (or very close) continually copying files from a 486DX33 running 2.1.7 back to the same mount point via TCP NFS. After two days (continuous copying) it has locked up. It still responds to pings, will switch virtual consoles, and I can get into ddb, but nothing else. Ddb shows that the machine is stuck in idle_loop(), and no processes are on the run queue (whichqs == 0), but ps (ddb command) shows a number of processes which are not waiting on anything. For example, there are 3 getty's on the syscons virtual screens, and only one has non-zero wchan (probably because I hit enter a few times on some screens to see if I could wake them up). The only unusual wchan is swapper waiting on swinuw (which must be from pmap_swapin_proc). Other processes are in nfsidl, pause, wait, ttyin, etc. Any ideas what is going on? I will keep the system up and hung in case anyone can think of any good tests. This system makes bad core dumps, so I can't save this stuff forever. Stephen. From owner-freebsd-current Mon Apr 7 01:28:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA00990 for current-outgoing; Mon, 7 Apr 1997 01:28:11 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00981 for ; Mon, 7 Apr 1997 01:28:08 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id LAA01124 for current@freebsd.org; Mon, 7 Apr 1997 11:28:34 +0300 (EET DST) From: mika ruohotie Message-Id: <199704070828.LAA01124@shadows.aeon.net> Subject: goose chase... To: current@freebsd.org Date: Mon, 7 Apr 1997 11:28:34 +0300 (EET DST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well... i might be after wild gooses here, but i have a reason to believe windows 95 telnet is able to cause something weird on my -current machine, problem started about 2 weeks ago, it might've been caused by me implementing /etc/login.conf but i'm not sure. (yes, yes, i didnt have that, or /etc/sysconfig for a _long_ while, byt finally took the whole machine into the _truly_ current stage) reason i report this is if anyone else is having weird things also... the symptoms are from slow as hell performance on the telnet window (on that win95) and occasionally it reboots! the bsd. (with different kernels, been updating those rather often) i didnt think that's possible until today when i found out it is not only the ether connected win95 that can make this, but also a remote win95 telnetting into the machine thru ppp0 from random machine. and it's only? those win95 telnets that cause this, i constantly ssh and other people telnet from where-ever and i dont see probs with that. sure, it could be, and most likely is win95 prob, but why did it appear only now? assuming it did appear. it also might not have anything to do with the telnet, but i believe i managed to generate the reboots to _bsd_ that way. it appeared to reboot after similar things on the win95 end, but it might've been only coincidence. i'd be shrugging this off if it would not be my _bsd_ that it reboots?. i have a 67 meg vmcore.0, but i dont know what to do with it... =) (gdb tells me my kernel.0 and vmcore.0 are unknown format) mickey From owner-freebsd-current Mon Apr 7 01:53:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA02235 for current-outgoing; Mon, 7 Apr 1997 01:53:16 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA02228 for ; Mon, 7 Apr 1997 01:53:12 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.4/8.8.4) id BAA29595; Mon, 7 Apr 1997 01:52:57 -0700 (PDT) Message-ID: <19970407015257.62070@hydrogen.nike.efn.org> Date: Mon, 7 Apr 1997 01:52:57 -0700 From: John-Mark Gurney To: mika ruohotie Cc: current@freebsd.org Subject: Re: goose chase... References: <199704070828.LAA01124@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199704070828.LAA01124@shadows.aeon.net>; from mika ruohotie on Mon, Apr 07, 1997 at 11:28:34AM +0300 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2-960801-SNAP 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk mika ruohotie scribbled this message on Apr 7: > i have a 67 meg vmcore.0, but i dont know what to do with it... =) > (gdb tells me my kernel.0 and vmcore.0 are unknown format) try running: gdb -k kernel.0 vmcore.0 also.. see the section in the handbook on kernel debugging... it's actually quite informative and useful... :) hope this helps... ttyl.. -- John-Mark Cu Networking Modem/FAX: +1 541 683 6954 Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Mon Apr 7 02:56:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA05493 for current-outgoing; Mon, 7 Apr 1997 02:56:49 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05484 for ; Mon, 7 Apr 1997 02:56:44 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.5/8.8.5) with ESMTP id LAA04178 for ; Mon, 7 Apr 1997 11:51:53 +0200 (MDT) Received: from curry.mchp.siemens.de (1@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.4/8.8.4) with ESMTP id LAA09461 for ; Mon, 7 Apr 1997 11:56:40 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.5/8.8.5) id LAA29136 for freebsd-current@freebsd.org; Mon, 7 Apr 1997 11:56:38 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199704070956.LAA02609@curry.mchp.siemens.de> Subject: id missing in 2.2 To: freebsd-current@freebsd.org Date: Mon, 7 Apr 1997 11:56:33 +0200 (CEST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, we have a directory /usr/src/usr.bin/id but no entry for id in /usr/src/usr.bin/Makefile. Is this correct? -Andre From owner-freebsd-current Mon Apr 7 03:28:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA06754 for current-outgoing; Mon, 7 Apr 1997 03:28:40 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA06747 for ; Mon, 7 Apr 1997 03:28:32 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.4/8.8.4) id DAA00475; Mon, 7 Apr 1997 03:28:09 -0700 (PDT) Message-ID: <19970407032809.56649@hydrogen.nike.efn.org> Date: Mon, 7 Apr 1997 03:28:09 -0700 From: John-Mark Gurney To: Andre Albsmeier Cc: freebsd-current@freebsd.org Subject: Re: id missing in 2.2 References: <199704070956.LAA02609@curry.mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199704070956.LAA02609@curry.mchp.siemens.de>; from Andre Albsmeier on Mon, Apr 07, 1997 at 11:56:33AM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2-960801-SNAP 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andre Albsmeier scribbled this message on Apr 7: > Hi, > > we have a directory /usr/src/usr.bin/id but no entry for id in > /usr/src/usr.bin/Makefile. Is this correct? are you sure?? I just checked out a copy of src/usr.bin/Makefile and it seems to exist: hydrogen,ttypa,/tmp/22,513$cvs co -r RELENG_2_2 src/usr.bin/Makefile U src/usr.bin/Makefile hydrogen,ttypa,/tmp/22,514$grep id src/usr.bin/Makefile gprof head hexdump host id indent ipcrm ipcs \ what's the version of your Makefile that your looking at? ttyl... -- John-Mark Cu Networking Modem/FAX: +1 541 683 6954 Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Mon Apr 7 07:52:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA16691 for current-outgoing; Mon, 7 Apr 1997 07:52:57 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA16681 for ; Mon, 7 Apr 1997 07:52:46 -0700 (PDT) Received: from grimbling ([89.10.0.0]) by isbalham.ist.co.uk (8.8.4/8.8.4) with ESMTP id PAA19003 for ; Mon, 7 Apr 1997 15:50:59 +0100 (BST) Message-Id: <199704071450.PAA19003@isbalham.ist.co.uk> From: "Bob Bishop" To: Subject: Is it me... Date: Mon, 7 Apr 1997 15:51:06 +0100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ...or have things slowed down recently? I'm finding make world of ctm src-cur 2829 with a kernel of the same vintage taking something like three times as long as I'd expect. -- Bob Bishop +44 118 977 4017 rb@gid.co.uk From owner-freebsd-current Mon Apr 7 09:35:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA21984 for current-outgoing; Mon, 7 Apr 1997 09:35:42 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA21976 for ; Mon, 7 Apr 1997 09:35:37 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA21355 for freebsd-current@FreeBSD.ORG; Mon, 7 Apr 1997 18:35:35 +0200 Received: (from j@localhost) by jette.heep.sax.de (8.8.5/8.8.5) id SAA00291; Mon, 7 Apr 1997 18:21:12 +0200 (CEST) Message-ID: <19970407182108.RO31161@jette.heep.sax.de> Date: Mon, 7 Apr 1997 18:21:08 +0200 From: j@jette.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG (FreeBSD Current Mailing List) Subject: Re: CVSUP and Release Question References: <3347AFDF.14D9@mindspring.com> <3327.860350134@time.cdrom.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3327.860350134@time.cdrom.com>; from Jordan K. Hubbard on Apr 6, 1997 11:08:54 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > I am using cvsup on tag=RELENG_2_2, but my build says 2.2-STABLE. > > Joerg jumped the gun on calling it -stable, but now I don't want > to switch it back because there will end up being two sets of > people with "2.2-STABLE" in their uname line - the pre-stables and > the real-stables. :-) So, this was the intended effect. :-) -- bye, J"org ...just travelling around. Don't try reaching me except by mail. :) From owner-freebsd-current Mon Apr 7 10:14:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA24668 for current-outgoing; Mon, 7 Apr 1997 10:14:36 -0700 (PDT) Received: from ouray.cudenver.edu (aybaram@ouray.cudenver.edu [132.194.10.9]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA24663 for ; Mon, 7 Apr 1997 10:14:32 -0700 (PDT) Received: by ouray.cudenver.edu (5.65/DEC-OSF/1.2) id AA08645; Mon, 7 Apr 1997 11:16:00 -0600 From: aybaram@ouray.cudenver.edu (Alex Baram) Message-Id: <9704071716.AA08645@ouray.cudenver.edu> To: freebsd-current@freebsd.org Date: Mon, 7 Apr 1997 11:16:00 -0600 (MDT) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-current Mon Apr 7 11:03:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA27517 for current-outgoing; Mon, 7 Apr 1997 11:03:05 -0700 (PDT) Received: from tica.jetstream.net (mail.jetstream.net [206.186.149.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA27498 for ; Mon, 7 Apr 1997 11:03:01 -0700 (PDT) Received: from bm.jetstream.net ([206.186.149.206]) by tica.jetstream.net (post.office MTA v2.0 0813 ID# 0-14040) with ESMTP id AAA50 for ; Mon, 7 Apr 1997 11:08:14 -0700 Message-ID: <32FB6E57.7A4B@mwc.net> Date: Fri, 07 Feb 1997 10:03:03 -0800 From: bmarr@jetstream.net (Braden Marr) Organization: Major Wireless Communications X-Mailer: Mozilla 4.0b2 (Win95; I) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Priority: 3 (Normal) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-current Mon Apr 7 11:07:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA27963 for current-outgoing; Mon, 7 Apr 1997 11:07:57 -0700 (PDT) Received: from gaia.coppe.ufrj.br (root@cisigw.coppe.ufrj.br [146.164.2.31]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA27958 for ; Mon, 7 Apr 1997 11:07:54 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.5/8.7.3) id OAA27406; Mon, 7 Apr 1997 14:12:05 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199704071712.OAA27406@gaia.coppe.ufrj.br> Subject: Re: make -j3 on make world? To: scrappy@hub.org (The Hermit Hacker) Date: Mon, 7 Apr 1997 14:12:05 -0300 (EST) Cc: current@freebsd.org In-Reply-To: from The Hermit Hacker at "Mar 30, 97 05:10:15 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk #define quoting(The Hermit Hacker) // On Sun, 30 Mar 1997, The Hermit Hacker wrote: // // > // > Hi... // > // > Is there a way of doing a 'make -j3 world'? I've tried it, and it // > doesn't seem to work, based on what I observe when doing a 'make -j3' when // > building the kernel... // > // > // > // // // Hi again... // // In reply to my own email, I did some playing around last night // with the /usr/share/mk/* files, bsd.subdir.mk in particular, and came // up with: // // _SUBDIRUSE: .USE // @for entry in ${SUBDIR}; do \ // (if test -d ${.CURDIR}/$${entry}.${MACHINE}; then \ // ${ECHODIR} "===> ${DIRPRFX}$${entry}.${MACHINE}"; \ // edir=$${entry}.${MACHINE}; \ // cd ${.CURDIR}/$${edir}; \ // else \ // ${ECHODIR} "===> ${DIRPRFX}$$entry"; \ // edir=$${entry}; \ // cd ${.CURDIR}/$${edir}; \ // fi; \ // ${MAKE} ${MAKEFLAGS} ${.TARGET:realinstall=install} DIRPRFX=${DIRPRFX}$$edir/); \ // done // // // The only change is adding ${MAKEFLAGS} to the ${MAKE} line so // that the -j3 flag carried down into the subdir's, so that make world // works with parellel make... // // Is there any reason that I'm overlooking why this *shouldn't* // be done this way? If not, and there are no arguments against it, I'd // like to make the change a permanent feature...? // Yes. If this worked you would create 3 copies of make for EACH subdirectory... Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-current Mon Apr 7 11:22:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA00199 for current-outgoing; Mon, 7 Apr 1997 11:22:29 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00193 for ; Mon, 7 Apr 1997 11:22:25 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id LAA18167; Mon, 7 Apr 1997 11:22:11 -0700 (PDT) Date: Mon, 7 Apr 1997 11:22:10 -0700 (PDT) From: Tom Bartol To: Brian Tao cc: FREEBSD-CURRENT-L Subject: Re: XFree86 3.2 causes constant 1.0 load average? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am running FreeBSD-3.0-970209-SNAP and AfterStep-1.0pre6 also and I too occasionally see this same thing (this morning, in fact). I have not been able to track it down. Anyone have a clue what commands I should execute to try to shed more light on the situation? Tom On Sun, 6 Apr 1997, Brian Tao wrote: > Has anyone else noticed that XFree86 3.2 will in many cases (but > not always) cause a 2.2 or 3.0 system to report a load average of at > least 1.0? ps/top both indicate little or no CPU activity, but the > load average does not fall below 1.0 unless I kill off X. > > I'm running AfterStep 1.0pre6 as the window manager, but the X > application mix can vary (with or without Netscape running, xterm > windows with very little update activity, etc.) What would cause > FreeBSD to report a load average of 1+ when there is no system load? > > > last pid: 13859; load averages: 1.31, 1.42, 1.45 12:09:25 > 50 processes: 1 running, 49 sleeping > CPU states: 0.4% user, 0.0% nice, 1.2% system, 0.0% interrupt, 98.5% idle > Mem: 33M Active, 3592K Inact, 15M Wired, 8280K Cache, 7644K Buf, 2364K Free > Swap: 128M Total, 24M Used, 104M Free, 19% Inuse > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 8121 root 2 0 7788K 16368K select 831:43 1.53% 1.53% XF86_Mach64 > 12566 taob 2 0 564K 1484K select 0:18 0.99% 0.99% xterm > 13859 taob 28 0 324K 828K RUN 0:00 0.46% 0.38% top > 8182 taob 2 0 3140K 2112K select 0:21 0.11% 0.11% screen-3.7.1 > 13857 taob 2 0 600K 964K select 0:00 0.12% 0.11% vim > > -- > Brian Tao (BT300, taob@risc.org) > "Though this be madness, yet there is method in't" > > From owner-freebsd-current Mon Apr 7 11:30:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA00632 for current-outgoing; Mon, 7 Apr 1997 11:30:16 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00611 for ; Mon, 7 Apr 1997 11:30:07 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id LAA03227; Mon, 7 Apr 1997 11:29:52 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org (FreeBSD Current Mailing List) Subject: Re: CVSUP and Release Question In-reply-to: Your message of "Mon, 07 Apr 1997 18:21:08 +0200." <19970407182108.RO31161@jette.heep.sax.de> Date: Mon, 07 Apr 1997 11:29:51 -0700 Message-ID: <3224.860437791@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As Jordan K. Hubbard wrote: > > > > I am using cvsup on tag=RELENG_2_2, but my build says 2.2-STABLE. > > > > Joerg jumped the gun on calling it -stable, but now I don't want > > to switch it back because there will end up being two sets of > > people with "2.2-STABLE" in their uname line - the pre-stables and > > the real-stables. :-) > > So, this was the intended effect. :-) Fine, so now you explain to all the current pre-stables that they're really pre-stable and not quite so safe as their uname(1) output would have them believe. :-) Jordan From owner-freebsd-current Mon Apr 7 12:02:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA02823 for current-outgoing; Mon, 7 Apr 1997 12:02:04 -0700 (PDT) Received: from haywire.DIALix.COM (news@haywire.dialix.com [192.203.228.65]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02815 for ; Mon, 7 Apr 1997 12:01:57 -0700 (PDT) Received: (from news@localhost) by haywire.DIALix.COM (8.8.4/8.8.2) id DAA17313 for freebsd-current@freebsd.org; Tue, 8 Apr 1997 03:01:51 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 7 Apr 1997 19:01:50 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <860439710.357888@haywire.DIALix.COM> Organization: DIALix Internet Services References: <199704030142.BAA04433@netfl15a.devetir.qld.gov.au> Subject: Re: POLL & the Single FreeBSD'r Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <19970403095026.AM16414@uriah.heep.sax.de>, j@uriah.heep.sax.de (J Wunsch) writes: > As Stephen Hocking wrote: > >> I note that NetBSD has had the poll system call for some time. Are >> there any plans to integrate one of the few nice SYSV'isms into >> FreeBSD (it would make porting some code a snap). > > At least, it hasn't been diminished to be a bad idea. I implemented an openbsd-style implementation of poll() some time ago but it was mixed up in the middle of the upages stuff so it lot left. Since then, NetBSD have done a much better implementation, I'm very tempted to back out what I've done and start from scratch while looking at the NetBSD method. Basically, OpenBSD implemented poll() as an alternative interface to the select hooks in the kernel which means that poll() is limited to what select() can test for. NetBSD did it a lot better, by replacing the select hooks by poll hooks, and updating both front-ends to use the new poll backend. The main difference is that under NetBSD, you can poll for (say) ugent data on a socket as opposed to merely "readable". > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Apr 7 13:51:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA11925 for current-outgoing; Mon, 7 Apr 1997 13:51:26 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11920 for ; Mon, 7 Apr 1997 13:51:22 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA11130; Mon, 7 Apr 1997 14:51:10 -0600 (MDT) Date: Mon, 7 Apr 1997 14:51:10 -0600 (MDT) Message-Id: <199704072051.OAA11130@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: peter@spinner.dialix.com (Peter Wemm) Cc: freebsd-current@freebsd.org Subject: Re: POLL & the Single FreeBSD'r In-Reply-To: <860439710.357888@haywire.DIALix.COM> References: <199704030142.BAA04433@netfl15a.devetir.qld.gov.au> <860439710.357888@haywire.DIALix.COM> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> I note that NetBSD has had the poll system call for some time. Are > >> there any plans to integrate one of the few nice SYSV'isms into > >> FreeBSD (it would make porting some code a snap). > > > > At least, it hasn't been diminished to be a bad idea. > > I implemented an openbsd-style implementation of poll() some time ago > but it was mixed up in the middle of the upages stuff so it lot left. > Since then, NetBSD have done a much better implementation, I'm very tempted > to back out what I've done and start from scratch while looking at the > NetBSD method. Jeffrey Hsu mentioned that having poll(2) would be a great boon to getting the JDK working in FreeBSD better, so if that encourages you in any way.... *grin* Nate From owner-freebsd-current Mon Apr 7 13:58:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA12463 for current-outgoing; Mon, 7 Apr 1997 13:58:08 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12445 for ; Mon, 7 Apr 1997 13:57:55 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02051; Mon, 7 Apr 1997 13:38:19 -0700 From: Terry Lambert Message-Id: <199704072038.NAA02051@phaeton.artisoft.com> Subject: Re: POLL & the Single FreeBSD'r To: peter@spinner.DIALix.COM (Peter Wemm) Date: Mon, 7 Apr 1997 13:38:19 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <860439710.357888@haywire.DIALix.COM> from "Peter Wemm" at Apr 7, 97 07:01:50 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I implemented an openbsd-style implementation of poll() some time ago > but it was mixed up in the middle of the upages stuff so it lot left. > Since then, NetBSD have done a much better implementation, I'm very tempted > to back out what I've done and start from scratch while looking at the > NetBSD method. Basically, OpenBSD implemented poll() as an alternative > interface to the select hooks in the kernel which means that poll() is > limited to what select() can test for. NetBSD did it a lot better, by > replacing the select hooks by poll hooks, and updating both front-ends to > use the new poll backend. The main difference is that under NetBSD, you > can poll for (say) ugent data on a socket as opposed to merely "readable". How does implementing select on top of poll hooks impact the ability to specify a 1uS valued timeval struct for the select timeout? Does it round to the 10ms granularity of poll, or does it work as expected (and as documented in the select() man page)? There is good reason why the select() call was located in the RT section of the SVID III definition when SystemV did poll()... 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 Apr 7 14:07:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA13139 for current-outgoing; Mon, 7 Apr 1997 14:07:05 -0700 (PDT) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13131 for ; Mon, 7 Apr 1997 14:07:01 -0700 (PDT) Received: from protocol.eng.umd.edu (protocol.eng.umd.edu [129.2.98.180]) by po2.glue.umd.edu (8.8.5/8.8.5) with ESMTP id RAA15500 for ; Mon, 7 Apr 1997 17:06:58 -0400 (EDT) Received: from localhost (chuckr@localhost) by protocol.eng.umd.edu (8.8.5/8.6.4) with SMTP id RAA15901 for ; Mon, 7 Apr 1997 17:06:57 -0400 (EDT) X-Authentication-Warning: protocol.eng.umd.edu: chuckr owned process doing -bs Date: Mon, 7 Apr 1997 17:06:56 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@protocol.eng.umd.edu To: FreeBSD current Subject: make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You know, there are several things installed by a make world that I *really* wish I could condition out via a make veriable: perl : I want to maintain my version at 5.003, not 4.036 groff : I want groff install to stop overwriting the /usr/share/groff_font/devlp/download file, so all those neat fonts I bought from WC stay installed. tcl : I want my version at 8.0a3, not the _old_ 7.5 There are others, probably, but these come immediately to mind. Others might not want them because of all the "bloat" complaints (I'm *not* complaining about bloat). I'd accept personal responsiblity at my site for maintaining the choked off parts. Would it be possible to add a variable to the make files so that some of this stuff would be ignored on build and install? Well, I know it's logically possible, I mean politically possible or desireable? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Mon Apr 7 14:28:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA14307 for current-outgoing; Mon, 7 Apr 1997 14:28:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA14299 for ; Mon, 7 Apr 1997 14:28:05 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA02169 for current@freebsd.org; Mon, 7 Apr 1997 14:09:47 -0700 From: Terry Lambert Message-Id: <199704072109.OAA02169@phaeton.artisoft.com> Subject: Humorous memory leak To: current@freebsd.org Date: Mon, 7 Apr 1997 14:09:47 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There is a humorous memory leak in kern/kern_exec.c in execve(). The path name buffer in the "exec_fail_dealloc:" case should be unconditionally freed, not conditionally freed based on a valid ndp->ni_vp. The reason is that if the namei() succeeded with the "SAVENAME" flag set, then a path buffer is allocated independently of whether the ndp->ni_vp value is valid. Actually, I can't see why the test is really necessary at all; the fail-through should be to "exec_fail:" in any case that could result in a NULL ndp->ni_vp, right? Anyway, it's funny. 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 Apr 7 14:39:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA15125 for current-outgoing; Mon, 7 Apr 1997 14:39:22 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.dialix.com [192.203.228.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15114 for ; Mon, 7 Apr 1997 14:39:13 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.5/8.8.5) with ESMTP id FAA03511; Tue, 8 Apr 1997 05:37:40 +0800 (WST) Message-Id: <199704072137.FAA03511@spinner.DIALix.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: POLL & the Single FreeBSD'r In-reply-to: Your message of "Mon, 07 Apr 1997 13:38:19 MST." <199704072038.NAA02051@phaeton.artisoft.com> Date: Tue, 08 Apr 1997 05:37:40 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > I implemented an openbsd-style implementation of poll() some time ago > > but it was mixed up in the middle of the upages stuff so it lot left. > > Since then, NetBSD have done a much better implementation, I'm very tempted > > to back out what I've done and start from scratch while looking at the > > NetBSD method. Basically, OpenBSD implemented poll() as an alternative > > interface to the select hooks in the kernel which means that poll() is > > limited to what select() can test for. NetBSD did it a lot better, by > > replacing the select hooks by poll hooks, and updating both front-ends to > > use the new poll backend. The main difference is that under NetBSD, you > > can poll for (say) ugent data on a socket as opposed to merely "readable". > > How does implementing select on top of poll hooks impact the ability > to specify a 1uS valued timeval struct for the select timeout? Does > it round to the 10ms granularity of poll, or does it work as expected > (and as documented in the select() man page)? It's got nothing to do with that. What I'm talking about is that the select functions in the device/file ops etc switch tables have a select backend that tests for FREAD, FWRITE or 0 (== exception). If you implement poll() over the top of that backend, you can't emulate the priority band stuff (urgent data). if, on the other hand, the backends are updated to scan for poll type events (read, write, urgent readable data, hangup, etc), you can implement poll() fully (and unambigiously), without hurting or penalising the select top end. Besides, all the timeout stuff is done in the top level code, select() or poll() in sys_generic. The fact that both call pollscan() or selscan() is irrelevant, because the scan routines are instant and do not sleep or timeout. The timeout is all up to the individual syscall handler. What you want is a high-resolution timer/sleep/schedule system, which we don't have, and nobody has offered to implement yet, so it's pretty unlikely that we'll see it in the near future. (This doesn't mean that it cannot be done, just that nobody has wanted it badly enough to do it. Messing with timers and a more precise sleep queue that can deal with the next event in microseconds for the timer programming might be enough, especially when combined with the RT schedule options) Incidently, the way the man page that you mention is written, it says the timeout is "the maximum amount of time to wait". It seems to me that rounding down to the nearest 10ms would make us more compliant with the man page, even though we can't control scheduling to guarantee an immediate wakeup. "waiting for the select event" != "waiting for process reschedule". So, if we ask for a 1us timeout, we'd be perfectly compliant with the man page to return immediately. In fact, we'd be compliant with the man page if we returned immediately no matter how long was asked for (0 seconds is not more than the maximum interval to wait for the selection to complete) - this goes to show that what is documented in the man pages isn't always good or useful. > Regards, > Terry Lambert > terry@lambert.org Cheers, -Peter From owner-freebsd-current Mon Apr 7 14:39:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA15192 for current-outgoing; Mon, 7 Apr 1997 14:39:46 -0700 (PDT) Received: from thor.inlink.com (ultra.inlink.com [206.196.96.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15180 for ; Mon, 7 Apr 1997 14:39:42 -0700 (PDT) Received: from mail.global-sol.com (global-sol.com [206.196.126.221]) by thor.inlink.com (8.8.0/V8) with ESMTP id QAA21304 for ; Mon, 7 Apr 1997 16:39:36 -0500 (CDT) Received: from mis ([206.196.126.208]) by mail.global-sol.com (8.7.5/8.7.3) with SMTP id QAA06207; Mon, 7 Apr 1997 16:47:38 GMT Message-ID: <33496990.3C58@midwestis.com> Date: Mon, 07 Apr 1997 16:39:28 -0500 From: "Timothy P. Layton, Sr." Organization: Midwest Information Systems X-Mailer: Mozilla 3.01 (X11; I; SunOS 5.5.1 i86pc) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-current Mon Apr 7 14:44:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA15492 for current-outgoing; Mon, 7 Apr 1997 14:44:41 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA15483 for ; Mon, 7 Apr 1997 14:44:38 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA25896; Mon, 7 Apr 1997 14:44:26 -0700 Date: Mon, 7 Apr 1997 14:44:25 -0700 (PDT) From: "Brian N. Handy" To: Chuck Robey Cc: FreeBSD current Subject: Re: make world In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >perl : I want to maintain my version at 5.003, not 4.036 >groff : I want groff install to stop overwriting the > /usr/share/groff_font/devlp/download file, so all > those neat fonts I bought from WC stay installed. >tcl : I want my version at 8.0a3, not the _old_ 7.5 I sorta like to be able to track the bleeding edge myself, and I seem to have a stockpile of stuff that wants perl5 that I have to be real careful with. I'd like this option as well. The grudging question is how many things break when you do this (at least with Perl and tcl)? Making it a makefile option is kinda nice in that the only people who'll do it are (maybe) proficient enough to deal with the breakages. (I say "maybe" since I'm not yet sure I could. :-) Happy trails, Brian From owner-freebsd-current Mon Apr 7 14:47:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA15702 for current-outgoing; Mon, 7 Apr 1997 14:47:46 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15696 for ; Mon, 7 Apr 1997 14:47:43 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA11559; Mon, 7 Apr 1997 15:47:31 -0600 (MDT) Date: Mon, 7 Apr 1997 15:47:31 -0600 (MDT) Message-Id: <199704072147.PAA11559@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: FreeBSD current Subject: Re: make world In-Reply-To: References: X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You know, there are several things installed by a make world that I > *really* wish I could condition out via a make veriable: Then copy gnu/usr.bin/Makefile to gnu/usr.bin/makefile, and comment them out. :) There is such a thing as being 'too flexible', because it introduces too much complexity for those that don't understand the system. Nate From owner-freebsd-current Mon Apr 7 15:01:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA16419 for current-outgoing; Mon, 7 Apr 1997 15:01:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA16411 for ; Mon, 7 Apr 1997 15:00:57 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA02263; Mon, 7 Apr 1997 14:41:59 -0700 From: Terry Lambert Message-Id: <199704072141.OAA02263@phaeton.artisoft.com> Subject: Re: POLL & the Single FreeBSD'r To: peter@spinner.DIALix.COM (Peter Wemm) Date: Mon, 7 Apr 1997 14:41:58 -0700 (MST) Cc: terry@lambert.org, freebsd-current@freebsd.org In-Reply-To: <199704072137.FAA03511@spinner.DIALix.COM> from "Peter Wemm" at Apr 8, 97 05:37:40 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > How does implementing select on top of poll hooks impact the ability > > to specify a 1uS valued timeval struct for the select timeout? Does > > it round to the 10ms granularity of poll, or does it work as expected > > (and as documented in the select() man page)? > > It's got nothing to do with that. What I'm talking about is that the > select functions in the device/file ops etc switch tables have a select > backend that tests for FREAD, FWRITE or 0 (== exception). If you implement > poll() over the top of that backend, you can't emulate the priority band > stuff (urgent data). if, on the other hand, the backends are updated to > scan for poll type events (read, write, urgent readable data, hangup, etc), > you can implement poll() fully (and unambigiously), without hurting or > penalising the select top end. Besides, all the timeout stuff is done in > the top level code, select() or poll() in sys_generic. The fact that both > call pollscan() or selscan() is irrelevant, because the scan routines are > instant and do not sleep or timeout. The timeout is all up to the individual > syscall handler. OK. That's cool, then. It's a good idea. > What you want is a high-resolution timer/sleep/schedule system, which we > don't have, and nobody has offered to implement yet, so it's pretty > unlikely that we'll see it in the near future. (This doesn't mean that it > cannot be done, just that nobody has wanted it badly enough to do it. > Messing with timers and a more precise sleep queue that can deal with the > next event in microseconds for the timer programming might be enough, > especially when combined with the RT schedule options) Yes; kernel preemtion on timer events before process quantum expiration is probably 90% of the way to real RT support... I don't necessarily want something with high-resoloution timing right now, but the select() code *will* operate sub-quantum if there's nothing else in the run queue without "real" high resoloution support. SunOS 4.x has historically worked that way (down to 4uS on a select/timeout buzz loop on a SPARCStation 1+, actually... better on faster hardware). I also don't want to preclude it (or require a rewrite) at some later time when someone goes to support it. > Incidently, the way the man page that you mention is written, it says the > timeout is "the maximum amount of time to wait". It seems to me that > rounding down to the nearest 10ms would make us more compliant with the man > page, even though we can't control scheduling to guarantee an immediate > wakeup. "waiting for the select event" != "waiting for process > reschedule". So, if we ask for a 1us timeout, we'd be perfectly compliant > with the man page to return immediately. In fact, we'd be compliant with > the man page if we returned immediately no matter how long was asked for > (0 seconds is not more than the maximum interval to wait for the selection > to complete) - this goes to show that what is documented in the man pages > isn't always good or useful. Well, I'd prefer that the internal granularity be 1uS, and if the scheduler can't keep up, then it can't keep up (the part of the man page I was referrung to was the tv_usec reference). You fire when you can, and you schedule as soon as you can without stealing someone else's quantum (unless you have RT scheduling, and the process is marked RT). For an unloaded system, that's still yas better than 10ms, though how much better is hardware dependent (as it should be). I could argue about SVID III compliance with "system clock frequency" instead of "system clock update frequency" as distinguished in SVID III by setitimer(RT) and gettimeofday(RT). At the very least, it's required for ABI compatability with Solaris 2.5 and above, even if the BSD select() call stays a slug. 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 Apr 7 15:05:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA16767 for current-outgoing; Mon, 7 Apr 1997 15:05:56 -0700 (PDT) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16754 for ; Mon, 7 Apr 1997 15:05:52 -0700 (PDT) Received: from protocol.eng.umd.edu (protocol.eng.umd.edu [129.2.98.180]) by po2.glue.umd.edu (8.8.5/8.8.5) with ESMTP id SAA17604; Mon, 7 Apr 1997 18:05:49 -0400 (EDT) Received: from localhost (chuckr@localhost) by protocol.eng.umd.edu (8.8.5/8.6.4) with SMTP id SAA15969; Mon, 7 Apr 1997 18:05:49 -0400 (EDT) X-Authentication-Warning: protocol.eng.umd.edu: chuckr owned process doing -bs Date: Mon, 7 Apr 1997 18:05:49 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@protocol.eng.umd.edu To: Nate Williams cc: FreeBSD current Subject: Re: make world In-Reply-To: <199704072147.PAA11559@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Apr 1997, Nate Williams wrote: > > You know, there are several things installed by a make world that I > > *really* wish I could condition out via a make veriable: > > Then copy gnu/usr.bin/Makefile to gnu/usr.bin/makefile, and comment > them out. :) > > There is such a thing as being 'too flexible', because it introduces > too much complexity for those that don't understand the system. Well, that takes care of one of three, but that gets undone next time I do a cvs update. It doesn't seem like a viable longterm alternative. Making the changes I want wouldn't break anything else in the make world, because I want more up to date versions (or to stop changing certain files). > > > > Nate > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Mon Apr 7 15:12:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA17274 for current-outgoing; Mon, 7 Apr 1997 15:12:57 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17261 for ; Mon, 7 Apr 1997 15:12:52 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA11718; Mon, 7 Apr 1997 16:12:46 -0600 (MDT) Date: Mon, 7 Apr 1997 16:12:46 -0600 (MDT) Message-Id: <199704072212.QAA11718@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: Nate Williams , FreeBSD current Subject: Re: make world In-Reply-To: References: <199704072147.PAA11559@rocky.mt.sri.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > You know, there are several things installed by a make world that I > > > *really* wish I could condition out via a make veriable: > > > > Then copy gnu/usr.bin/Makefile to gnu/usr.bin/makefile, and comment > > them out. :) > > > > There is such a thing as being 'too flexible', because it introduces > > too much complexity for those that don't understand the system. > > Well, that takes care of one of three, but that gets undone next time I do > a cvs update. Uhh, nope. CVS won't touch files that have never been in the system, like 'makefile'. I tdo this all the time on my laptop which doesn't have space for the big packages, so I delete them and build a 'makefile' with them gone. CVS update creates the directories anew, but my CVS update script deletes them again as soon as the update completes. The only time this fails is when new directories are in place, but any 'customized' system needs some modifications to stay current. Nate From owner-freebsd-current Mon Apr 7 15:15:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA17486 for current-outgoing; Mon, 7 Apr 1997 15:15:49 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17475 for ; Mon, 7 Apr 1997 15:15:47 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA04188; Mon, 7 Apr 1997 15:15:40 -0700 (PDT) To: Chuck Robey cc: FreeBSD current Subject: Re: make world In-reply-to: Your message of "Mon, 07 Apr 1997 17:06:56 EDT." Date: Mon, 07 Apr 1997 15:15:40 -0700 Message-ID: <4185.860451340@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Would it be possible to add a variable to the make files so that some of > this stuff would be ignored on build and install? Well, I know it's > logically possible, I mean politically possible or desireable? Neither. :-) Jordan From owner-freebsd-current Mon Apr 7 15:16:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA17611 for current-outgoing; Mon, 7 Apr 1997 15:16:52 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.dialix.com [192.203.228.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17605 for ; Mon, 7 Apr 1997 15:16:46 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.5/8.8.5) with ESMTP id GAA03730; Tue, 8 Apr 1997 06:15:09 +0800 (WST) Message-Id: <199704072215.GAA03730@spinner.DIALix.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: POLL & the Single FreeBSD'r In-reply-to: Your message of "Mon, 07 Apr 1997 14:41:58 MST." <199704072141.OAA02263@phaeton.artisoft.com> Date: Tue, 08 Apr 1997 06:15:09 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > What you want is a high-resolution timer/sleep/schedule system, which we > > don't have, and nobody has offered to implement yet, so it's pretty > > unlikely that we'll see it in the near future. (This doesn't mean that it > > cannot be done, just that nobody has wanted it badly enough to do it. > > Messing with timers and a more precise sleep queue that can deal with the > > next event in microseconds for the timer programming might be enough, > > especially when combined with the RT schedule options) > > Yes; kernel preemtion on timer events before process quantum expiration > is probably 90% of the way to real RT support... > > I don't necessarily want something with high-resoloution timing right > now, but the select() code *will* operate sub-quantum if there's nothing > else in the run queue without "real" high resoloution support. SunOS 4.x > has historically worked that way (down to 4uS on a select/timeout buzz > loop on a SPARCStation 1+, actually... better on faster hardware). Hmm.. this is an interesting suggestion.. I think we can do the same with some careful use of microtime() and mi_switch().. > scheduler can't keep up, then it can't keep up (the part of the man > page I was referrung to was the tv_usec reference). peter@spinner[6:07am]~src/sys/kern-132> man select | col -b | grep tv_ peter@spinner[6:11am]~src/sys/kern-133> What tv_usec reference? Are you on the wrong system? :-) Our 4.4BSD derived man page only says the word "timeout" and mentions nothing about tv_* at all > Regards, > Terry Lambert > terry@lambert.org Cheers, -Peter From owner-freebsd-current Mon Apr 7 15:21:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA17917 for current-outgoing; Mon, 7 Apr 1997 15:21:25 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17908 for ; Mon, 7 Apr 1997 15:21:21 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA04293; Mon, 7 Apr 1997 15:21:09 -0700 (PDT) To: "Brian N. Handy" cc: Chuck Robey , FreeBSD current Subject: Re: make world In-reply-to: Your message of "Mon, 07 Apr 1997 14:44:25 PDT." Date: Mon, 07 Apr 1997 15:21:09 -0700 Message-ID: <4290.860451669@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I sorta like to be able to track the bleeding edge myself, and I seem to > have a stockpile of stuff that wants perl5 that I have to be real careful > with. I'd like this option as well. jkh shouts "/usr/local! /usr/local!" until he goes hoarse. :) Jordan From owner-freebsd-current Mon Apr 7 15:45:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA19539 for current-outgoing; Mon, 7 Apr 1997 15:45:00 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA19532 for ; Mon, 7 Apr 1997 15:44:56 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02421; Mon, 7 Apr 1997 15:26:04 -0700 From: Terry Lambert Message-Id: <199704072226.PAA02421@phaeton.artisoft.com> Subject: Re: POLL & the Single FreeBSD'r To: peter@spinner.DIALix.COM (Peter Wemm) Date: Mon, 7 Apr 1997 15:26:04 -0700 (MST) Cc: terry@lambert.org, freebsd-current@freebsd.org In-Reply-To: <199704072215.GAA03730@spinner.DIALix.COM> from "Peter Wemm" at Apr 8, 97 06:15:09 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > scheduler can't keep up, then it can't keep up (the part of the man > > page I was referrung to was the tv_usec reference). > > peter@spinner[6:07am]~src/sys/kern-132> man select | col -b | grep tv_ > peter@spinner[6:11am]~src/sys/kern-133> > What tv_usec reference? Are you on the wrong system? :-) > > Our 4.4BSD derived man page only says the word "timeout" and mentions nothing > about tv_* at all | If timeout is a non-nil pointer, it specifies a maximum interval | to wait for the selection to complete. And timeout specified a struct timeval. It draws a distinction between a "minimally non-zero valued" and a "zero valued" timeval as well: | To affect a poll, the timeout argument should be non-nil, | pointing to a zero-valued timeval structure. (This last is implicit, but no less real for it). Yeah, I'm picking nits, but you have to admit that those nits result in useful behaviours under most circumstances. For instance, a 200uS timeout for a select on an X fd is sufficient for ~30FPS cell animation, while still returning unused process time to the system instead of buzz-looping (I know, I know: now I have self-identified as "one of those graphics geeks"... 8-)). Mostly, I've found the SunOS 4.x behaviour useful in the past, and would like to see that code runable on FreeBSD without a round up by a factor of 50 in the inter-event delay. 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 Apr 7 15:58:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA20414 for current-outgoing; Mon, 7 Apr 1997 15:58:50 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA20406 for ; Mon, 7 Apr 1997 15:58:44 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02494; Mon, 7 Apr 1997 15:39:13 -0700 From: Terry Lambert Message-Id: <199704072239.PAA02494@phaeton.artisoft.com> Subject: Re: make world To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 7 Apr 1997 15:39:13 -0700 (MST) Cc: chuckr@glue.umd.edu, freebsd-current@freefall.freebsd.org In-Reply-To: <4185.860451340@time.cdrom.com> from "Jordan K. Hubbard" at Apr 7, 97 03:15:40 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Would it be possible to add a variable to the make files so that some of > > this stuff would be ignored on build and install? Well, I know it's > > logically possible, I mean politically possible or desireable? > > Neither. :-) Would it be possible to make the date stamp dependencies work? New code is newer than old code, last time I looked... 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 Apr 7 16:18:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA22423 for current-outgoing; Mon, 7 Apr 1997 16:18:40 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22417 for ; Mon, 7 Apr 1997 16:18:35 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id QAA05811; Mon, 7 Apr 1997 16:18:14 -0700 (PDT) Message-Id: <199704072318.QAA05811@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: current@freebsd.org Subject: Re: Humorous memory leak In-reply-to: Your message of "Mon, 07 Apr 1997 14:09:47 PDT." <199704072109.OAA02169@phaeton.artisoft.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Apr 1997 16:18:14 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >There is a humorous memory leak in kern/kern_exec.c in execve(). > >The path name buffer in the "exec_fail_dealloc:" case should be >unconditionally freed, not conditionally freed based on a valid >ndp->ni_vp. > >The reason is that if the namei() succeeded with the "SAVENAME" flag >set, then a path buffer is allocated independently of whether the >ndp->ni_vp value is valid. > >Actually, I can't see why the test is really necessary at all; the >fail-through should be to "exec_fail:" in any case that could result >in a NULL ndp->ni_vp, right? It's completely harmless. It was added while trying to fix some other problems, but after looking more carefully at the what the logic had mutated into, it wasn't strictly necessary. It does not, however, result in a memory leak; ni_vp will always be valid at that point (else the machine would have already paniced by derefencing a bad pointer). >Anyway, it's funny. You have a strange sense of humor. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Apr 7 16:27:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA23785 for current-outgoing; Mon, 7 Apr 1997 16:27:56 -0700 (PDT) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA23772 for ; Mon, 7 Apr 1997 16:27:52 -0700 (PDT) Received: from protocol.eng.umd.edu (protocol.eng.umd.edu [129.2.98.180]) by po2.glue.umd.edu (8.8.5/8.8.5) with ESMTP id TAA19772; Mon, 7 Apr 1997 19:27:49 -0400 (EDT) Received: from localhost (chuckr@localhost) by protocol.eng.umd.edu (8.8.5/8.6.4) with SMTP id TAA16009; Mon, 7 Apr 1997 19:27:48 -0400 (EDT) X-Authentication-Warning: protocol.eng.umd.edu: chuckr owned process doing -bs Date: Mon, 7 Apr 1997 19:27:48 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@protocol.eng.umd.edu To: Nate Williams cc: FreeBSD current Subject: Re: make world In-Reply-To: <199704072212.QAA11718@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Apr 1997, Nate Williams wrote: > > > > You know, there are several things installed by a make world that I > > > > *really* wish I could condition out via a make veriable: > > > > > > Then copy gnu/usr.bin/Makefile to gnu/usr.bin/makefile, and comment > > > them out. :) > > > > > > There is such a thing as being 'too flexible', because it introduces > > > too much complexity for those that don't understand the system. > > > > Well, that takes care of one of three, but that gets undone next time I do > > a cvs update. > > Uhh, nope. CVS won't touch files that have never been in the system, > like 'makefile'. I tdo this all the time on my laptop which doesn't > have space for the big packages, so I delete them and build a > 'makefile' with them gone. CVS update creates the directories anew, > but my CVS update script deletes them again as soon as the update > completes. > > The only time this fails is when new directories are in place, but > any 'customized' system needs some modifications to stay current. Ah, I see, if there's a "makefile", then "Makefile" isn't even read. I didn't understand what you were aiming at. Great, this'll do just what I want! Thanks, Nate. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Mon Apr 7 16:30:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA24456 for current-outgoing; Mon, 7 Apr 1997 16:30:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA24439 for ; Mon, 7 Apr 1997 16:30:06 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA02593; Mon, 7 Apr 1997 16:11:16 -0700 From: Terry Lambert Message-Id: <199704072311.QAA02593@phaeton.artisoft.com> Subject: Re: Humorous memory leak To: dg@root.com Date: Mon, 7 Apr 1997 16:11:16 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <199704072318.QAA05811@root.com> from "David Greenman" at Apr 7, 97 04:18:14 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Anyway, it's funny. > > You have a strange sense of humor. Now that's the first time I've ever heard that... ;-) 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 Apr 7 16:32:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA24807 for current-outgoing; Mon, 7 Apr 1997 16:32:57 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA24790 for ; Mon, 7 Apr 1997 16:32:51 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA12042; Mon, 7 Apr 1997 17:32:20 -0600 (MDT) Date: Mon, 7 Apr 1997 17:32:20 -0600 (MDT) Message-Id: <199704072332.RAA12042@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: Nate Williams , FreeBSD current Subject: Re: make world In-Reply-To: References: <199704072212.QAA11718@rocky.mt.sri.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ah, I see, if there's a "makefile", then "Makefile" isn't even read. You got it. 'makefile' is preferred to 'Makefile' by every 'make' program I've used, which is something I count on when doing development. Nate From owner-freebsd-current Mon Apr 7 16:35:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA25227 for current-outgoing; Mon, 7 Apr 1997 16:35:51 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25213 for ; Mon, 7 Apr 1997 16:35:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id QAA05907; Mon, 7 Apr 1997 16:35:01 -0700 (PDT) Message-Id: <199704072335.QAA05907@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: current@freebsd.org Subject: Re: Humorous memory leak In-reply-to: Your message of "Mon, 07 Apr 1997 16:11:16 PDT." <199704072311.QAA02593@phaeton.artisoft.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Apr 1997 16:35:01 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >Anyway, it's funny. >> >> You have a strange sense of humor. > >Now that's the first time I've ever heard that... ;-) Oh, and I forgot to mention why I didn't revert the change... it's the same reason why the exit code is duplicated almost identically there for the success and failure cases: I was planning to combine both exit points into a single exit (which should make YOU happy), but more important things keep getting in the way...so it sits on my mental todo list. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Apr 7 16:58:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA27025 for current-outgoing; Mon, 7 Apr 1997 16:58:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA27017 for ; Mon, 7 Apr 1997 16:58:27 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA04288; Mon, 7 Apr 1997 16:39:36 -0700 From: Terry Lambert Message-Id: <199704072339.QAA04288@phaeton.artisoft.com> Subject: Re: Humorous memory leak To: dg@root.com Date: Mon, 7 Apr 1997 16:39:35 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <199704072335.QAA05907@root.com> from "David Greenman" at Apr 7, 97 04:35:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Oh, and I forgot to mention why I didn't revert the change... it's the > same reason why the exit code is duplicated almost identically there for the > success and failure cases: I was planning to combine both exit points into a > single exit (which should make YOU happy), As a clam... 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 Apr 7 17:10:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA27639 for current-outgoing; Mon, 7 Apr 1997 17:10:57 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA27634 for ; Mon, 7 Apr 1997 17:10:54 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA12168; Tue, 8 Apr 1997 09:40:26 +0930 (CST) From: Michael Smith Message-Id: <199704080010.JAA12168@genesis.atrad.adelaide.edu.au> Subject: Re: make world In-Reply-To: from Chuck Robey at "Apr 7, 97 05:06:56 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Tue, 8 Apr 1997 09:40:25 +0930 (CST) Cc: freebsd-current@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey stands accused of saying: > You know, there are several things installed by a make world that I > *really* wish I could condition out via a make veriable: ... > Would it be possible to add a variable to the make files so that some of > this stuff would be ignored on build and install? Well, I know it's > logically possible, I mean politically possible or desireable? I put forward a scheme using some slight mods to bsd.subdir.mk and subdirectory Makefiles, but I was ignored. Perhaps I should have taken that as a "yes, go ahead"? This was tied in with the perl5 discussions. Hey Perl people, I thought the "stable" perl5 was due out RSN. What happened? Atari take over Perl development? > Chuck Robey | Interests include any kind of voice or data -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Mon Apr 7 18:39:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA07888 for current-outgoing; Mon, 7 Apr 1997 18:39:09 -0700 (PDT) Received: from isf.kiev.ua (sunone.isf.kiev.ua [194.44.162.131]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA07879 for ; Mon, 7 Apr 1997 18:38:47 -0700 (PDT) Received: from olinet.isf.kiev.ua by isf.kiev.ua with ESMTP id EAA07181; (8.8.3/2.b1) Tue, 8 Apr 1997 04:31:43 +0300 (EET DST) Received: from myname.my.domain by olinet.isf.kiev.ua with SMTP id EAA07999; (8.8.3/vak/1.9) Tue, 8 Apr 1997 04:22:47 +0300 (EET DST) Message-ID: <33499F02.167EB0E7@olinet.isf.kiev.ua> Date: Tue, 08 Apr 1997 01:27:30 +0000 From: Vladimir Kushnir X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-current Mon Apr 7 19:18:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA09888 for current-outgoing; Mon, 7 Apr 1997 19:18:48 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09883 for ; Mon, 7 Apr 1997 19:18:45 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id TAA02843 for ; Mon, 7 Apr 1997 19:18:44 -0700 (PDT) Message-Id: <199704080218.TAA02843@austin.polstra.com> To: current@freebsd.org Subject: Kernel builders: update your assemblers Date: Mon, 07 Apr 1997 19:18:44 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Later this week, I am going to commit some kernel changes that will rely on your having an up-to-date version of "as" installed. If you do "make world" or something equivalent, this will be taken care of automatically. But if you occasionally update just your kernel, you'll need to make sure that you've installed the latest version of the assembler (src/gnu/usr.bin/as). I committed the assembler mods on March 29th, so if you've updated it since then, you're all set. Don't say I didn't warn you ... John -- 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 Apr 7 19:49:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA11124 for current-outgoing; Mon, 7 Apr 1997 19:49:01 -0700 (PDT) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA11118 for ; Mon, 7 Apr 1997 19:48:53 -0700 (PDT) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id VAA17082; Mon, 7 Apr 1997 21:57:55 -0500 (CDT) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id VAA13412; Mon, 7 Apr 1997 21:50:01 -0500 Message-ID: <19970407215000.10561@right.PCS> Date: Mon, 7 Apr 1997 21:50:00 -0500 From: Jonathan Lemon To: Michael Smith Cc: Chuck Robey , freebsd-current@freefall.freebsd.org Subject: Re: make world References: <199704080010.JAA12168@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199704080010.JAA12168@genesis.atrad.adelaide.edu.au>; from Michael Smith on Apr 04, 1997 at 09:40:25AM +0930 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Apr 04, 1997 at 09:40:25AM +0930, Michael Smith wrote: > > This was tied in with the perl5 discussions. Hey Perl people, I > thought the "stable" perl5 was due out RSN. What happened? Atari > take over Perl development? No, the release appears to have gone into an infinite loop with Chip "Just One More Patch-Bugfix-Enhancment-Change" Salzenberg. We can't seem to turn him off. (Hmm, wasn't there a similar problem with rolling 2.1.1-R?) -- Jonathan From owner-freebsd-current Mon Apr 7 20:22:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA12212 for current-outgoing; Mon, 7 Apr 1997 20:22:30 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA12204 for ; Mon, 7 Apr 1997 20:22:21 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wERTf-0001Yp-00; Mon, 7 Apr 1997 21:21:47 -0600 To: Nate Williams Subject: Re: make world Cc: Chuck Robey , FreeBSD current In-reply-to: Your message of "Mon, 07 Apr 1997 17:32:20 MDT." <199704072332.RAA12042@rocky.mt.sri.com> References: <199704072332.RAA12042@rocky.mt.sri.com> <199704072212.QAA11718@rocky.mt.sri.com> Date: Mon, 07 Apr 1997 21:21:47 -0600 From: Warner Losh Message-Id: Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199704072332.RAA12042@rocky.mt.sri.com> Nate Williams writes: : You got it. 'makefile' is preferred to 'Makefile' by every 'make' : program I've used, which is something I count on when doing : development. It is even documented to behave this way on most of them :-) Warner From owner-freebsd-current Mon Apr 7 21:24:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA15027 for current-outgoing; Mon, 7 Apr 1997 21:24:28 -0700 (PDT) Received: from peeper.jackson.org ([208.128.8.180]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA15019 for ; Mon, 7 Apr 1997 21:24:18 -0700 (PDT) Received: (from tom@localhost) by peeper.jackson.org (8.8.5/8.7.3) id XAA01332; Mon, 7 Apr 1997 23:03:55 -0500 (CDT) Message-ID: <19970407230355.64426@peeper.jackson.org> Date: Mon, 7 Apr 1997 23:03:55 -0500 From: Tom Jackson To: freebsd-current@freebsd.org References: <32FB6E57.7A4B@mwc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <32FB6E57.7A4B@mwc.net>; from Braden Marr on Fri, Feb 07, 1997 at 10:03:03AM -0800 Reply-To: toj@gorilla.net Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, Feb 07, 1997 at 10:03:03AM -0800, Braden Marr wrote: > unsubscribe Could *not* unsubscribe because your date is out of range!! CORRECT -- Tom Jackson I'm ProChoice->FreeBSD toj@gorilla.net http://www.freebsd.org tjackson@tulsix.utulsa.edu "Out in the Ozone Again" From owner-freebsd-current Mon Apr 7 23:20:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA19257 for current-outgoing; Mon, 7 Apr 1997 23:20:28 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA19252 for ; Mon, 7 Apr 1997 23:20:25 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA13668; Mon, 7 Apr 1997 23:20:24 -0700 (PDT) To: toj@gorilla.net cc: freebsd-current@freebsd.org In-reply-to: Your message of "Mon, 07 Apr 1997 23:03:55 CDT." <19970407230355.64426@peeper.jackson.org> Date: Mon, 07 Apr 1997 23:20:23 -0700 Message-ID: <13664.860480423@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Fri, Feb 07, 1997 at 10:03:03AM -0800, Braden Marr wrote: > > unsubscribe > > Could *not* unsubscribe because your date is out of range!! CORRECT :) Actually, I just use the following boilerplate reply. Others are free to copy it and use it for the same purpose: --------- If you're receiving this message, it's because you recently sent an "unsubscribe" request to one of the lists, perhaps thinking that you were reaching an automated system instead of the multiple-thousands of people who are now seeing your "unsubscribe" in their mailboxes and thinking "Geeze, what a complete idiot!" Perhaps some of them are even now sending you email telling you this in more detail. :-) This message attempts to clear some of that up for you so you don't make the same mistake again. First off, just about all mailing lists on the internet support the -request naming standard, meaning that if the mailing list you wish to get off of (or make some comment to the administrators about) is named "taco-lovers" then the administrative alias will be called "taco-lovers-request". You do NOT send your messages to taco-lovers, since that's only going to get to the fans of that most tasty mexican dish, not the person (or program) who actually maintains the list and can do something about your request. Second, for those who plead ignorance of all this, let me just point out that you *were* sent a welcome message when you joined the FreeBSD mailing lists telling you to send ALL administrative requests to majordomo@freebsd.org (the *-request aliases for our lists just point to this one). Our mailing list software is fully automated, and it's up to the users to add and remove themselves as they see fit - no FreeBSD personnel are involved in this! If you just threw this welcome message away and didn't read it, you have only yourself to blame for the flames which may now be filling your mailbox. If you have tried repeatedly with majordomo to remove yourself and it's not working, you still don't want to send a message to the list since the users can't help you - send mail in such cases to postmaster@freebsd.org and the FreeBSD postmaster will manually intervene to figure out why you're having problems with majordomo (and try majordomo FIRST! Our postmaster is very overworked!). Thank you! Jordan From owner-freebsd-current Tue Apr 8 03:31:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA29773 for current-outgoing; Tue, 8 Apr 1997 03:31:45 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA29751; Tue, 8 Apr 1997 03:31:36 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id KAA10828; Tue, 8 Apr 1997 10:30:00 GMT Date: Tue, 8 Apr 1997 19:29:59 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Terry Lambert cc: current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: DISCUSS: vnode references as open instances In-Reply-To: <199704032343.QAA17773@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry, I think it will be hard to get support to change ufs this drastically at this time since Kirk is working on soft updates. And there is also quite of a bit of community interest in having a trusted stable fs implementation to fall back on. How you considered what Netcom? did with tfs? It seems they use their own vnode allocation scheme. I vaguely remember seeing changes made to allow this. If you wanted to make even more radical changes Heidemann's papers discuss using a compatibility layer between the consumer of the old interface and a new framework. This would give you more leeway for big changes like reimplementing ufs without the outdated cylinder group layout stuff, etc. I know it's easier said then done and there might be some restrictions, but I think you would get more support with this strategy. Regards, Mike Hancock On Thu, 3 Apr 1997, Terry Lambert wrote: > I am looking for discussion, pro and con. > > ----------------------------------------------------------------------------- > > I believe that vnode references should be treated as counting > semaphores. > > Currently, reference holders are net required to count references > in all cases. > > The purpose of this change would be to significantly clean up > the vnode reference interactions to provide a meaningful > seperation between vnode maintenance and vnode reclamation, > with the eventual intention of removing the need for vclean() > and the duplication of code in each per FS VOP_LOCK implementation. > > > This change would affect the directory name lookup cache code > (for which a vnode reference in a cache would be very much the > same as an open instance for a vnode reference by a system open > file table reference), as well as several other subsystems. > > > Though vnodes are currently globally accounted, I beleive that > there should be a per FS interface, initially to the global > accounting interface, for freeing vnodes in an FS specific > manner. > > The eventual intent of this change is to allow per-FS management > of vnodes as part of the FS's [*,i]node pool, and to therefore > relieve the need for global vnode pool management, and thus global > recovery of vnodes for reuse. > > > This would be similar in scope to the SVR4 vnode management scheme, > as described in "The Magic Garden Explained" and the _Bach_ book. > > > One large benefit of this technique would be to allow the recovery > of unreferenced vnodes from per FS "second chance" caches, like > the FFS "ihash" facility, and therfore the recovery of perfectly > valid memory pages that refere to a referenced per FS object. > > Currently, there is no recovery mechanism whereby the valid pages > can be re-referenced for use once the vnode had been disassociated > from the per-FS object, but not from the valid pages. > > When a reference which references these pages occurs, the data, > though in core, cannot be reclaimed, and must be reread from > disk. > > ----------------------------------------------------------------------------- > > > Regards, > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F 2-5-12, Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 From owner-freebsd-current Tue Apr 8 03:46:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA02059 for current-outgoing; Tue, 8 Apr 1997 03:46:53 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA02034; Tue, 8 Apr 1997 03:46:46 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id KAA10918; Tue, 8 Apr 1997 10:46:38 GMT Date: Tue, 8 Apr 1997 19:46:38 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: DISCUSS: vnode references as open instances In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Apr 1997, Michael Hancock wrote: > Terry, > > I think it will be hard to get support to change ufs this drastically at > this time since Kirk is working on soft updates. And there is also quite > of a bit of community interest in having a trusted stable fs > implementation to fall back on. > > How you considered what Netcom? did with tfs? It seems they use their own > vnode allocation scheme. I vaguely remember seeing changes made to allow > this. I just verified this. Grep for VT_TFS in /sys/kern. It's a special case hack, but maybe we can come up with a more general way of informing the kernel that we're doing our own vnode management. Regards, Mike From owner-freebsd-current Tue Apr 8 05:54:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA07229 for current-outgoing; Tue, 8 Apr 1997 05:54:23 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA07221 for ; Tue, 8 Apr 1997 05:54:19 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id NAA04649 for ; Tue, 8 Apr 1997 13:54:00 +0100 (BST) Date: Tue, 8 Apr 1997 13:54:00 +0100 (BST) From: Doug Rabson To: current@freebsd.org Subject: Fixes to NFSv3 for review Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently added code to NFS to use write clustering for NFSv3 commits. This improves write performance for NFSv3 considerably. Unfortunately, it also had a bug which was triggered by code which write many small blocks. The symptom which I saw was a panic("nfsbioread") when performing a make world on a machine with NFS mounted src and obj. I have a fix but I am going on holiday tomorrow for a week and I don't want to commit anything without being around to deal with any subsequent problems. Could someone review and possibly commit this fix. The bug is present in both 2.2 and 3.0 branches. Index: nfs/nfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_bio.c,v retrieving revision 1.34 diff -u -r1.34 nfs_bio.c --- nfs_bio.c 1997/04/03 07:52:00 1.34 +++ nfs_bio.c 1997/04/08 11:41:17 @@ -962,9 +962,12 @@ iomode = NFSV3WRITE_FILESYNC; bp->b_flags |= B_WRITEINPROG; error = nfs_writerpc(vp, uiop, cr, &iomode, &must_commit); - if (!error && iomode == NFSV3WRITE_UNSTABLE) - bp->b_flags |= B_NEEDCOMMIT | B_CLUSTEROK; - else + if (!error && iomode == NFSV3WRITE_UNSTABLE) { + bp->b_flags |= B_NEEDCOMMIT; + if (bp->b_dirtyoff == 0 + && bp->b_dirtyend == bp->b_bufsize) + bp->b_flags |= B_CLUSTEROK; + } else bp->b_flags &= ~B_NEEDCOMMIT; bp->b_flags &= ~B_WRITEINPROG; Index: kern/vfs_cluster.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_cluster.c,v retrieving revision 1.44 diff -u -r1.44 vfs_cluster.c --- vfs_cluster.c 1997/04/01 11:48:30 1.44 +++ vfs_cluster.c 1997/04/08 11:46:12 @@ -468,6 +468,7 @@ tbp->b_flags |= B_ERROR; tbp->b_error = error; } + tbp->b_dirtyoff = tbp->b_dirtyend = 0; biodone(tbp); } relpbuf(bp); -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Tue Apr 8 05:54:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA07251 for current-outgoing; Tue, 8 Apr 1997 05:54:30 -0700 (PDT) Received: from thor.dee.uc.pt (thor.dee.uc.pt [193.136.205.35]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA07217 for ; Tue, 8 Apr 1997 05:54:07 -0700 (PDT) Received: from localhost (pm@localhost) by thor.dee.uc.pt (8.8.5/8.8.5) with SMTP id NAA12116 for ; Tue, 8 Apr 1997 13:54:21 +0100 (WEST) Date: Tue, 8 Apr 1997 13:54:20 +0100 (WEST) From: Paulo Menezes To: current@freebsd.org Subject: nfs problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, After last rebuild of the nfs server running 2.2.1 (ctm 226), the clients are unable to use mounted fs. They seem to be able to mount the fs but can do nothing with it. On the server I have the following messages NFS request from unprivileged port (193.136.205.41:1236) NFS request from unprivileged port (193.136.205.41:1236) NFS request from unprivileged port (193.136.205.41:1236) NFS request from unprivileged port (193.136.205.41:1236) NFS request from unprivileged port (193.136.205.41:1327) NFS request from unprivileged port (193.136.205.41:1327) NFS request from unprivileged port (193.136.205.41:1327) Is this a known problem, or it is just a gift I received. thanks Paulo Menezes From owner-freebsd-current Tue Apr 8 06:36:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA08885 for current-outgoing; Tue, 8 Apr 1997 06:36:38 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA08811; Tue, 8 Apr 1997 06:35:35 -0700 (PDT) Received: by sovcom.kiae.su id AA28868 (5.65.kiae-1 ); Tue, 8 Apr 1997 15:45:07 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 8 Apr 97 15:45:07 +0300 Received: (from ache@localhost) by nagual.ru (8.8.5/8.8.5) id QAA00230; Tue, 8 Apr 1997 16:43:25 +0400 (MSD) Date: Tue, 8 Apr 1997 16:43:23 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: FreeBSD-current Cc: dyson@freebsd.org, peter@freebsd.org Subject: new ufs exec crash in -current Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Put this line in your .login and you got system crash withing a minute after this command executed: exec /usr/local/bin/ssh -l -e none -c des locahlost ^^^^^ this cipher must be _not_ supported, it is true, if you run sshd 1.2.18 If you remove "exec" word from here, you'll just get proper error diagnostic about not supported cipher, but no crash. Crash details: page fault in kernel mode stack looks like: lockstatus ufs_islocked vfs_msync sync vfs_update kproc_start main Please, fix. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Tue Apr 8 09:09:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA15792 for current-outgoing; Tue, 8 Apr 1997 09:09:13 -0700 (PDT) Received: from icicle.winternet.com (adm@icicle.winternet.com [198.174.169.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA15784 for ; Tue, 8 Apr 1997 09:09:04 -0700 (PDT) Received: (from adm@localhost) by icicle.winternet.com (8.7.5/8.7.5) id LAA25526; Tue, 8 Apr 1997 11:08:38 -0500 (CDT) Posted-Date: Tue, 8 Apr 1997 11:08:38 -0500 (CDT) Received: from chaos.ecp.net(204.246.64.13) by icicle.winternet.com via smap (V2.0beta) id xma025444; Tue, 8 Apr 97 11:08:13 -0500 Received: from localhost (raistlin@localhost) by chaos.ecp.net (8.8.5/8.8.3) with SMTP id QAA03199; Tue, 8 Apr 1997 16:07:59 GMT Date: Tue, 8 Apr 1997 16:07:54 +0000 () From: Justen Stepka To: Paulo Menezes cc: current@freebsd.org Subject: Re: nfs problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Apr 1997, Paulo Menezes wrote: > > Hi, > > After last rebuild of the nfs server running 2.2.1 (ctm 226), the clients > are unable to use mounted fs. > They seem to be able to mount the fs but can do nothing with it. > On the server I have the following messages > > NFS request from unprivileged port (193.136.205.41:1236) > NFS request from unprivileged port (193.136.205.41:1236) > NFS request from unprivileged port (193.136.205.41:1236) > NFS request from unprivileged port (193.136.205.41:1236) > NFS request from unprivileged port (193.136.205.41:1327) > NFS request from unprivileged port (193.136.205.41:1327) > NFS request from unprivileged port (193.136.205.41:1327) > > Is this a known problem, or it is just a gift I received. I got the same problem and I screamed :). All that you need to do is use mountd -n on the server. FreeBSD doesn't use secure ports by default and this make allow the non secure port request. From owner-freebsd-current Tue Apr 8 10:23:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA19076 for current-outgoing; Tue, 8 Apr 1997 10:23:22 -0700 (PDT) Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA19060 for ; Tue, 8 Apr 1997 10:23:16 -0700 (PDT) Received: (from davidn@localhost) by unique.usn.blaze.net.au (8.8.5/8.8.5) id DAA02132; Wed, 9 Apr 1997 03:23:04 +1000 (EST) Message-ID: <19970409032303.34151@usn.blaze.net.au> Date: Wed, 9 Apr 1997 03:23:03 +1000 From: David Nugent To: Peter Wemm Cc: freebsd-current@freebsd.org Subject: Re: POLL & the Single FreeBSD'r References: <199704030142.BAA04433@netfl15a.devetir.qld.gov.au> <860439710.357888@haywire.DIALix.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 In-Reply-To: <860439710.357888@haywire.DIALix.COM>; from Peter Wemm on Apr 04, 1997 at 07:01:50PM Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I implemented an openbsd-style implementation of poll() some time ago > but it was mixed up in the middle of the upages stuff so it lot left. > Since then, NetBSD have done a much better implementation, I'm very tempted > to back out what I've done and start from scratch while looking at the > NetBSD method. Basically, OpenBSD implemented poll() as an alternative > interface to the select hooks in the kernel which means that poll() is > limited to what select() can test for. NetBSD did it a lot better, by > replacing the select hooks by poll hooks, and updating both front-ends to > use the new poll backend. The main difference is that under NetBSD, you > can poll for (say) ugent data on a socket as opposed to merely "readable". Interesting. Does "urgent data" include, say, an {m,c,a}time change on a file descriptor? If not, could it be implemented? I'm guessting that "urgent data" in this context has the same meaning with a socket with respect to tcp/ip transactions (ie. OOB data), but the hook for poll() I'm suggesting would be perfect for a process that sits and waits for updates or accesses to a disk file. Processes that currently do that have to either use alarm() or call select() with a timeout, and both are fairly sloppy in terms of virtual memory usage. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Tue Apr 8 10:28:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA19471 for current-outgoing; Tue, 8 Apr 1997 10:28:19 -0700 (PDT) Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA19463 for ; Tue, 8 Apr 1997 10:28:15 -0700 (PDT) Received: (from davidn@localhost) by unique.usn.blaze.net.au (8.8.5/8.8.5) id DAA02284; Wed, 9 Apr 1997 03:27:59 +1000 (EST) Message-ID: <19970409032758.35315@usn.blaze.net.au> Date: Wed, 9 Apr 1997 03:27:58 +1000 From: David Nugent To: Chuck Robey Cc: FreeBSD current Subject: Re: make world References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 In-Reply-To: ; from Chuck Robey on Apr 04, 1997 at 05:06:56PM Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Apr 04, 1997 at 05:06:56PM, Chuck Robey wrote: > You know, there are several things installed by a make world that I > *really* wish I could condition out via a make veriable: > > perl : I want to maintain my version at 5.003, not 4.036 > groff : I want groff install to stop overwriting the > /usr/share/groff_font/devlp/download file, so all > those neat fonts I bought from WC stay installed. > tcl : I want my version at 8.0a3, not the _old_ 7.5 > > There are others, probably, but these come immediately to mind. Don't forget sendmail. :) > Would it be possible to add a variable to the make files so that some of > this stuff would be ignored on build and install? Well, I know it's > logically possible, I mean politically possible or desireable? It's a good idea. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Tue Apr 8 10:31:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA19763 for current-outgoing; Tue, 8 Apr 1997 10:31:53 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA19758 for ; Tue, 8 Apr 1997 10:31:50 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id SAA07524; Tue, 8 Apr 1997 18:31:21 +0100 (BST) Date: Tue, 8 Apr 1997 18:31:21 +0100 (BST) From: Doug Rabson To: Justen Stepka cc: Paulo Menezes , current@freebsd.org Subject: Re: nfs problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Apr 1997, Justen Stepka wrote: > > > On Tue, 8 Apr 1997, Paulo Menezes wrote: > > > > > Hi, > > > > After last rebuild of the nfs server running 2.2.1 (ctm 226), the clients > > are unable to use mounted fs. > > They seem to be able to mount the fs but can do nothing with it. > > On the server I have the following messages > > > > NFS request from unprivileged port (193.136.205.41:1236) > > NFS request from unprivileged port (193.136.205.41:1236) > > NFS request from unprivileged port (193.136.205.41:1236) > > NFS request from unprivileged port (193.136.205.41:1236) > > NFS request from unprivileged port (193.136.205.41:1327) > > NFS request from unprivileged port (193.136.205.41:1327) > > NFS request from unprivileged port (193.136.205.41:1327) > > > > Is this a known problem, or it is just a gift I received. > > I got the same problem and I screamed :). All that you need to do is use > mountd -n on the server. FreeBSD doesn't use secure ports by default and > this make allow the non secure port request. > FreeBSD-current now uses secure ports by default. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Tue Apr 8 11:08:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA21462 for current-outgoing; Tue, 8 Apr 1997 11:08:58 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.dialix.com [192.203.228.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA21456 for ; Tue, 8 Apr 1997 11:08:52 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.5/8.8.5) with ESMTP id CAA11077; Wed, 9 Apr 1997 02:08:37 +0800 (WST) Message-Id: <199704081808.CAA11077@spinner.DIALix.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: David Nugent cc: freebsd-current@freebsd.org Subject: Re: POLL & the Single FreeBSD'r In-reply-to: Your message of "Wed, 09 Apr 1997 03:23:03 +1000." <19970409032303.34151@usn.blaze.net.au> Date: Wed, 09 Apr 1997 02:08:36 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Nugent wrote: > > I implemented an openbsd-style implementation of poll() some time ago > > but it was mixed up in the middle of the upages stuff so it lot left. > > Since then, NetBSD have done a much better implementation, I'm very tempted > > to back out what I've done and start from scratch while looking at the > > NetBSD method. Basically, OpenBSD implemented poll() as an alternative > > interface to the select hooks in the kernel which means that poll() is > > limited to what select() can test for. NetBSD did it a lot better, by > > replacing the select hooks by poll hooks, and updating both front-ends to > > use the new poll backend. The main difference is that under NetBSD, you > > can poll for (say) ugent data on a socket as opposed to merely "readable". > > Interesting. Does "urgent data" include, say, an {m,c,a}time > change on a file descriptor? If not, could it be implemented? No, but if we use a poll-style backend, we can define it. > I'm guessting that "urgent data" in this context has the same > meaning with a socket with respect to tcp/ip transactions (ie. > OOB data), but the hook for poll() I'm suggesting would be > perfect for a process that sits and waits for updates or > accesses to a disk file. Processes that currently do that have > to either use alarm() or call select() with a timeout, and > both are fairly sloppy in terms of virtual memory usage. Oh, what a pleasant thought! :-) poll() a directory waiting for something to put a file in there without having to wake up every so-many seconds and stat the dir (as cron does). poll() a file to see time or size changes, eg: do what tail -f does without having to sleep and re-read every so often.. Hmm.. wasn't something like this in ITS? It's print spooler was supposedly automatically woken when a file was placed in the queue directory. > Regards, > > David Nugent - Unique Computing Pty Ltd - Melbourne, Australia > Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet > davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ Cheers, -Peter From owner-freebsd-current Tue Apr 8 11:39:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA22838 for current-outgoing; Tue, 8 Apr 1997 11:39:23 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA22828 for ; Tue, 8 Apr 1997 11:39:17 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id OAA14015; Tue, 8 Apr 1997 14:36:42 -0400 (EDT) From: Peter Dufault Message-Id: <199704081836.OAA14015@hda.hda.com> Subject: Re: POLL & the Single FreeBSD'r In-Reply-To: <199704081808.CAA11077@spinner.DIALix.COM> from Peter Wemm at "Apr 9, 97 02:08:36 am" To: peter@spinner.DIALix.COM (Peter Wemm) Date: Tue, 8 Apr 1997 14:36:41 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Oh, what a pleasant thought! :-) poll() a directory waiting for > something to put a file in there without having to wake up every so-many > seconds and stat the dir (as cron does). poll() a file to see time or > size changes, eg: do what tail -f does without having to sleep and re-read > every so often.. > > Hmm.. wasn't something like this in ITS? It's print spooler was > supposedly automatically woken when a file was placed in the queue > directory. The WIN32 API has this. I don't remember what it is. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-current Tue Apr 8 11:48:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA23318 for current-outgoing; Tue, 8 Apr 1997 11:48:00 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23295 for ; Tue, 8 Apr 1997 11:47:58 -0700 (PDT) Received: from militzer.me.tuns.ca (militzer.me.tuns.ca [134.190.50.153]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id LAA01810 for ; Tue, 8 Apr 1997 11:47:56 -0700 (PDT) Received: from localhost (bemfica@localhost) by militzer.me.tuns.ca (8.8.5/8.8.4) with SMTP id PAA03965 for ; Tue, 8 Apr 1997 15:45:37 -0300 (ADT) Date: Tue, 8 Apr 1997 15:45:36 -0300 (ADT) From: Antonio Bemfica To: current@FreeBSD.ORG Subject: Re: nfs problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Apr 1997, Doug Rabson wrote: > FreeBSD-current now uses secure ports by default. And what would be the proper way to reconcile this new behaviour with the requests by clients that want access through insecure ports? I'm having problems with amd, and would not like to just "make it work" now when there is a recommended way of doing it (especially if it will get "broken" again the next time I recompile the system). Antonio -- ------------------------------------------------------------------------ "I myself have always disliked being called a 'genius'. It is fascinating to notice how quick people have been to intuit this aversion and avoid using the term" -- John Lanchester, in "The Debt to Pleasure" From owner-freebsd-current Tue Apr 8 13:10:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA28061 for current-outgoing; Tue, 8 Apr 1997 13:10:46 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA28054 for ; Tue, 8 Apr 1997 13:10:44 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.159]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id NAA01919 for ; Tue, 8 Apr 1997 13:10:41 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.5/8.7.3) id PAA00267; Tue, 8 Apr 1997 15:08:25 -0500 (CDT) Message-ID: <19970408150825.38520@peeper.my.domain> Date: Tue, 8 Apr 1997 15:08:25 -0500 From: Tom Jackson To: FreeBSD-current Subject: Re: new ufs exec crash in -current References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: ; from ????????????? on Tue, Apr 08, 1997 at 04:43:23PM +0400 Reply-To: toj@gorilla.net Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Apr 08, 1997 at 04:43:23PM +0400, ????????????? wrote: > > Put this line in your .login and you got system crash withing a minute > after this command executed: > > exec /usr/local/bin/ssh -l -e none -c des locahlost > ^^^^^ this cipher must be _not_ > supported, it is true, > if you run sshd 1.2.18 > > If you remove "exec" word from here, you'll just get proper error > diagnostic about not supported cipher, but no crash. > > Crash details: > page fault in kernel mode > > stack looks like: > > lockstatus > ufs_islocked > vfs_msync > sync > vfs_update > kproc_start > main > > Please, fix. > > I've got 3 of these fatal trap 12 pagefaults in the last 2 days; I'm not running ssh. Usually happens when su'ing to root and such. -- Tom Jackson I'm ProChoice->FreeBSD toj@gorilla.net http://www.freebsd.org tjackson@tulsix.utulsa.edu "Out in the Ozone Again" From owner-freebsd-current Tue Apr 8 13:19:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA28455 for current-outgoing; Tue, 8 Apr 1997 13:19:28 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA28450 for ; Tue, 8 Apr 1997 13:19:22 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id QAA14157 for current@freebsd.org; Tue, 8 Apr 1997 16:16:42 -0400 (EDT) From: Peter Dufault Message-Id: <199704082016.QAA14157@hda.hda.com> Subject: POSIX 4 question To: current@freebsd.org Date: Tue, 8 Apr 1997 16:16:41 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A follow up to the earlier discussion about POSIX 4: In adding the correct interface I'm tempted to: 1. (Easy) Make everything contingent on "OPT_POSIX4" and "OPT_POSIX4_ENABLED" (second option says _POSIX_C_SOURCE isn't requesting an earlier interface); 2. #define all of the new POSIX 4 "_POSIX_feature_test" macros so that at compile time it appears ALL features are possibly present; 3. #define the minimum limit required in the system headers if not already defined; 4. Have sysconf return that the functionality isn't configured in; 5. Provide stub functions that fail. Then the functionality can be loaded in one feature at a time via the LKM mechanism at run time without changing the system headers, and at LKM load time they can provide the correct info to sysconf. Comments? I like the idea of having the infrastructure in place to ensure consistency in loading, unloading, sysconf, etc. Peter -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-current Tue Apr 8 15:35:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA06098 for current-outgoing; Tue, 8 Apr 1997 15:35:38 -0700 (PDT) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA06074 for ; Tue, 8 Apr 1997 15:35:32 -0700 (PDT) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id PAA24991 for ; Tue, 8 Apr 1997 15:37:47 -0700 (PDT) Received: (qmail 25891 invoked by uid 110); 8 Apr 1997 22:34:24 -0000 Message-ID: <19970408223424.25890.qmail@suburbia.net> Subject: ipfilter-proff.shar.gz To: hackers@freebsd.org Date: Wed, 9 Apr 1997 08:34:23 +1000 (EST) Cc: security@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've addressed what I consider all outstanding issues with ipfilter insofar as one can without stepping on too many toes. This is complete. I haven't tested it under 2.2, but any changes should be very minimal. /usr/src/contrib/ipfilter can be, and should be zorched after this shar unpacks. Review is appreciated, but anything but bug-fixes will fall on deaf ears. The code is available as: ftp.freebsd.org/FreeBSD/incoming/ipfilter-proff.shar.gz (100k) and from GNATS as `kern/3234'. Unpack the three new source trees and two patch files: root@current# cd /usr root@current# unshar Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA10401 for current-outgoing; Tue, 8 Apr 1997 16:30:00 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA10393; Tue, 8 Apr 1997 16:29:55 -0700 (PDT) Message-Id: <199704082329.QAA10393@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA245011847; Wed, 9 Apr 1997 09:24:07 +1000 From: Darren Reed Subject: Re: ipfilter-proff.shar.gz To: proff@suburbia.net Date: Wed, 9 Apr 1997 09:24:07 +1000 (EST) Cc: hackers@freebsd.org, security@freebsd.org, current@freebsd.org In-Reply-To: <19970408223424.25890.qmail@suburbia.net> from "proff@suburbia.net" at Apr 9, 97 08:34:23 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There was one other issue I'd like to see resolved and that was how IP Filter should be included within FreeBSD if the current layout isn't satisfactory. I recall the last email I read on the subject was from Julian, but in this, i really need a decision made by someone who is authorised to make that sort of decision before any changes to the current layout are made. Darren From owner-freebsd-current Tue Apr 8 16:34:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA10867 for current-outgoing; Tue, 8 Apr 1997 16:34:22 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA10859 for ; Tue, 8 Apr 1997 16:34:19 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id QAA09341; Tue, 8 Apr 1997 16:34:16 -0700 (PDT) Message-Id: <199704082334.QAA09341@austin.polstra.com> To: bemfica@militzer.me.tuns.ca Subject: Re: nfs problem Newsgroups: polstra.freebsd.current In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Tue, 08 Apr 1997 16:34:15 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Antonio Bemfica wrote: > On Tue, 8 Apr 1997, Doug Rabson wrote: > > > FreeBSD-current now uses secure ports by default. > > And what would be the proper way to reconcile this new behaviour with the > requests by clients that want access through insecure ports? I'm having > problems with amd, and would not like to just "make it work" now when > there is a recommended way of doing it (especially if it will get "broken" > again the next time I recompile the system). You can either configure the clients to use reserved ports, or you can configure the server so that it doesn't require them. To make a client use reserved ports, just add the "resvport" option to its mount command lines, or to your amd map file: /defaults type:=host;fs:=${autodir}/${rhost};rhost:=${key} * opts:=rw,grpid,resvport This option has already been added to /usr/src/etc/amd.map, by the way. Somebody else on this list recently described how to change the server configuration. Sorry, I don't remember how. -- 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 Tue Apr 8 16:55:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA12669 for current-outgoing; Tue, 8 Apr 1997 16:55:22 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12657 for ; Tue, 8 Apr 1997 16:55:18 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA21446; Wed, 9 Apr 1997 09:24:53 +0930 (CST) From: Michael Smith Message-Id: <199704082354.JAA21446@genesis.atrad.adelaide.edu.au> Subject: Re: nfs problem In-Reply-To: <199704082334.QAA09341@austin.polstra.com> from John Polstra at "Apr 8, 97 04:34:15 pm" To: jdp@polstra.com (John Polstra) Date: Wed, 9 Apr 1997 09:24:53 +0930 (CST) Cc: bemfica@militzer.me.tuns.ca, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Polstra stands accused of saying: > > You can either configure the clients to use reserved ports, > or you can configure the server so that it doesn't require them. > To make a client use reserved ports, just add the "resvport" > option to its mount command lines, or to your amd map file: I find it extremely annoying that named options line "resvport" aren't documented for mount or mount_nfs. *grumble* > Somebody else on this list recently described how to change the > server configuration. Sorry, I don't remember how. sysctl -w vfs.nfs.nfs_privport=0 There may be an /etc/sysconfig knob as well. > John Polstra jdp@polstra.com -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 8 17:15:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA14422 for current-outgoing; Tue, 8 Apr 1997 17:15:21 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14417 for ; Tue, 8 Apr 1997 17:15:18 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA21646 for current@freebsd.org; Wed, 9 Apr 1997 09:45:16 +0930 (CST) From: Michael Smith Message-Id: <199704090015.JAA21646@genesis.atrad.adelaide.edu.au> Subject: 'make release' &c. To: current@freebsd.org Date: Wed, 9 Apr 1997 09:45:15 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm cross because people keep rebooting the machine I'm trying to build a release on, but that's neither here nor there 8) I actually wanted to gripe about this : setenv NOSECURE setenv NOPROFILE setenv NOGAMES setenv NO_PORTS *^* Can we either lose the underscore (bad) or have it become WITHPORTS that actually enables the ports (better)? You can imagine how I felt after about the fifth 'make release' failure having to go look for this one buried in the release Makefile (it's not even listed at the top, *grumble*. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 8 17:18:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA14594 for current-outgoing; Tue, 8 Apr 1997 17:18:48 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14586 for ; Tue, 8 Apr 1997 17:18:43 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id RAA09538; Tue, 8 Apr 1997 17:18:37 -0700 (PDT) Message-Id: <199704090018.RAA09538@austin.polstra.com> To: Michael Smith cc: current@freebsd.org Subject: Re: nfs problem In-reply-to: Your message of "Wed, 09 Apr 1997 09:24:53 +0930." <199704082354.JAA21446@genesis.atrad.adelaide.edu.au> References: <199704082354.JAA21446@genesis.atrad.adelaide.edu.au> Date: Tue, 08 Apr 1997 17:18:36 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I find it extremely annoying that named options line "resvport" > aren't documented for mount or mount_nfs. *grumble* "resvport" is documented in mount_nfs(8), under the "-o" option. It and the other named options are described as deprecated, though. > sysctl -w vfs.nfs.nfs_privport=0 Thanks. John -- 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 Tue Apr 8 17:23:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA14830 for current-outgoing; Tue, 8 Apr 1997 17:23:32 -0700 (PDT) Received: from ouray.cudenver.edu (aybaram@ouray.cudenver.edu [132.194.10.9]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA14813 for ; Tue, 8 Apr 1997 17:23:29 -0700 (PDT) Received: by ouray.cudenver.edu (5.65/DEC-OSF/1.2) id AA07353; Tue, 8 Apr 1997 18:24:55 -0600 From: aybaram@ouray.cudenver.edu (Alex Baram) Message-Id: <9704090024.AA07353@ouray.cudenver.edu> To: current@freebsd.org Date: Tue, 8 Apr 1997 18:24:55 -0600 (MDT) Cc: iu@ouray.cudenver.edu X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-current Tue Apr 8 17:28:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA15138 for current-outgoing; Tue, 8 Apr 1997 17:28:36 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15133 for ; Tue, 8 Apr 1997 17:28:34 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id RAA21082; Tue, 8 Apr 1997 17:28:10 -0700 (PDT) To: Michael Smith cc: jdp@polstra.com (John Polstra), bemfica@militzer.me.tuns.ca, current@freebsd.org Subject: Re: nfs problem In-reply-to: Your message of "Wed, 09 Apr 1997 09:24:53 +0930." <199704082354.JAA21446@genesis.atrad.adelaide.edu.au> Date: Tue, 08 Apr 1997 17:28:10 -0700 Message-ID: <21079.860545690@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I find it extremely annoying that named options line "resvport" > aren't documented for mount or mount_nfs. *grumble* You know where the man pages are... :-) Jordan From owner-freebsd-current Tue Apr 8 17:54:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA15933 for current-outgoing; Tue, 8 Apr 1997 17:54:38 -0700 (PDT) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15928 for ; Tue, 8 Apr 1997 17:54:35 -0700 (PDT) Received: from baud.eng.umd.edu (baud.eng.umd.edu [129.2.98.183]) by po1.glue.umd.edu (8.8.5/8.8.5) with ESMTP id UAA01059; Tue, 8 Apr 1997 20:54:32 -0400 (EDT) Received: from localhost (chuckr@localhost) by baud.eng.umd.edu (8.8.5/8.6.4) with SMTP id UAA10691; Tue, 8 Apr 1997 20:54:30 -0400 (EDT) X-Authentication-Warning: baud.eng.umd.edu: chuckr owned process doing -bs Date: Tue, 8 Apr 1997 20:54:29 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@baud.eng.umd.edu To: Michael Smith cc: current@freebsd.org Subject: Re: 'make release' &c. In-Reply-To: <199704090015.JAA21646@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Apr 1997, Michael Smith wrote: > > I'm cross because people keep rebooting the machine I'm trying to build > a release on, but that's neither here nor there 8) > > I actually wanted to gripe about this : > > setenv NOSECURE > setenv NOPROFILE > setenv NOGAMES > setenv NO_PORTS Yeah, underbars. Some of the mount stuff that's recently changed because of the Lite2 changes shows the same problems. Look at the mount stuff: journey2:/usr/src/sys:62 >find . -name \*mount.h -print ./i386/ibcs2/ibcs2_mount.h ./isofs/cd9660/cd9660_mount.h ./msdosfs/msdosfsmount.h ./nfs/nfsmount.h ./sys/mount.h ./ufs/ufs/ufsmount.h I'd like to see the ibcs2 and cd9660 stuff changed to reject the underbar, or add it to the other ones. I'd figure out the required changes by munging around my tree, if I got consensus on the need (maybe this weekend?) ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Tue Apr 8 17:55:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA15979 for current-outgoing; Tue, 8 Apr 1997 17:55:23 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15973 for ; Tue, 8 Apr 1997 17:55:20 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id RAA21252; Tue, 8 Apr 1997 17:55:15 -0700 (PDT) To: Michael Smith cc: current@freebsd.org Subject: Re: 'make release' &c. In-reply-to: Your message of "Wed, 09 Apr 1997 09:45:15 +0930." <199704090015.JAA21646@genesis.atrad.adelaide.edu.au> Date: Tue, 08 Apr 1997 17:55:15 -0700 Message-ID: <21248.860547315@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Can we either lose the underscore (bad) or have it become WITHPORTS > that actually enables the ports (better)? You can imagine how I felt I vote for losing the underscore since at least the NOFOO convention is well understood. I'm not quite ready for a whole new batch of WITHFOO variables. :-) Jordan From owner-freebsd-current Tue Apr 8 18:30:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA17401 for current-outgoing; Tue, 8 Apr 1997 18:30:45 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA17367; Tue, 8 Apr 1997 18:30:40 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id BAA15672; Wed, 9 Apr 1997 01:30:32 GMT Date: Wed, 9 Apr 1997 10:30:32 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: DISCUSS: vnode references as open instances In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Apr 1997, Michael Hancock wrote: > > Though vnodes are currently globally accounted, I beleive that > > there should be a per FS interface, initially to the global > > accounting interface, for freeing vnodes in an FS specific > > manner. > > > > The eventual intent of this change is to allow per-FS management > > of vnodes as part of the FS's [*,i]node pool, and to therefore > > relieve the need for global vnode pool management, and thus global > > recovery of vnodes for reuse. > > > > One large benefit of this technique would be to allow the recovery > > of unreferenced vnodes from per FS "second chance" caches, like > > the FFS "ihash" facility, and therfore the recovery of perfectly > > valid memory pages that refere to a referenced per FS object. > > > > Currently, there is no recovery mechanism whereby the valid pages > > can be re-referenced for use once the vnode had been disassociated > > from the per-FS object, but not from the valid pages. > > > > When a reference which references these pages occurs, the data, > > though in core, cannot be reclaimed, and must be reread from > > disk. 1) Create a directory /sys/u2fs. 2) Build the necessary scaffolding, VT_U2FS, vop scripts, etc. and do the VT_TFS thing. 3) Submit updates to the /sys/u2fs directory in parcels as big as you want. 4) If your analysis is accurate, and you correctly design and implement the changes then most applications will show a significant performance improvement. 5) Get Matt Dillon, Joe Greco, and Karl to "beat the snot" out your new improved ufs and get them to make testimonials. 6) Then work on converting the VT_TFS, VT_U2FS special case the general case. Regards, Mike Hancock From owner-freebsd-current Tue Apr 8 18:33:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA17572 for current-outgoing; Tue, 8 Apr 1997 18:33:34 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA17567 for ; Tue, 8 Apr 1997 18:33:31 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id VAA24304; Tue, 8 Apr 1997 21:33:20 -0400 (EDT) Date: Tue, 8 Apr 1997 21:33:20 -0400 (EDT) From: Garrett Wollman Message-Id: <199704090133.VAA24304@khavrinen.lcs.mit.edu> To: Michael Smith Cc: jdp@polstra.com (John Polstra), bemfica@militzer.me.tuns.ca, current@freebsd.org Subject: Re: nfs problem In-Reply-To: <199704082354.JAA21446@genesis.atrad.adelaide.edu.au> References: <199704082334.QAA09341@austin.polstra.com> <199704082354.JAA21446@genesis.atrad.adelaide.edu.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > I find it extremely annoying that named options line "resvport" > aren't documented for mount or mount_nfs. *grumble* That's because `resvport' is compatibility cruft. The proper name is `-P'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Tue Apr 8 18:49:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA18210 for current-outgoing; Tue, 8 Apr 1997 18:49:54 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA18199 for ; Tue, 8 Apr 1997 18:49:48 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA22555; Wed, 9 Apr 1997 11:19:19 +0930 (CST) From: Michael Smith Message-Id: <199704090149.LAA22555@genesis.atrad.adelaide.edu.au> Subject: Re: nfs problem In-Reply-To: <199704090133.VAA24304@khavrinen.lcs.mit.edu> from Garrett Wollman at "Apr 8, 97 09:33:20 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Wed, 9 Apr 1997 11:19:19 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, jdp@polstra.com, bemfica@militzer.me.tuns.ca, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Garrett Wollman stands accused of saying: > < said: > > > I find it extremely annoying that named options line "resvport" > > aren't documented for mount or mount_nfs. *grumble* > > That's because `resvport' is compatibility cruft. The proper name is > `-P'. Huh? -P is meant to represent a 'better' thing than a meaningful keyword? That's crazy 8( > -GAWollman -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 8 23:22:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA29350 for current-outgoing; Tue, 8 Apr 1997 23:22:15 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA29345 for ; Tue, 8 Apr 1997 23:22:10 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id JAA13506 for current@freebsd.org; Wed, 9 Apr 1997 09:22:27 +0300 (EET DST) From: mika ruohotie Message-Id: <199704090622.JAA13506@shadows.aeon.net> Subject: 3.0-current make world To: current@freebsd.org Date: Wed, 9 Apr 1997 09:22:26 +0300 (EET DST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk current make world would die with error: cc -O2 -m486 -pipe -I/usr/src/lib/libtcl/../../contrib/tcl/generic -I/usr/src/li b/libtcl/../../contrib/tcl/unix -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DTIME_WIT H_SYS_TIME=1 -DHAVE_TM_ZONE=1 -DHAVE_TM_GMTOFF=1 -DSTDC_HEADERS=1 -DNEED_MATHERR =1 -DTCL_SHLIB_EXT=\".so\" -DTCL_LIBRARY=\"/usr/libdata/tcl\" -c /usr/src/lib/li btcl/../../contrib/tcl/unix/tclMtherr.c -o tclMtherr.o /usr/src/lib/libtcl/../../contrib/tcl/unix/tclMtherr.c: In function `matherr': /usr/src/lib/libtcl/../../contrib/tcl/unix/tclMtherr.c:80: dereferencing pointer to incomplete type /usr/src/lib/libtcl/../../contrib/tcl/unix/tclMtherr.c:80: `DOMAIN' undeclared ( first use this function) /usr/src/lib/libtcl/../../contrib/tcl/unix/tclMtherr.c:80: (Each undeclared iden tifier is reported only once /usr/src/lib/libtcl/../../contrib/tcl/unix/tclMtherr.c:80: for each function it appears in.) /usr/src/lib/libtcl/../../contrib/tcl/unix/tclMtherr.c:80: dereferencing pointer to incomplete type /usr/src/lib/libtcl/../../contrib/tcl/unix/tclMtherr.c:80: `SING' undeclared (fi rst use this function) ...skipping... *** Error code 1 (continuing) but since i use 'make -k world' it doesnt die here... and coz it's tcl thing i dont much care... =) that's been in my last two make worlds, one from saturday, one from last night. mickey From owner-freebsd-current Tue Apr 8 23:25:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA29514 for current-outgoing; Tue, 8 Apr 1997 23:25:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA29506 for ; Tue, 8 Apr 1997 23:24:57 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA23115 for freebsd-current@freebsd.org; Wed, 9 Apr 1997 08:24:49 +0200 Received: (from j@localhost) by jette.heep.sax.de (8.8.5/8.8.5) id IAA00594; Wed, 9 Apr 1997 08:15:02 +0200 (CEST) Message-ID: <19970409081458.GD60312@jette.heep.sax.de> Date: Wed, 9 Apr 1997 08:14:58 +0200 From: j@jette.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org (FreeBSD Current Mailing List) Subject: Re: CVSUP and Release Question References: <19970407182108.RO31161@jette.heep.sax.de> <3224.860437791@time.cdrom.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3224.860437791@time.cdrom.com>; from Jordan K. Hubbard on Apr 7, 1997 11:29:51 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > So, this was the intended effect. :-) > > Fine, so now you explain to all the current pre-stables that they're > really pre-stable and not quite so safe as their uname(1) output would > have them believe. :-) They believed they were running a stable system by the time 2.1-stable has been established... so what? Do you know of any major instability of 2.2-stable? I don't. (Sure, i know of a number of bugs, but no serious instability ones. The ahc bugs should be present in all branches anyway, since Justin keeps them in sync.) -- bye, J"org ...just travelling around. Don't try reaching me except by mail. :) From owner-freebsd-current Wed Apr 9 03:32:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA10443 for current-outgoing; Wed, 9 Apr 1997 03:32:14 -0700 (PDT) Received: from mailbox.uq.edu.au (zzshocki.slip.cc.uq.edu.au [130.102.221.173]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10438 for ; Wed, 9 Apr 1997 03:32:09 -0700 (PDT) Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by mailbox.uq.edu.au (8.8.5/8.6.12) with ESMTP id UAA00811; Wed, 9 Apr 1997 20:20:07 +1000 (EST) Message-Id: <199704091020.UAA00811@mailbox.uq.edu.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Peter Wemm cc: current@freebsd.org Subject: Re: POLL & the Single FreeBSD'r In-reply-to: Your message of "Wed, 09 Apr 1997 02:08:36 +0800." <199704081808.CAA11077@spinner.DIALix.COM> From: shocking@mailbox.uq.edu.au Reply-To: shocking@mailbox.uq.edu.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Apr 1997 20:20:06 +1000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Pete, if you can figure out a way to have it co-exist with old LKMs for devices that have the select interface only (I'm thinking here of the OSS LKM I just purchased), then, in the words of that ad which the HeavensGate people acted on, Just Do It. Stephen From owner-freebsd-current Wed Apr 9 05:08:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA15030 for current-outgoing; Wed, 9 Apr 1997 05:08:06 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15025 for ; Wed, 9 Apr 1997 05:08:03 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id IAA01550 for ; Wed, 9 Apr 1997 08:06:32 -0400 (EDT) Date: Wed, 9 Apr 1997 08:06:31 -0400 (EDT) From: James FitzGibbon To: freebsd-current@freebsd.org Subject: NFS + Quotas in current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is support for quotas over NFS new in 3.0-current ? I can do it on one of my machines (which is 2.2, upgraded to -current, and has had world made on it in the last two weeks), but it doesn't work with a 2.2.1R machine or a 3.0-970209-SNAP machine freshly installed (having recompiled the kernel with "options QUOTA"). If it is new in the last two months, how stable is it ? I'd appreciate thoughts on the doability of it being merged into RELENG_2_2, or if a diff applied to the /src/sys/nfs tree would be even feasible. Thanks. -- j. From owner-freebsd-current Wed Apr 9 05:18:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA15869 for current-outgoing; Wed, 9 Apr 1997 05:18:17 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.dialix.com [192.203.228.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15857 for ; Wed, 9 Apr 1997 05:18:12 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.5/8.8.5) with ESMTP id UAA17638; Wed, 9 Apr 1997 20:17:56 +0800 (WST) Message-Id: <199704091217.UAA17638@spinner.DIALix.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: shocking@mailbox.uq.edu.au cc: current@freebsd.org Subject: Re: POLL & the Single FreeBSD'r In-reply-to: Your message of "Wed, 09 Apr 1997 20:20:06 +1000." <199704091020.UAA00811@mailbox.uq.edu.au> Date: Wed, 09 Apr 1997 20:17:56 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk shocking@mailbox.uq.edu.au wrote: > > Pete, if you can figure out a way to have it co-exist with old LKMs > for devices that have the select interface only (I'm thinking here of the OSS > LKM I just purchased), then, in the words of that ad which the HeavensGate > people acted on, > > Just Do It. Yeah, well, that's the thing isn't it... Trying to maintain binary compatability with an older release... :-] The select handler takes an "int" arg, the poll handler takes an "int *" arg. Extending the cdevsw vector is painful.. Still, I guess there's the possibility of doing something cute within devsw_register(), or have a devsw_register2 with some #defines so that the old devsw_register takes an "ocdevsw" table and pads it, the new one takes the extended table, and compile time checking sorts out the mess. ie: something similar to the getvfsbyname() and mount() tweaks. I guess the question becomes, what else is likely to break from a kernel binary compatability perspective soon anyway? Is the LKM likely to "know" about offsets in struct proc etc? These change regularly.. > Stephen Cheers, -Peter From owner-freebsd-current Wed Apr 9 07:55:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA23814 for current-outgoing; Wed, 9 Apr 1997 07:55:50 -0700 (PDT) Received: from dn800e0.fingerhut.com (dn800e0-ext.fingerhut.com [204.221.45.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA23809 for ; Wed, 9 Apr 1997 07:55:45 -0700 (PDT) Received: from dn800e0.fingerhut.com (root@localhost) by dn800e0.fingerhut.com (8.7.5/8.7.3) with ESMTP id JAA19090; Wed, 9 Apr 1997 09:57:08 -0500 (CDT) Received: from seag.fingerhut.com (GF007E0.SEAG.fingerhut.com [151.210.140.7]) by dn800e0.fingerhut.com (8.7.5/8.7.3) with SMTP id JAA19086; Wed, 9 Apr 1997 09:57:07 -0500 (CDT) Received: from gf006e0.seag.fingerhut.com by seag.fingerhut.com (SMI-8.6/SMI-SVR4) id JAA18395; Wed, 9 Apr 1997 09:55:42 -0500 Received: by gf006e0.seag.fingerhut.com (5.x/SMI-SVR4) id AA18339; Wed, 9 Apr 1997 09:55:39 -0500 Date: Wed, 9 Apr 1997 09:55:39 -0500 Message-Id: <9704091455.AA18339@gf006e0.seag.fingerhut.com> From: Bruce Albrecht To: Chuck Robey Cc: FreeBSD current Subject: Re: make world In-Reply-To: References: Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey writes: > You know, there are several things installed by a make world that I > *really* wish I could condition out via a make veriable: > > perl : I want to maintain my version at 5.003, not 4.036 > groff : I want groff install to stop overwriting the > /usr/share/groff_font/devlp/download file, so all > those neat fonts I bought from WC stay installed. > tcl : I want my version at 8.0a3, not the _old_ 7.5 It seems to me that after Perl 5.004 is released (probably within the next 3 weeks), it should be made the standard Perl for FreeBSD-current. Perl 4.036 isn't supported by the perl porters, and Perl 5 is way cooler and much more powerful. From owner-freebsd-current Wed Apr 9 09:51:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA01335 for current-outgoing; Wed, 9 Apr 1997 09:51:49 -0700 (PDT) Received: from charm.il.ft.hse.nl (erik@charm.il.ft.hse.nl [145.85.127.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01330 for ; Wed, 9 Apr 1997 09:51:45 -0700 (PDT) Received: (from erik@localhost) by charm.il.ft.hse.nl (8.8.5/8.7.3) id SAA17508; Wed, 9 Apr 1997 18:51:41 +0200 (CEST) From: Erik Manders Message-Id: <199704091651.SAA17508@charm.il.ft.hse.nl> Subject: Re: NFS + Quotas in current In-Reply-To: from James FitzGibbon at "Apr 9, 97 08:06:31 am" To: james@nexis.net (James FitzGibbon) Date: Wed, 9 Apr 1997 18:51:41 +0200 (MEST) Cc: freebsd-current@freebsd.org X-Location: Somewhere in The Netherlands X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk James FitzGibbon is said to have made the following statement: > > Is support for quotas over NFS new in 3.0-current ? I can do it on one of > my machines (which is 2.2, upgraded to -current, and has had world made > on it in the last two weeks), but it doesn't work with a 2.2.1R machine or > a 3.0-970209-SNAP machine freshly installed (having recompiled the kernel > with "options QUOTA"). > > If it is new in the last two months, how stable is it ? I'd appreciate > thoughts on the doability of it being merged into RELENG_2_2, or if a diff > applied to the /src/sys/nfs tree would be even feasible. > > Thanks. > > -- > j. Well, I have got it to work, mostly. The only thing I haven't gotten to work yet is the ability to set quotas over the net. This will require kernel hacking Quotas seems to be stable to the extent that you can export a filesystem with quotas and have the server enforce them. It is even possble to have quota(1) report quota and limit data to a remote user, but only if the quota file is in the mounted filesystem and rpc.rquotad is running on the fileserver. Patching rpc.rquotad to keep working even if the quota files are located outside their filesystems is easy, make a one line change to .../libexec/rpc.rquotad/rquotad.c::initfs(). ... stat(qfpathname, &st); ... should be changed to ... stat(fs_current->st_dev, &st); ... Cheers, Erik Manders erik@il.ft.hse.nl -- It is by caffeine alone that I set my mind in motion; it is by the cans of cola that the thoughts acquire speed, hands acquire shaking, the shaking becomes a warning; it is with caffeine alone that I set my mind in motion. --from the movie `Dune', edited From owner-freebsd-current Wed Apr 9 10:03:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA02005 for current-outgoing; Wed, 9 Apr 1997 10:03:40 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA01996 for ; Wed, 9 Apr 1997 10:03:33 -0700 (PDT) Received: from whizzo.transsys.com by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0wF0mQ-00096zC; Wed, 9 Apr 97 10:03 PDT Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.5/8.7.3) with SMTP id MAA19396; Wed, 9 Apr 1997 12:59:33 -0400 (EDT) Message-Id: <199704091659.MAA19396@whizzo.transsys.com> To: David Nugent cc: Chuck Robey , FreeBSD current From: "Louis A. Mamakos" Subject: Re: make world References: <19970409032758.35315@usn.blaze.net.au> In-reply-to: Your message of "Wed, 09 Apr 1997 03:27:58 +1000." <19970409032758.35315@usn.blaze.net.au> Date: Wed, 09 Apr 1997 12:59:33 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Apr 04, 1997 at 05:06:56PM, Chuck Robey wrote: > > You know, there are several things installed by a make world that I > > *really* wish I could condition out via a make veriable: > > > > perl : I want to maintain my version at 5.003, not 4.036 > > groff : I want groff install to stop overwriting the > > /usr/share/groff_font/devlp/download file, so all > > those neat fonts I bought from WC stay installed. > > tcl : I want my version at 8.0a3, not the _old_ 7.5 > > > > There are others, probably, but these come immediately to mind. > > Don't forget sendmail. :) We also have a rather ederly xntp in the FreeBSD distirbution. The newer one has my fixed to use kernel-based timestamps (which I did on FreeBSD, and is in our kernel now). As far as I know, FreeBSD is unique in this capability, but our xntp doesn't know how to use it. The newer versions just compile out-of-the-box on FreeBSD, so I don't know how hard it is to update the one in our tree. I've had very mixed results getting stuff merged into the tree - the Brooktree 848 changes I've done got merged because someone with commit privs was also actively involved in the process. The socket-timestamp kernel code got in. But after two attempts to get simple changes to /usr/sbin/moused in (which would keep my mouse working when doing 'make world', sigh) and a one-liner to /usr/src/sbin/mount/getmntopts.c to fix a bug introduced recently introduced that breaks cfs, I dunno what to think. louie From owner-freebsd-current Wed Apr 9 10:48:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA04239 for current-outgoing; Wed, 9 Apr 1997 10:48:20 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04234 for ; Wed, 9 Apr 1997 10:48:18 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id NAA22647; Wed, 9 Apr 1997 13:46:52 -0400 (EDT) Date: Wed, 9 Apr 1997 13:46:52 -0400 (EDT) From: Brian Tao To: Frank Chen Hsiung Chan cc: FREEBSD-CURRENT-L Subject: Re: XFree86 3.2 causes constant 1.0 load average? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Apr 1997, Frank Chen Hsiung Chan wrote: > > We had this problem here. We then found that the asclock is > responsible for this. Try not running asclock and/or other asstuff, > that might help. I really like asclock though, but the bogus load average does not always occur (even though asclock is always running). Right now my load is reported as 0.04. I'll have to make a log of what I do in a typical X session and see if that correlates with the load. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-current Wed Apr 9 10:50:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA04379 for current-outgoing; Wed, 9 Apr 1997 10:50:36 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04367 for ; Wed, 9 Apr 1997 10:50:27 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id NAA22654; Wed, 9 Apr 1997 13:47:58 -0400 (EDT) Date: Wed, 9 Apr 1997 13:47:57 -0400 (EDT) From: Brian Tao To: Tom Bartol cc: FREEBSD-CURRENT-L Subject: Re: XFree86 3.2 causes constant 1.0 load average? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Apr 1997, Tom Bartol wrote: > > I am running FreeBSD-3.0-970209-SNAP and AfterStep-1.0pre6 also and > I too occasionally see this same thing (this morning, in fact). I > have not been able to track it down. What X server are you using? Mach64? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-current Wed Apr 9 11:57:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA08392 for current-outgoing; Wed, 9 Apr 1997 11:57:28 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA08375 for ; Wed, 9 Apr 1997 11:57:24 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id LAA25452; Wed, 9 Apr 1997 11:57:16 -0700 (PDT) Date: Wed, 9 Apr 1997 11:57:14 -0700 (PDT) From: Tom Bartol To: Brian Tao cc: FREEBSD-CURRENT-L Subject: Re: XFree86 3.2 causes constant 1.0 load average? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes, I'm using the Mach64 server. Tom On Wed, 9 Apr 1997, Brian Tao wrote: > On Mon, 7 Apr 1997, Tom Bartol wrote: > > > > I am running FreeBSD-3.0-970209-SNAP and AfterStep-1.0pre6 also and > > I too occasionally see this same thing (this morning, in fact). I > > have not been able to track it down. > > What X server are you using? Mach64? > -- > Brian Tao (BT300, taob@netcom.ca) > "Though this be madness, yet there is method in't" > > From owner-freebsd-current Wed Apr 9 12:23:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA10284 for current-outgoing; Wed, 9 Apr 1997 12:23:00 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10266 for ; Wed, 9 Apr 1997 12:22:55 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.5/8.7.3) with SMTP id PAA20011; Wed, 9 Apr 1997 15:22:21 -0400 (EDT) Message-Id: <199704091922.PAA20011@whizzo.transsys.com> To: Brian Tao cc: Frank Chen Hsiung Chan , FREEBSD-CURRENT-L From: "Louis A. Mamakos" Subject: Re: XFree86 3.2 causes constant 1.0 load average? References: In-reply-to: Your message of "Wed, 09 Apr 1997 13:46:52 EDT." Date: Wed, 09 Apr 1997 15:22:21 -0400 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why not "ktrace" the process to see what it's doing? I've noticed a similar problem with an X11 application (fxtv, which puts a window frame up on the display and waits for events while the kernel driver arranged the video image to be copied into the frame buffer). When I ktrace'ed it, it noticed it doing a whole bunch 'o FIONREAD ioctl's, just as hard as it could. I've not investigated any further yet, but something like this would get you pointed in the right direction. louie From owner-freebsd-current Wed Apr 9 12:48:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA11976 for current-outgoing; Wed, 9 Apr 1997 12:48:37 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA11961 for ; Wed, 9 Apr 1997 12:48:17 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA07377; Wed, 9 Apr 1997 12:26:47 -0700 From: Terry Lambert Message-Id: <199704091926.MAA07377@phaeton.artisoft.com> Subject: Re: nfs problem To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 9 Apr 1997 12:26:47 -0700 (MST) Cc: wollman@khavrinen.lcs.mit.edu, msmith@atrad.adelaide.edu.au, jdp@polstra.com, bemfica@militzer.me.tuns.ca, current@FreeBSD.ORG In-Reply-To: <199704090149.LAA22555@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 9, 97 11:19:19 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I find it extremely annoying that named options line "resvport" > > > aren't documented for mount or mount_nfs. *grumble* > > > > That's because `resvport' is compatibility cruft. The proper name is > > `-P'. > > Huh? -P is meant to represent a 'better' thing than a meaningful keyword? > That's crazy 8( The -P is a getopt(3) parseable command line option for mount_nfs. And yes, making the fstab options match the command line options for the mount for the FS type specified in the fstab *is* a better thing. You might successfully argue for "-o resvport,nosuid" or whatever as a syntax change for "mount_nfs"... 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 Wed Apr 9 12:59:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA12546 for current-outgoing; Wed, 9 Apr 1997 12:59:51 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA12534 for ; Wed, 9 Apr 1997 12:59:32 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id VAA10153; Wed, 9 Apr 1997 21:58:51 +0200 (SAT) From: John Hay Message-Id: <199704091958.VAA10153@zibbi.mikom.csir.co.za> Subject: Re: make world In-Reply-To: <199704091659.MAA19396@whizzo.transsys.com> from "Louis A. Mamakos" at "Apr 9, 97 12:59:33 pm" To: louie@TransSys.COM (Louis A. Mamakos) Date: Wed, 9 Apr 1997 21:58:50 +0200 (SAT) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > We also have a rather ederly xntp in the FreeBSD distirbution. The newer > one has my fixed to use kernel-based timestamps (which I did on FreeBSD, > and is in our kernel now). As far as I know, FreeBSD is unique in this > capability, but our xntp doesn't know how to use it. The newer versions > just compile out-of-the-box on FreeBSD, so I don't know how hard it is to > update the one in our tree. > I have been thinking of updateing it, but it has been changing too often. As soon as it stabilizes I'll have a look at it. Harlan said in his announce message of xntp3-5.90 that it is the release candidate so maybe we won't have to wait too long. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Wed Apr 9 13:37:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA16264 for current-outgoing; Wed, 9 Apr 1997 13:37:41 -0700 (PDT) Received: from desk.jhs.no_domain (slip139-92-4-182.mu.de.ibm.net [139.92.4.182]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA16225; Wed, 9 Apr 1997 13:37:06 -0700 (PDT) Received: from desk.jhs.no_domain (localhost [127.0.0.1]) by desk.jhs.no_domain (8.7.5/8.6.9) with ESMTP id TAA08869; Wed, 9 Apr 1997 19:33:38 +0200 (MET DST) Message-Id: <199704091733.TAA08869@desk.jhs.no_domain> To: Darren Reed cc: proff@suburbia.net, hackers@freebsd.org, security@freebsd.org, current@freebsd.org, julian@freebsd.org, kaveman@magna.com.au Subject: Re: ipfilter-proff.shar.gz From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" X-Email: jhs@freebsd.org, Fallback: jhs@gil.physik.rwth-aachen.de X-Organization: Vector Systems Ltd. X-Mailer: EXMH 1.6.7, PGP PGP key on web X-Web: http://www.freebsd.org/~jhs/ X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Tel: Phone +49.89.268616, Fax +49.89.2608126, Data +49.89.26023276 In-reply-to: Your message of "Wed, 09 Apr 1997 09:24:07 +1000." <199704082329.QAA10393@freefall.freebsd.org> Date: Wed, 09 Apr 1997 19:33:37 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Darren Reed > > ... IP Filter ... > > I recall the last email I read on the subject was from Julian, > > Darren Which Julian ? Loads of them in FreeBSD :-) Chronologically : ... Julian.Elischer: julian@freebsd.org Julian Stacey jhs@freebsd.org Julian.Jenkins: kaveman@magna.com.au julianj@vast.unsw.edu.au Julian.Assange: proff@suburbia.net proff@iq.org If anyone is _The_ Julian in FreeBSD, it'd be Elischer, (he was first here, & is julian@freebsd.org). I had assumed you meant Elischer, but Gary Jennejohn (there are at least 3 Garys) told me you didn't mean Elischer, so maybe you meant Jenkins or Assange, or another new Julian ? Whilst every last Julian is undoubtedly a great boon & blessing to FreeBSD ;-)) it does seem the name is more common than one might imagine, so please folks, append at least a Surname initial to the Julians, Thanks :-) A.N.Other Julian .... Julian S. -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Apr 9 13:55:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA17283 for current-outgoing; Wed, 9 Apr 1997 13:55:02 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17274 for ; Wed, 9 Apr 1997 13:54:58 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id NAA18435 for ; Wed, 9 Apr 1997 13:54:57 -0700 (PDT) Message-Id: <199704092054.NAA18435@austin.polstra.com> To: current@freebsd.org Subject: Heads up: building shared libraries Date: Wed, 09 Apr 1997 13:54:56 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Later this week, I am going to commit a change to that will eliminate the need for the CPLUSPLUSLIB variable in the makefiles for C++ shared libraries. The change will cause /usr/lib/c++rt0.o to be linked into all shared libraries, even non-C++ ones. It is essential that an up-to-date version of c++rt0.o be installed in /usr/lib before building any shared libraries using the new method. I have already committed the new version of that (src/lib/csu/i386/c++rt0.c version 1.8). The change won't cause any problems for normal "make world" runs. The top-level Makefile takes care to install an up-to-date c++rt0.o before building any shared libraries. If you manually build a new shared library using the new but the old c++rt0.o, it will cause problems. They are not compile-time or link-time errors, but rather subtle run-time errors. (Usually, messages from malloc saying that free() was called on an already-freed block.) So ... don't do that. :-) -- 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 Wed Apr 9 14:19:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA18684 for current-outgoing; Wed, 9 Apr 1997 14:19:00 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA18671 for ; Wed, 9 Apr 1997 14:18:54 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id WAA09834 for freebsd.org!freebsd-current; Wed, 9 Apr 1997 22:15:02 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 9 Apr 1997 22:11:28 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199704071450.PAA19003@isbalham.ist.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 9 Apr 1997 22:09:05 +0100 To: freebsd-current From: Bob Bishop Subject: Watching paint dry Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently wrote: >Is it me, or have things slowed down recently? I'm finding make world of ctm >src-cur 2829 with a kernel of the same vintage taking something like three >times as long as I'd expect. That was a gross underestimate. I gave up after c.96 hours (normally takes about 12). Just to check, I tried again with a kernel dating from around 26 Mar, and got through in 12 hours. Anyone know what's going on? I'm moving up to CTM src-cur 2835 now, can I expect this to have gone away? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Wed Apr 9 14:24:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA19122 for current-outgoing; Wed, 9 Apr 1997 14:24:09 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA19117 for ; Wed, 9 Apr 1997 14:24:05 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id RAA03239; Wed, 9 Apr 1997 17:22:24 -0400 (EDT) Date: Wed, 9 Apr 1997 17:22:23 -0400 (EDT) From: James FitzGibbon To: Erik Manders cc: freebsd-current@freebsd.org Subject: Re: NFS + Quotas in current In-Reply-To: <199704091651.SAA17508@charm.il.ft.hse.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > James FitzGibbon is said to have made the following statement: > > > > Is support for quotas over NFS new in 3.0-current ? I can do it on one of > > my machines (which is 2.2, upgraded to -current, and has had world made > > on it in the last two weeks), but it doesn't work with a 2.2.1R machine or > > a 3.0-970209-SNAP machine freshly installed (having recompiled the kernel > > with "options QUOTA"). > > > > If it is new in the last two months, how stable is it ? I'd appreciate > > thoughts on the doability of it being merged into RELENG_2_2, or if a diff > > applied to the /src/sys/nfs tree would be even feasible. > > > > Thanks. > > > > -- > > j. > On Wed, 9 Apr 1997, Erik Manders wrote: > Well, I have got it to work, mostly. The only thing I haven't gotten to work > yet is the ability to set quotas over the net. This will require kernel hacking > Quotas seems to be stable to the extent that you can export a filesystem with > quotas and have the server enforce them. It is even possble to have quota(1) > report quota and limit data to a remote user, but only if the quota file is > in the mounted filesystem and rpc.rquotad is running on the fileserver. This is with a 2.2.x client ? When I try to mount with quotas : [nebula:james] ~ (66) # mount -t nfs -o rw,noatime,userquota,-b nexis.net:/usr/home /mnt I get this: nfs: -o userquota: option not supported This is with 2.2.1R. Any ideas ? -- j. From owner-freebsd-current Wed Apr 9 15:18:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA21626 for current-outgoing; Wed, 9 Apr 1997 15:18:53 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA21613 for ; Wed, 9 Apr 1997 15:18:50 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id PAA17358 for ; Wed, 9 Apr 1997 15:25:12 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id SAA16185; Wed, 9 Apr 1997 18:18:13 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id SAA12523; Wed, 9 Apr 1997 18:18:14 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id RAA17807; Wed, 9 Apr 1997 17:18:28 -0500 (CDT) Date: Wed, 9 Apr 1997 17:18:28 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199704092218.RAA17807@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@freebsd.org Subject: FYI: sb16 stopped working X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was up and running current effective March 14th, but reverted to 2.2.1 while the X server was failing to run. I'm back now, but find that my OEM SB16 no longer runs. VoxWare Sound Driver:3.0-beta-950506 (Sun Feb 5 14:38:12 EST 1995 freebsd-hackers@freefall.cdrom.com) Config options: ffffffff Installed drivers: Type 1: OPL-2/OPL-3 FM Type 5: Roland MPU-401 Type 2: SoundBlaster Type 6: SoundBlaster16 Type 7: SB16 MIDI Card config: SoundBlaster at 0x220 irq 10 drq 1 Roland MPU-401 at 0x330 irq 9 drq 0 SoundBlaster16 at 0xffffffff irq 65535 drq 5 (SB16 MIDI at 0x330 irq 65535 drq 4294967295) OPL-2/OPL-3 FM at 0x200 irq 65535 drq 4294967295 Audio devices: Synth devices: 0: Yamaha OPL-3 Midi devices: Timers: 0: System Timer Mixers: 0: SoundBlaster 2.2.1: Apr 2 22:04:16 compound /kernel: sb0 at 0x220 irq 10 drq 1 on isa Apr 2 22:04:16 compound /kernel: sb0: Apr 2 22:04:16 compound /kernel: sbmidi0 not found at 0x330 Apr 2 22:04:16 compound /kernel: sbxvi0 at 0x0 drq 5 on isa Apr 2 22:04:16 compound /kernel: sbxvi0: Apr 2 22:04:16 compound /kernel: mpu0 at 0x330 irq 9 drq 0 on isa Apr 2 22:04:16 compound /kernel: mpu0 not probed due to irq conflict with mse0 at 9 Apr 2 22:04:16 compound /kernel: opl0 at 0x200 on isa Apr 2 22:04:16 compound /kernel: opl0: 3.0 current: Apr 5 12:31:25 compound /cur: sb0 at 0x220-0x22f irq 10 drq 1 on isa Apr 5 12:31:25 compound /cur: sb0: Apr 5 12:31:25 compound /cur: sbmidi0 not found at 0x330 Apr 5 12:31:25 compound /cur: sbxvi0 at 0x220-0x22f irq 10 drq 5 on isa Apr 5 12:31:25 compound /cur: sbxvi0 not probed due to I/O address conflict with sb0 at 0x220 Apr 5 12:31:25 compound /cur: mpu0 at 0x330 irq 9 drq 0 on isa Apr 5 12:31:25 compound /cur: mpu0 not probed due to irq conflict with mse0 at 9 Apr 5 12:31:26 compound /cur: opl0 at 0x200-0x203 on isa Apr 5 12:31:26 compound /cur: opl0: From owner-freebsd-current Wed Apr 9 16:27:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA26476 for current-outgoing; Wed, 9 Apr 1997 16:27:26 -0700 (PDT) Received: from zeppelin.net (obiwan@zeppelin.net [206.170.177.52]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26451 for ; Wed, 9 Apr 1997 16:27:14 -0700 (PDT) Received: (from obiwan@localhost) by zeppelin.net (8.8.5/8.8.5) id QAA13023; Wed, 9 Apr 1997 16:29:29 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-beta [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199704092218.RAA17807@compound.east.sun.com> Date: Wed, 09 Apr 1997 16:26:09 -0700 (PDT) From: Josh Howard To: Anthony.Kimball@East.Sun.COM Subject: RE: FYI: sb16 stopped working Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 09-Apr-97 Tony Kimball wrote: > >I was up and running current effective March 14th, but reverted to >2.2.1 while the X server was failing to run. I'm back now, but find >that my OEM SB16 no longer runs. >2.2.1: [....] The config is a little different, I would suggest rereading LINT in -current. At least that was my problem when I noticed the same symptoms. http://pobox.com/~kenobi/ The steady state of disks is full. -- Ken Thompson From owner-freebsd-current Wed Apr 9 17:41:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA29994 for current-outgoing; Wed, 9 Apr 1997 17:41:28 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA29989 for ; Wed, 9 Apr 1997 17:41:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA28370; Thu, 10 Apr 1997 10:11:04 +0930 (CST) From: Michael Smith Message-Id: <199704100041.KAA28370@genesis.atrad.adelaide.edu.au> Subject: Re: make world In-Reply-To: <9704091455.AA18339@gf006e0.seag.fingerhut.com> from Bruce Albrecht at "Apr 9, 97 09:55:39 am" To: Bruce.Albrecht@seag.fingerhut.com (Bruce Albrecht) Date: Thu, 10 Apr 1997 10:11:03 +0930 (CST) Cc: chuckr@glue.umd.edu, freebsd-current@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Albrecht stands accused of saying: > > It seems to me that after Perl 5.004 is released (probably within the > next 3 weeks), it should be made the standard Perl for FreeBSD-current. > Perl 4.036 isn't supported by the perl porters, and Perl 5 is way cooler > and much more powerful. We have been waiting for these three weeks for about eight months now. When it's ready, there are plenty of people will commit it. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Apr 9 17:52:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA00649 for current-outgoing; Wed, 9 Apr 1997 17:52:19 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA00644 for ; Wed, 9 Apr 1997 17:52:16 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id RAA19325; Wed, 9 Apr 1997 17:51:51 -0700 (PDT) To: "Louis A. Mamakos" cc: David Nugent , Chuck Robey , FreeBSD current Subject: Re: make world In-reply-to: Your message of "Wed, 09 Apr 1997 12:59:33 EDT." <199704091659.MAA19396@whizzo.transsys.com> Date: Wed, 09 Apr 1997 17:51:51 -0700 Message-ID: <19321.860633511@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've had very mixed results getting stuff merged into the tree - the > Brooktree 848 changes I've done got merged because someone with commit > privs was also actively involved in the process. The socket-timestamp > kernel code got in. But after two attempts to get simple changes to > /usr/sbin/moused in (which would keep my mouse working when doing > 'make world', sigh) and a one-liner to > /usr/src/sbin/mount/getmntopts.c to fix a bug introduced recently > introduced that breaks cfs, I dunno what to think. This happens sometimes and the best I can recommend to *anyone* faced with desultory response from -committers is to follow this track: 1. Submit the bug fix or enhancement with send-pr, waiting for your acknowledgement and assigned tracking number to be returned. 2. Wait about a week. If it's committed, go back to step 1 for your next change. If not, go to step 3. 3. Send mail to committers@freebsd.org saying "Hey, is *anyone* going to commit PR#123456 or at least tell me why it's bogus? Please? Thanks!" 4. Wait a week. If it's still not committed, send mail to jkh@freebsd.org saying "HEY, THEY'RE IGNORING ME OVER THERE, HELP JORDAN!!" and I will step in and try to see that it's resolved somehow, even if I have to commit it myself. I hate to see this happen to anyone. Jordan From owner-freebsd-current Wed Apr 9 18:04:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA01672 for current-outgoing; Wed, 9 Apr 1997 18:04:42 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA01656 for ; Wed, 9 Apr 1997 18:04:38 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA28585; Thu, 10 Apr 1997 10:33:06 +0930 (CST) From: Michael Smith Message-Id: <199704100103.KAA28585@genesis.atrad.adelaide.edu.au> Subject: Re: nfs problem In-Reply-To: <199704091926.MAA07377@phaeton.artisoft.com> from Terry Lambert at "Apr 9, 97 12:26:47 pm" To: terry@lambert.org (Terry Lambert) Date: Thu, 10 Apr 1997 10:33:05 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, wollman@khavrinen.lcs.mit.edu, jdp@polstra.com, bemfica@militzer.me.tuns.ca, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > > > Huh? -P is meant to represent a 'better' thing than a meaningful keyword? > > That's crazy 8( > > The -P is a getopt(3) parseable command line option for mount_nfs. I thought we were looking for "better" not "easier for the parser". *shrug* Let's not start fighting about getopt just now. > And yes, making the fstab options match the command line options for > the mount for the FS type specified in the fstab *is* a better thing. > > You might successfully argue for "-o resvport,nosuid" or whatever as > a syntax change for "mount_nfs"... You mean, un-deprecate them? TBH I prefer these (from mount_nfs(8)) : Historic -o options Use of these options is deprecated, they are only mentioned here for compatibility with historic versions of mount_nfs. bg Same as -b. conn Same as -c. dumbtimer Same as -d. intr Same as -i. kerb Same as -K. nfsv3 Same as -3. rdirplus Same as -l. mntudp Same as -U. resvport Same as -P. seqpacket Same as -p. nqnfs Same as -q. soft Same as -s. tcp Same as -T. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Apr 9 18:09:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA01935 for current-outgoing; Wed, 9 Apr 1997 18:09:06 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA01926 for ; Wed, 9 Apr 1997 18:09:02 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id SAA20936; Wed, 9 Apr 1997 18:08:56 -0700 (PDT) Message-Id: <199704100108.SAA20936@austin.polstra.com> To: Michael Smith cc: current@FreeBSD.ORG Subject: Re: nfs problem In-reply-to: Your message of "Thu, 10 Apr 1997 10:33:05 +0930." <199704100103.KAA28585@genesis.atrad.adelaide.edu.au> References: <199704100103.KAA28585@genesis.atrad.adelaide.edu.au> Date: Wed, 09 Apr 1997 18:08:56 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > TBH I prefer these (from mount_nfs(8)) : > > Historic -o options > > Use of these options is deprecated, they are only mentioned here > for compatibility with historic versions of mount_nfs. > > bg Same as -b. > > conn Same as -c. > > dumbtimer Same as -d. > [...] Me too! There are too many possible options for the single-letter flags to be mnemonic. And, the "historic" -o options are the only ones that amd understands. -- 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 Wed Apr 9 19:32:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA05978 for current-outgoing; Wed, 9 Apr 1997 19:32:38 -0700 (PDT) Received: from mailsrv.cc.utsunomiya-u.ac.jp (mailsrv.cc.utsunomiya-u.ac.jp [160.12.200.20]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05969 for ; Wed, 9 Apr 1997 19:32:36 -0700 (PDT) Received: from zodiac.mech.utsunomiya-u.ac.jp (YWBEeSj21ZYhBCsOntHG7skLvZV/d7Pt@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by mailsrv.cc.utsunomiya-u.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl4) with ESMTP id LAA01822; Thu, 10 Apr 1997 11:31:39 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA07337; Thu, 10 Apr 1997 11:36:11 +0900 (JST) Message-Id: <199704100236.LAA07337@zodiac.mech.utsunomiya-u.ac.jp> To: "Louis A. Mamakos" cc: freebsd-current@freefall.freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: moused enhancement (was: Re: make world) In-reply-to: Your message of "Wed, 09 Apr 1997 12:59:33 -0400." <199704091659.MAA19396@whizzo.transsys.com> References: <19970409032758.35315@usn.blaze.net.au> <199704091659.MAA19396@whizzo.transsys.com> Date: Thu, 10 Apr 1997 11:36:10 +0900 From: Kazutaka YOKOTA Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I've had very mixed results getting stuff merged into the tree - the >Brooktree 848 changes I've done got merged because someone with commit >privs was also actively involved in the process. The socket-timestamp >kernel code got in. But after two attempts to get simple changes to >/usr/sbin/moused in (which would keep my mouse working when doing >'make world', sigh) and a one-liner to Although I am not responsible for `moused', I have been aware of your GlidePoint patch. (I may be guilty, but only *partially* :-) I looked at your patch (PR bin/3028) and understand that it adds ALPS GlidePoint support. XFree86 also has GlidePoint support (since 3.1.2F?). As far as I can understand, your support code and XFree86's are not functionally equivalent. Yours is for GlidePoint on the PS/2 mouse port and XFree86's code is for GlidePoint attached to a serial port. Your code makes `moused' pretend the left mouse button is pressed when the user `taps' GlidePoint's surface, whereas XFree86 regards the `tap' action as the fourth button press. Ok, we can argue that it isn't necessary that `moused' and XFree86 behave in exactly the same way. But, isn't this difference rather confusing to the user? In order for a user to use GlidePoint with X, he has to choose: 1) attach GlidePoint to the PS/2 mouse port and specify `glidepoint' to `moused'. Tell X, in XF86Config, to access `/dev/sysmouse' and the protocol is `mousesystems'. 2) attach GlidePoint to a serial port, don't use `moused'. specify `glidepoint' in XF86Config. If GlidePoint is attached to a serial port and the user intends to use `moused', he shouldn't specify `glidepoint' as the protocol, rather he has to choose `microsoft' or `mouseman'. `Tap' feature won't be recognized in this case. If GlidePoint is attached to the PS/2 mouse port and the user don't use `moused', he shouldn't specify `glidepoint' as the protocol in XF86Config, rather he has to say `ps/2'. `Tap' feature won't be recognized in this case. IMHO, more complete support for GlidePoint is necessary for both `moused' and XFree86. One solution on `moused's side may be to incorporate serial GlidePoint support code from XFree86 into `moused'. What do you think? One other thing. ALPS produces several models of GlidePoint devices. I know that some models (such as Desktop GlidePoint model GP101) need specific support code, but the others (such as GlidePoint model GP001) don't; they internally generate a left button press event when the user taps the surface of the device. Kazu From owner-freebsd-current Wed Apr 9 20:04:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA07853 for current-outgoing; Wed, 9 Apr 1997 20:04:19 -0700 (PDT) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07766; Wed, 9 Apr 1997 20:03:57 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970116) with ESMTP id XAA12591; Wed, 9 Apr 1997 23:02:58 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id XAA03578; Wed, 9 Apr 1997 23:02:57 -0400 (EDT) To: "Julian H. Stacey" cc: Darren Reed , proff@suburbia.net, hackers@freebsd.org, security@freebsd.org, current@freebsd.org, julian@freebsd.org, kaveman@magna.com.au Reply-To: chat@freebsd.org From: "Gary Palmer" Subject: Re: ipfilter-proff.shar.gz In-reply-to: Your message of "Wed, 09 Apr 1997 19:33:37 +0200." <199704091733.TAA08869@desk.jhs.no_domain> Date: Wed, 09 Apr 1997 23:02:57 -0400 Message-ID: <3575.860641377@orion.webspan.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Julian H. Stacey" wrote in message ID <199704091733.TAA08869@desk.jhs.no_domain>: > I had assumed you meant Elischer, but Gary Jennejohn (there are at least > 3 Garys) told me you didn't mean Elischer, so maybe you meant Jenkins or > Assange, or another new Julian ? There are WAY more than three Garys these, days, and everytime I read a mail which blames a `Gary' for something I have to stop and think ``was that me??''. It's enough to make a guy insecure! (Reply-To: set appropriately) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Wed Apr 9 20:34:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA09459 for current-outgoing; Wed, 9 Apr 1997 20:34:31 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA09454 for ; Wed, 9 Apr 1997 20:34:26 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.5/8.7.3) with SMTP id XAA21958; Wed, 9 Apr 1997 23:33:58 -0400 (EDT) Message-Id: <199704100333.XAA21958@whizzo.transsys.com> To: Kazutaka YOKOTA cc: freebsd-current@freefall.freebsd.org From: "Louis A. Mamakos" Subject: Re: moused enhancement (was: Re: make world) References: <19970409032758.35315@usn.blaze.net.au> <199704091659.MAA19396@whizzo.transsys.com> <199704100236.LAA07337@zodiac.mech.utsunomiya-u.ac.jp> In-reply-to: Your message of "Thu, 10 Apr 1997 11:36:10 +0900." <199704100236.LAA07337@zodiac.mech.utsunomiya-u.ac.jp> Date: Wed, 09 Apr 1997 23:33:57 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I looked at your patch (PR bin/3028) and understand that it adds ALPS > GlidePoint support. XFree86 also has GlidePoint support (since > 3.1.2F?). As far as I can understand, your support code and XFree86's > are not functionally equivalent. Yes, this seems to be the case. I had already made similar changes to this in the X server and moused seems to be the better approach - it didn't require that I have to figure out how to build X. > Yours is for GlidePoint on the PS/2 mouse port and XFree86's code is > for GlidePoint attached to a serial port. Your code makes `moused' > pretend the left mouse button is pressed when the user `taps' > GlidePoint's surface, whereas XFree86 regards the `tap' action as the > fourth button press. I was hopeful when I heard about the glidepoint support in XFree86, but frankly, having the tap gesture appear as a fourth mouse button didn't solve a problem - it simply created another one. Frankly, X already has way too many degrees of freedom and configurability as a substitute for user interface design, and this was another chrome plated knob. All I wanted was to have the stupid point device *work*; I lost my will to dick around with X trying to get CAPS-LOCK/CTRL keys to do the right thing. I just wanted it to work.. > Ok, we can argue that it isn't necessary that `moused' and XFree86 > behave in exactly the same way. But, isn't this difference rather > confusing to the user? In order for a user to use GlidePoint with X, > he has to choose: > > 1) attach GlidePoint to the PS/2 mouse port and specify `glidepoint' > to `moused'. Tell X, in XF86Config, to access `/dev/sysmouse' and > the protocol is `mousesystems'. > 2) attach GlidePoint to a serial port, don't use `moused'. specify > `glidepoint' in XF86Config. > > If GlidePoint is attached to a serial port and the user intends to use > `moused', he shouldn't specify `glidepoint' as the protocol, rather he > has to choose `microsoft' or `mouseman'. `Tap' feature won't be > recognized in this case. > If GlidePoint is attached to the PS/2 mouse port and the user don't > use `moused', he shouldn't specify `glidepoint' as the protocol in > XF86Config, rather he has to say `ps/2'. `Tap' feature won't be > recognized in this case. > > IMHO, more complete support for GlidePoint is necessary for both > `moused' and XFree86. One solution on `moused's side may be to > incorporate serial GlidePoint support code from XFree86 into `moused'. > What do you think? Alternatively, we ought to recommend that moused *always* be used as a default configuration, and leave one less XF86Config option to worry about. In that way, you'll get the syscons support along for free. I claim that having the XFree86 behaviour of a 4th mouse button doesn't actually help most users. They just want the pointing device to do the right thing. I suppose (eeek!) an option could be added to configure what the tap gesture should do. > One other thing. ALPS produces several models of GlidePoint devices. > I know that some models (such as Desktop GlidePoint model GP101) need > specific support code, but the others (such as GlidePoint model GP001) > don't; they internally generate a left button press event when the > user taps the surface of the device. Certainly the earlier ALPS 3 button devices, including the "standalone" laptop pointing device and their combined keyboard/pointing device have a seperate tap gesture. I haven't encountered the other ones myself. louie From owner-freebsd-current Wed Apr 9 20:47:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA10672 for current-outgoing; Wed, 9 Apr 1997 20:47:20 -0700 (PDT) Received: from sed.cs.fsu.edu (sed.cs.fsu.edu [128.186.121.157]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA10663 for ; Wed, 9 Apr 1997 20:47:09 -0700 (PDT) Received: (from uh@localhost) by sed.cs.fsu.edu (8.8.5/8.7.3) id XAA01762 for current@freebsd.org; Wed, 9 Apr 1997 23:47:08 -0400 (EDT) From: Gang-Ryung Uh Message-Id: <199704100347.XAA01762@sed.cs.fsu.edu> Subject: netscape4 To: current@freebsd.org Date: Wed, 9 Apr 1997 23:47:07 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I am running a kernel that was built using the src as current Jan 28 1997. Recently, I installed new netscape from the port netscape4. But, I can not run any applet on this fancy looking new web browser. Am I missing something? (as always I did before) Thanks. Regards, Gang-Ryung Uh (uh@cs.fsu.edu) From owner-freebsd-current Wed Apr 9 21:08:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA12142 for current-outgoing; Wed, 9 Apr 1997 21:08:50 -0700 (PDT) Received: from mailsrv.cc.utsunomiya-u.ac.jp (mailsrv.cc.utsunomiya-u.ac.jp [160.12.200.20]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA12137 for ; Wed, 9 Apr 1997 21:08:47 -0700 (PDT) Received: from zodiac.mech.utsunomiya-u.ac.jp (g66yspyXXlRAtC8/3YCVfwz4HcTmKUpC@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by mailsrv.cc.utsunomiya-u.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl4) with ESMTP id NAA02109; Thu, 10 Apr 1997 13:07:47 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id NAA08728; Thu, 10 Apr 1997 13:12:19 +0900 (JST) Message-Id: <199704100412.NAA08728@zodiac.mech.utsunomiya-u.ac.jp> To: "Louis A. Mamakos" cc: freebsd-current@freefall.freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: moused enhancement (was: Re: make world) In-reply-to: Your message of "Wed, 09 Apr 1997 23:33:57 -0400." <199704100333.XAA21958@whizzo.transsys.com> References: <19970409032758.35315@usn.blaze.net.au> <199704091659.MAA19396@whizzo.transsys.com> <199704100236.LAA07337@zodiac.mech.utsunomiya-u.ac.jp> <199704100333.XAA21958@whizzo.transsys.com> Date: Thu, 10 Apr 1997 13:12:18 +0900 From: Kazutaka YOKOTA Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> IMHO, more complete support for GlidePoint is necessary for both >> `moused' and XFree86. One solution on `moused's side may be to >> incorporate serial GlidePoint support code from XFree86 into `moused'. >> What do you think? > >Alternatively, we ought to recommend that moused *always* be used as a >default configuration, and leave one less XF86Config option to worry about. >In that way, you'll get the syscons support along for free. > >I claim that having the XFree86 behaviour of a 4th mouse button >doesn't actually help most users. They just want the pointing device >to do the right thing. I suppose (eeek!) an option could be added to >configure what the tap gesture should do. I agree that regarding `tap' as the fourth button action is stupid. But, I still think the serial GlidePoint should be supported too if the PS/2 GlidePoint is to be supported and if we are to make `moused' standard. Otherwise, `moused' is good only for the PS/2 GlidePoint owners, and useless for the serial GlidePoint owners... How about importing the serial GlidePoint I/O code from XFree86, but make `tap' a left button down action rather than the fourth button? Kazu From owner-freebsd-current Wed Apr 9 21:13:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA12453 for current-outgoing; Wed, 9 Apr 1997 21:13:58 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA12448 for ; Wed, 9 Apr 1997 21:13:55 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.5/8.7.3) with SMTP id AAA22167; Thu, 10 Apr 1997 00:13:17 -0400 (EDT) Message-Id: <199704100413.AAA22167@whizzo.transsys.com> To: Kazutaka YOKOTA cc: freebsd-current@freefall.freebsd.org From: "Louis A. Mamakos" Subject: Re: moused enhancement (was: Re: make world) References: <19970409032758.35315@usn.blaze.net.au> <199704091659.MAA19396@whizzo.transsys.com> <199704100236.LAA07337@zodiac.mech.utsunomiya-u.ac.jp> <199704100333.XAA21958@whizzo.transsys.com> <199704100412.NAA08728@zodiac.mech.utsunomiya-u.ac.jp> In-reply-to: Your message of "Thu, 10 Apr 1997 13:12:18 +0900." <199704100412.NAA08728@zodiac.mech.utsunomiya-u.ac.jp> Date: Thu, 10 Apr 1997 00:13:17 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I agree that regarding `tap' as the fourth button action is stupid. > But, I still think the serial GlidePoint should be supported too if > the PS/2 GlidePoint is to be supported and if we are to make `moused' > standard. Otherwise, `moused' is good only for the PS/2 GlidePoint > owners, and useless for the serial GlidePoint owners... Oh, I see now. Yes, I agree. > How about importing the serial GlidePoint I/O code from XFree86, but > make `tap' a left button down action rather than the fourth button? This sounds like a good plan. I haven't look for this lately, but is the XFree86 release with the glidepoint support out of beta now with source available? I haven't looked in a while. louie From owner-freebsd-current Wed Apr 9 23:22:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA18454 for current-outgoing; Wed, 9 Apr 1997 23:22:27 -0700 (PDT) Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA18433; Wed, 9 Apr 1997 23:22:21 -0700 (PDT) Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.8.5) id XAA17951; Wed, 9 Apr 1997 23:22:18 -0700 (PDT) Received: from localhost by newport.ece.uci.edu (8.8.5) id XAA19967; Wed, 9 Apr 1997 23:22:16 -0700 (PDT) Message-Id: <199704100622.XAA19967@newport.ece.uci.edu> To: bugs@freebsd.org cc: current@freebsd.org Subject: NFS/mmap freeze in 2.2R Date: Wed, 09 Apr 1997 23:22:15 -0700 From: Steven Wallace Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have discovered how to freeze the system over an NFS mounted filesystem. If you map a file over NFS read/write and shared, write to the area in memory, and then have another program read that nfs file, the system will freeze. The freeze is kindof wierd though. It appears that the kernel is still running somehow. I can change the sysconts vty's but typing and all other processes are frozen and not running. The system will get error messages (sometimes) ever 30 seconds when it syncs. They report: Apr 9 23:05:35 sdw /kernel: vnode_pager_putpages: I/O error 13 Apr 9 23:05:35 sdw /kernel: vnode_pager_putpages: residual I/O 65536 at 496 I have made life easy for you, Mr. VM master, by providing a program to freeze your system, guaranteed. Here is the program to freeze your system: /* Instructions to freeze system: cc -O crashme.c -o crashme cd /nfs_mounted_dir crashme & cat nfsfile > /dev/null ------------SYSTEM FREEZE----------------- */ #include #include #include #include #include #include #include #define RAMSIZE_DEF 0x220000 #define SLEEP 1 static int mapmem(int fd, long start, long size, long offset, int w) { caddr_t maddr, addr; off_t moffset = (off_t)offset; const int flags = /* MAP_FIXED |*/ MAP_SHARED; const int prot = PROT_READ | (w ? PROT_WRITE : 0); maddr = (caddr_t)(start); addr = (caddr_t)mmap(maddr, (size_t)size, prot, flags, fd, moffset); if((int)addr == -1) { fprintf(stderr, "mapmem at addr=%6x size=%5x offset=%5x: %s\n", maddr, size, offset, strerror(errno)); } return((int)addr); } int main(int argc, char *argv[]) { int fdram; int dummy; long size = RAMSIZE_DEF; char *data; char *map; fdram = open("nfsfile", O_RDWR | O_CREAT, 0666); if(fdram < 0) { perror("open nfsfile"); return(fdram); } if(lseek(fdram, 0, SEEK_END) <= 0) { if(lseek(fdram, size - sizeof(dummy), SEEK_SET) < 0) perror("lseek ram"); if(write(fdram, &dummy, sizeof(dummy)) < 0) perror("write ram"); } map = (char *)mapmem(fdram, 0, size, 0, 1); if((int)map == -1) return -1; data = (char *)malloc(size); strcpy(data, "begin of data"); data[size - 1] = 'Z'; if(!data) { printf("malloc failed\n"); return -1; } while(1) { sleep(SLEEP); memcpy(map, data, size); printf("data written to mapped file\n"); } } From owner-freebsd-current Thu Apr 10 02:36:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA25978 for current-outgoing; Thu, 10 Apr 1997 02:36:05 -0700 (PDT) Received: from charm.il.ft.hse.nl (erik@charm.il.ft.hse.nl [145.85.127.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA25973 for ; Thu, 10 Apr 1997 02:36:01 -0700 (PDT) Received: (from erik@localhost) by charm.il.ft.hse.nl (8.8.5/8.7.3) id LAA06963; Thu, 10 Apr 1997 11:35:48 +0200 (CEST) From: Erik Manders Message-Id: <199704100935.LAA06963@charm.il.ft.hse.nl> Subject: Re: NFS + Quotas in current In-Reply-To: from James FitzGibbon at "Apr 9, 97 05:22:23 pm" To: james@nexis.net (James FitzGibbon) Date: Thu, 10 Apr 1997 11:35:48 +0200 (MEST) Cc: freebsd-current@freebsd.org X-Location: Somewhere in The Netherlands X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk James FitzGibbon is said to have made the following statement: > > James FitzGibbon is said to have made the following statement: > > > > > > Is support for quotas over NFS new in 3.0-current ? I can do it > > > on one of my machines (which is 2.2, upgraded to -current, and > > > has had world made on it in the last two weeks), but it doesn't > > > work with a 2.2.1R machine or a 3.0-970209-SNAP machine freshly > > > installed (having recompiled the kernel with "options QUOTA"). > > > > > > If it is new in the last two months, how stable is it ? I'd > > > appreciate thoughts on the doability of it being merged into > > > RELENG_2_2, or if a diff applied to the /src/sys/nfs tree would be > > > even feasible. > > > > > > Thanks. > > > > > > -- > > > j. > > > On Wed, 9 Apr 1997, Erik Manders wrote: > > > Well, I have got it to work, mostly. The only thing I haven't gotten > > to work yet is the ability to set quotas over the net. This will > > require kernel hacking Quotas seems to be stable to the extent that > > you can export a filesystem with quotas and have the server enforce > > them. It is even possble to have quota(1) report quota and limit > > data to a remote user, but only if the quota file is in the mounted > > filesystem and rpc.rquotad is running on the fileserver. > > This is with a 2.2.x client ? When I try to mount with quotas : > > [nebula:james] ~ (66) # mount -t nfs -o rw,noatime,userquota,-b > nexis.net:/usr/home /mnt > > I get this: > > nfs: -o userquota: option not supported > This is true, sort of. Mount_nfs doesn't support the userquota option. I'm running a slightly patched 2.2.1-RELEASE and my setup is as follows: Server /etc/exports: /var/mail -maproot=root:wheel nfscharm nfstop Server /etc/fstab: /dev/sd1a /var/mail ufs rw,userquota=/usr/quotas/mail.user 1 2 Client /etc/fstab: nfs:/var/mail /var/mail nfs rw,intr 0 0 Both machines have quota code enabled in the kernel, but only the server has check_quotas=YES in /etc/sysconfig. In addition, the server runs rpc.rquotad. I added it to /etc/rc.local, but you can have inetd run it. You basically let the fileserver enforce quotas and tell the clients when limits have been reached. rpc.rquotad runs to let quota(1) work. Quota(1) is NFS-aware and will automatically ask the server's rpc.rquotad for quota information on any NFS filesystems it encounters. However, remember that the 2.2.1-RELEASE rpc.rquotad will only work if the quotafiles are on their relevant filesystems (see my last post for a fix). Also keep in mind that edquota(8) and friends will only work on the fileserver since quotactl(2) hasn't been implemented for NFS. Sample output from quota(1): Disk quotas for user erik (uid 100): Filesystem blocks quota limit grace files quota limit grace /var/mail 88 1024 2048 1 0 0 Something on this subject should be put into the FAQ or the handbook. Hope this helps, Erik Manders erik@il.ft.hse.nl -- It is by caffeine alone that I set my mind in motion; it is by the cans of cola that the thoughts acquire speed, hands acquire shaking, the shaking becomes a warning; it is with caffeine alone that I set my mind in motion. --from the movie `Dune', edited From owner-freebsd-current Thu Apr 10 03:24:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA27503 for current-outgoing; Thu, 10 Apr 1997 03:24:04 -0700 (PDT) Received: from utserv.mcc.ac.uk (utserv.mcc.ac.uk [130.88.200.6]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA27433 for ; Thu, 10 Apr 1997 03:23:31 -0700 (PDT) Received: from albatross.mcc.ac.uk by utserv.mcc.ac.uk with SMTP (PP); Thu, 10 Apr 1997 11:22:45 +0100 Received: (from ip@localhost) by albatross.mcc.ac.uk (8.8.5/8.6.12) id LAA15505 for freebsd-current@freebsd.org; Thu, 10 Apr 1997 11:22:36 +0100 (BST) From: Ian Pallfreeman Message-Id: <199704101022.LAA15505@albatross.mcc.ac.uk> Subject: Re: wdx interrupt timeouts (fwd) To: freebsd-current@freebsd.org Date: Thu, 10 Apr 1997 11:22:35 +0100 (BST) Reply-To: ip@mcc.ac.uk X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've switched this to the current list, since it's worse than I thought. Doug White wrote: > On Tue, 8 Apr 1997, Ian Pallfreeman wrote: > > Apr 8 15:07:54 lurch /kernel: wd3: interrupt timeout: > > Apr 8 15:07:54 lurch /kernel: wd3: status 58 error 0 > > [...] > Do you have IDE spindown enabled? That's what it looks like happened-- > wd3 spun down and the system tried to poke it, and it took a little too > long to come back to ready. Nothing to worry about. Nothing to do with IDE spindown (had a couple of other folks suggesting that). This happens under heavy load -- e.g. mirroring the ftp archive. The problem has become worse over the last few days. First it changed to: Apr 9 14:06:48 lurch /kernel: wd3e: reverting to non-multi sector mode reading fsbn 4213504 of 4213456-4213518 (wd3 bn 4213504; cn 4180 tn 1 sn 1)wd3: status 59 error 40 Apr 9 14:06:55 lurch /kernel: wd3e: hard error reading fsbn 4213506 of 4213456-4213518 (wd3 bn 4213506; cn 4180 tn 1 sn 3)wd3: status 59 error 40 followed by a hang. Now it's giving a panic (integer divide overflow) whenever I try to read that block. Managed to get a dump, but kgdb won't tell me anything (can't find kstack). I guess I'll reformat the disks eventually; anybody got any other ideas? Ian. From owner-freebsd-current Thu Apr 10 04:03:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA29050 for current-outgoing; Thu, 10 Apr 1997 04:03:52 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29034 for ; Thu, 10 Apr 1997 04:03:33 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id HAA06126; Thu, 10 Apr 1997 07:01:33 -0400 (EDT) Date: Thu, 10 Apr 1997 07:01:33 -0400 (EDT) From: James FitzGibbon To: Erik Manders cc: freebsd-current@freebsd.org Subject: Re: NFS + Quotas in current In-Reply-To: <199704100935.LAA06963@charm.il.ft.hse.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Apr 1997, Erik Manders wrote: > > This is with a 2.2.x client ? When I try to mount with quotas : > > > > [nebula:james] ~ (66) # mount -t nfs -o rw,noatime,userquota,-b > > nexis.net:/usr/home /mnt > > > > I get this: > > > > nfs: -o userquota: option not supported > > > This is true, sort of. Mount_nfs doesn't support the userquota option. > > I'm running a slightly patched 2.2.1-RELEASE and my setup is as follows: > > Server /etc/exports: > /var/mail -maproot=root:wheel nfscharm nfstop > > Server /etc/fstab: > /dev/sd1a /var/mail ufs rw,userquota=/usr/quotas/mail.user 1 2 > > Client /etc/fstab: > nfs:/var/mail /var/mail nfs rw,intr 0 0 > > Both machines have quota code enabled in the kernel, but only the > server has check_quotas=YES in /etc/sysconfig. In addition, the server > runs rpc.rquotad. I added it to /etc/rc.local, but you can have inetd > run it. > > You basically let the fileserver enforce quotas and tell the clients > when limits have been reached. rpc.rquotad runs to let quota(1) work. I've tried doing this, but the server never tells the clients when the quotas has been reached. I can run quota(1) no problems, but if I have a 5mb quota on a directory and I try to write more than 5mb from the client, the client *thinks* everything went just fine. Meanwhile, the server just stopped writing data at 5mb. Can you run a really quick test on your setup to verify if I've done something wrong ? Set up a small (<10mb quota) on the server. On the client, run a little perl program like this : --START-- #!/usr/bin/perl # for( $i=0; ; $i++ ) { print "This is test line $i\n"; } ---END--- >From the client, run that redirected to a file on the quota'd filesystem. At the same time, run a 'tail -f' on the same file from the server. When I did this, I could watch the quota go up from either machine. The tail process showed new lines being added (the increasing number obviously being the indicator. However, when the quota limit was reached, the client never knew. It just kept on writing happy as can be. The tail process just stopped. No new lines were being committed to disk. If your results differ in this respect, I'd really appreciate knowing. At least then I know it's possible, and that I can with effort get it to work. If not, I have to re-think what I'm trying to do. > Something on this subject should be put into the FAQ or the handbook. Agreed. Thanks again for your help. -- j. From owner-freebsd-current Thu Apr 10 04:25:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA29827 for current-outgoing; Thu, 10 Apr 1997 04:25:54 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29821 for ; Thu, 10 Apr 1997 04:25:47 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.5) id VAA09335 for freebsd-current@freebsd.org; Thu, 10 Apr 1997 21:25:43 +1000 Received: by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) id VAA04747; Thu, 10 Apr 1997 21:16:41 +1000 (EST) Date: Thu, 10 Apr 1997 21:16:41 +1000 (EST) From: Stephen McKay Message-Id: <199704101116.VAA04747@ogre.dtir.qld.gov.au> To: freebsd-current@freebsd.org cc: Stephen McKay Subject: Re: Hang during NFS stress test X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stephen McKay wrote: >Setup: 386DX20 with 8Mb ram running 2.2.1 (or very close) continually >copying files from a 486DX33 running 2.1.7 back to the same mount point >via TCP NFS. After two days (continuous copying) it has locked up. It >still responds to pings, will switch virtual consoles, and I can get into >ddb, but nothing else. > >Ddb shows that the machine is stuck in idle_loop(), and no processes are >on the run queue (whichqs == 0), but ps (ddb command) shows a number of >processes which are not waiting on anything. For example, there are 3 >getty's on the syscons virtual screens, and only one has non-zero wchan >(probably because I hit enter a few times on some screens to see if I >could wake them up). > >The only unusual wchan is swapper waiting on swinuw (which must be from >pmap_swapin_proc). Other processes are in nfsidl, pause, wait, ttyin, etc. Cpl and ipending look fine: just my console tty interrupt showing. The clock is still updating 'time'. There are no processes on any run queue because only one runnable process is in core (P_INMEM). That process is in the process of exiting (P_WEXIT). In fact, it seems to have got all the way through exit1() and cpu_exit() into cpu_switch() which would have dropped us in idle() because everyone else is asleep. Oh, and the parent is pseudo-awake: that is it is not waiting, but is not actually in core, so it must have been woken by the exiting process near the end of exit1(). Process 0 (swapper) is waiting (on "swinuw", presumably in pmap_swapin_proc) for some process's upages to unbusy. The processes not waiting on anything are not runnable because they are swapped out. The swapper hasn't managed to swap any of them in because it is stuck. Which process has marked that upage busy? No idea. So, what went wrong? Not a clue. This is Hard Stuff(tm) and I need some help here. I can keep this hung machine hung for another day at least, but can't guarantee any more. And it writes bad core dumps. Sigh. Unfortunately the serious VM folks might be somewhat disinterested because manipulations of upages have changed in -current (in a broad way I haven't examined yet), and presumably any bugs would have moved or mutated. Any pointers or DDB tips gratefully accepted. Stephen. From owner-freebsd-current Thu Apr 10 04:25:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA29845 for current-outgoing; Thu, 10 Apr 1997 04:25:58 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29822 for ; Thu, 10 Apr 1997 04:25:49 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.5) id VAA09315; Thu, 10 Apr 1997 21:25:34 +1000 Received: by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) id UAA04428; Thu, 10 Apr 1997 20:47:35 +1000 (EST) Date: Thu, 10 Apr 1997 20:47:35 +1000 (EST) From: Stephen McKay Message-Id: <199704101047.UAA04428@ogre.dtir.qld.gov.au> To: Steven Wallace cc: freebsd-current@freebsd.org, syssgm@dtir.qld.gov.au Subject: Re: NFS/mmap freeze in 2.2R X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steven Wallace wrote: >I have discovered how to freeze the system over an NFS mounted filesystem. >If you map a file over NFS read/write and shared, write >to the area in memory, and then have another program read that nfs file, >the system will freeze. The freeze is kindof wierd though. >It appears that the kernel is still running somehow. >I can change the sysconts vty's but typing and all other processes >are frozen and not running. This is awfully similar to my problem (see my NFS stress test post of a few days ago). I'm about to follow-up on that thread. Take a peek. Stephen. From owner-freebsd-current Thu Apr 10 06:09:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA04116 for current-outgoing; Thu, 10 Apr 1997 06:09:06 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04107; Thu, 10 Apr 1997 06:09:00 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id IAA00366; Thu, 10 Apr 1997 08:08:52 -0500 (EST) From: "John S. Dyson" Message-Id: <199704101308.IAA00366@dyson.iquest.net> Subject: Re: NFS/mmap freeze in 2.2R In-Reply-To: <199704100622.XAA19967@newport.ece.uci.edu> from Steven Wallace at "Apr 9, 97 11:22:15 pm" To: swallace@ece.uci.edu (Steven Wallace) Date: Thu, 10 Apr 1997 08:08:52 -0500 (EST) Cc: bugs@freebsd.org, current@freebsd.org Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have discovered how to freeze the system over an NFS mounted filesystem. > If you map a file over NFS read/write and shared, write > to the area in memory, and then have another program read that nfs file, > the system will freeze. The freeze is kindof wierd though. > It appears that the kernel is still running somehow. > I can change the sysconts vty's but typing and all other processes > are frozen and not running. > Sounds like a recursive VFS locking problem or somesuch. Thanks for the report, and will look at it ASAP. John From owner-freebsd-current Thu Apr 10 07:21:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA08031 for current-outgoing; Thu, 10 Apr 1997 07:21:23 -0700 (PDT) Received: from mailsrv.cc.utsunomiya-u.ac.jp (mailsrv.cc.utsunomiya-u.ac.jp [160.12.200.20]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA08019 for ; Thu, 10 Apr 1997 07:21:15 -0700 (PDT) Received: from zodiac.mech.utsunomiya-u.ac.jp (veKbI6+T/ErxEqsNpzqaVTvWnxU4/9xv@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by mailsrv.cc.utsunomiya-u.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl4) with ESMTP id XAA05233; Thu, 10 Apr 1997 23:21:07 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id XAA14661; Thu, 10 Apr 1997 23:25:37 +0900 (JST) Message-Id: <199704101425.XAA14661@zodiac.mech.utsunomiya-u.ac.jp> To: "Louis A. Mamakos" cc: freebsd-current@freefall.freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: moused enhancement (was: Re: make world) In-reply-to: Your message of "Thu, 10 Apr 1997 00:13:17 -0400." <199704100413.AAA22167@whizzo.transsys.com> References: <19970409032758.35315@usn.blaze.net.au> <199704091659.MAA19396@whizzo.transsys.com> <199704100236.LAA07337@zodiac.mech.utsunomiya-u.ac.jp> <199704100333.XAA21958@whizzo.transsys.com> <199704100412.NAA08728@zodiac.mech.utsunomiya-u.ac.jp> <199704100413.AAA22167@whizzo.transsys.com> Date: Thu, 10 Apr 1997 23:25:35 +0900 From: Kazutaka YOKOTA Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> How about importing the serial GlidePoint I/O code from XFree86, but >> make `tap' a left button down action rather than the fourth button? > >This sounds like a good plan. I haven't look for this lately, but >is the XFree86 release with the glidepoint support out of beta now >with source available? I haven't looked in a while. Yes, it's in XFree86 3.2. The file in question is xc/programs/Xserver/hw/xfree86/xf86_Mouse.c. Kazu From owner-freebsd-current Thu Apr 10 07:30:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA08435 for current-outgoing; Thu, 10 Apr 1997 07:30:04 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA08401 for ; Thu, 10 Apr 1997 07:29:59 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id HAA00725 for ; Thu, 10 Apr 1997 07:29:59 -0700 (PDT) Message-Id: <199704101429.HAA00725@austin.polstra.com> To: current@freebsd.org Subject: ahc crashes 2.2-STABLE machine during dump to DAT tape Date: Thu, 10 Apr 1997 07:29:58 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In an up-to-date RELENG_2_2 kernel (CVSupped last night: 9 April, 20:45 PDT), the system cannot make it thru a backup without crashing. It hangs with the following messages on the screen: ahc0:A:0: no active SCB for reconnecting target - issuing ABORT SAVED_TCL == 0x0 ahc0:A:0: Warning - unknown message received from target (0xff). Rejecting ahc_intr: seqint, intstat == 0xc1, scsisigi = 0xf6 ahc0:A:0: Target did not send an IDENTIFY message. LASTPHASE = 0x0, SAVED_TCL == 0x0 ahc0: Issued Channel A Bus Reset. 4 SCBs aborted At that point the machine is unresponsive to its keyboard, and I have to press the Big Red Button. This problem is not new with last night's kernel -- I've been seeing it for a couple of weeks, maybe longer. (I haven't been trying backups very often lately.) Before I upgraded to 2.2, this problem never appeared on the machine. The kernel has DDB configured into it, and it's built with debugging symbols. But since it doesn't panic, I haven't been able to get into the debugger to get a stack trace. I should mention that the CD-ROM drive has been added in the past few weeks. It's a replacement for one that crapped out. It seems to work fine. I can't remember whether these crashes were happening before I put it in or not. Maybe it's a clue. Generally when these crashes occur, the machine is idle except for the dump in progress. I'm attaching my dmesg.boot and config files. I'd be happy to run some tests if there's anything that would help to track it down. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth =============================================================================== Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-STABLE #1: Wed Apr 9 22:41:13 PDT 1997 jdp@austin.polstra.com:/home/src/sys/compile/AUSTIN CPU: Pentium (89.81-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30703616 (29984K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 vga0 rev 0 int a irq 11 on pci0:13 ahc0 rev 3 int a irq 10 on pci0:15 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "SEAGATE ST31230N 0510" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1010MB (2069860 512 byte sectors) ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "SEAGATE ST15150N 0017" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 4095MB (8388315 512 byte sectors) (ahc0:3:0): "TEAC CD-ROM CD-56S 1.0B" type 5 removable SCSI 2 cd0(ahc0:3:0): CD-ROM cd present [313642 x 2048 byte records] (ahc0:4:0): "ARCHIVE Python XXXXX-XXX 4.AF" type 1 removable SCSI 2 st0(ahc0:4:0): Sequential-Access density code 0x13, 512-byte blocks, write-enabled de0 rev 17 int a irq 9 on pci0:16 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:0d:15:c6 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> mse0 at 0x23c irq 5 on isa sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 7 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvi0: sbmidi0 at 0x330 on isa opl0 at 0x388 on isa opl0: WARNING: / was not properly dismounted. =============================================================================== # # AUSTIN config file # machine "i386" cpu "I586_CPU" # aka Pentium(tm) ident AUSTIN maxusers 10 config kernel root on sd0 options "CHILD_MAX=128" options "OPEN_MAX=128" options "COMPAT_43" options USER_LDT #allow user-level control of i386 ldt options SYSVSHM options SYSVSEM options SYSVMSG options DDB options DDB_UNATTENDED options KTRACE #kernel tracing options UCONSOLE options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device snp 3 #Snoop device - to look at pty/vty/etc. pseudo-device tun 1 #Tunnel driver (user process ppp) options FFS #Fast filesystem options NFS #Network File System options "CD9660" #ISO 9660 filesystem options FDESC #File descriptor filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options "NSWAPDEV=4" options "SCSI_DELAY=5" #Boot time SCSI settling time in seconds controller scbus0 #base SCSI code device sd0 #SCSI disks device st0 #SCSI tapes device cd0 #SCSI CD-ROMs pseudo-device pty 64 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) controller isa0 options "AUTO_EOI_1" device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 device mse0 at isa? port 0x23c tty irq 5 vector mseintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr controller snd0 device sb0 at isa? port 0x220 irq 7 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 controller pci0 controller ahc0 options AHC_TAGENABLE #Tagged queuing options AHC_ALLOW_MEMIO device de0 =============================================================================== From owner-freebsd-current Thu Apr 10 08:53:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA13962 for current-outgoing; Thu, 10 Apr 1997 08:53:39 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA13957 for ; Thu, 10 Apr 1997 08:53:36 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id IAA10722 for ; Thu, 10 Apr 1997 08:53:36 -0700 (PDT) Date: Thu, 10 Apr 1997 08:53:34 -0700 (PDT) From: Tom Bartol To: current@freebsd.org Subject: Error in make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I just got the following error in the middle of make world on 4/9/97: cc -O2 -m486 -pipe -I/usr/src/gnu/usr.bin/gdb/gdb -I/usr/include/readline -I/usr/src/gnu/usr.bin/gdb/gdb/../bfd -DNO_MMALLOC -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/include/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/bfd/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/libiberty/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/config/. -DHAVE_CONFIG_H -c /usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/opcodes/disassemble.c make: don't know how to make bfd. Stop *** Error code 2 Has anyone else seen this or is it just me? My make world on 4/8/97 succeeded. Thanks, Tom From owner-freebsd-current Thu Apr 10 10:32:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA19196 for current-outgoing; Thu, 10 Apr 1997 10:32:59 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA19183; Thu, 10 Apr 1997 10:32:43 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id KAA00860; Thu, 10 Apr 1997 10:15:36 -0700 (PDT) Message-ID: <334D2033.2781E494@whistle.com> Date: Thu, 10 Apr 1997 10:15:31 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: chat@freebsd.org CC: "Julian H. Stacey" , Darren Reed , proff@suburbia.net, hackers@freebsd.org, security@freebsd.org, current@freebsd.org, julian@freebsd.org, kaveman@magna.com.au Subject: Re: ipfilter-proff.shar.gz References: <3575.860641377@orion.webspan.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gary Palmer wrote: > > "Julian H. Stacey" wrote in message ID > <199704091733.TAA08869@desk.jhs.no_domain>: > > I had assumed you meant Elischer, but Gary Jennejohn (there are at least > > 3 Garys) told me you didn't mean Elischer, so maybe you meant Jenkins or > > Assange, or another new Julian ? > > There are WAY more than three Garys these, days, and everytime I read > a mail which blames a `Gary' for something I have to stop and think > ``was that me??''. It's enough to make a guy insecure! > > (Reply-To: set appropriately) > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info I've never been in a group with mor ethan 1 julian before.. it's kind of unique to have 3.5 of us floating around.. :) julian (E) From owner-freebsd-current Thu Apr 10 10:38:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA19655 for current-outgoing; Thu, 10 Apr 1997 10:38:58 -0700 (PDT) Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA19609; Thu, 10 Apr 1997 10:38:26 -0700 (PDT) Received: from dvl-1.pathlink.com (dvl-1.pathlink.com [204.30.237.241]) by dopey.pathlink.com (8.8.5/8.8.4) with SMTP id KAA25163; Thu, 10 Apr 1997 10:48:53 -0700 (PDT) Message-Id: <199704101748.KAA25163@dopey.pathlink.com> To: dyson@freebsd.org Subject: Re: NFS/mmap freeze in 2.2R Cc: freebsd-current@freebsd.org From: kachun@zippo.com (Kachun Lee) Date: Thu, 10 Apr 97 10:38:21 PST X-Mailer: WinVN 0.99.8 (beta 2) In-Reply-To: <5iism1$s6l@newsrv.zippo.com> References: <199704100622.XAA19967@newport.ece.uci.edu> from Steven Wallace at "Apr 9, 97 11:22:15 pm" <5iism1$s6l@newsrv.zippo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <5iism1$s6l@newsrv.zippo.com>, you say... > >> >> I have discovered how to freeze the system over an NFS mounted filesystem. >> If you map a file over NFS read/write and shared, write >> to the area in memory, and then have another program read that nfs file, >> the system will freeze. The freeze is kindof wierd though. >> It appears that the kernel is still running somehow. >> I can change the sysconts vty's but typing and all other processes >> are frozen and not running. >> >Sounds like a recursive VFS locking problem or somesuch. Thanks for the >report, and will look at it ASAP. > >John While you are at it, maybe, you want to check this out also. We noticed we have been getting these messages: ------------- Apr 8 23:21:12 lois /kernel: vnode_pager_getpages: I/O read error Apr 8 23:21:12 lois /kernel: vm_fault: pager input (probably hardware) error, P ID 11987 failure Apr 8 23:21:12 lois /kernel: pid 11987 (in.nnrpd), uid 7003: exited on signal 11 -------------- since 2.2R or later with our NFS mounted news servers. They appeared at the NFS clients during news was expiring at the NFS server. That leaded me to believe that the message was triggered when someone was reading an article while the NFS server removed it - both systems kept running though. From owner-freebsd-current Thu Apr 10 13:52:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA29434 for current-outgoing; Thu, 10 Apr 1997 13:52:17 -0700 (PDT) Received: from ki1.chemie.fu-berlin.de (ki1.chemie.fu-berlin.de [160.45.24.21]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA29426 for ; Thu, 10 Apr 1997 13:52:14 -0700 (PDT) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Thu, 10 Apr 97 22:52 MEST Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-current@freebsd.org id ; Thu, 10 Apr 97 22:52 MET DST Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA01412; Thu, 10 Apr 97 21:52:02 +0200 Date: Thu, 10 Apr 97 21:52:02 +0200 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9704101952.AA01412@wavehh.hanse.de> To: jdp@polstra.COM Cc: freebsd-current@freebsd.org Subject: Re: ahc crashes 2.2-STABLE machine during dump to DAT tape Newsgroups: hanse-ml.freebsd.current References: <199704101429.HAA00725@austin.polstra.com> Reply-To: cracauer@wavehh.hanse.de Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Postra wrote: >In an up-to-date RELENG_2_2 kernel (CVSupped last night: 9 April, >20:45 PDT), the system cannot make it thru a backup without crashing. >It hangs with the following messages on the screen: >ahc0:A:0: no active SCB for reconnecting target - issuing ABORT >SAVED_TCL == 0x0 >ahc0:A:0: Warning - unknown message received from target (0xff). Rejecting >ahc_intr: seqint, intstat == 0xc1, scsisigi = 0xf6 >ahc0:A:0: Target did not send an IDENTIFY message. LASTPHASE = 0x0, SAVED_TCL == 0x0 >ahc0: Issued Channel A Bus Reset. 4 SCBs aborted >At that point the machine is unresponsive to its keyboard, and I have to >press the Big Red Button. The same happened for me two times with 2.2.1-release. >This problem is not new with last night's kernel -- I've been seeing >it for a couple of weeks, maybe longer. (I haven't been trying >backups very often lately.) Before I upgraded to 2.2, this problem >never appeared on the machine. Same here. >The kernel has DDB configured into it, and it's built with debugging >symbols. But since it doesn't panic, I haven't been able to get into >the debugger to get a stack trace. My kernel doesn't have DDB or -g. >I should mention that the CD-ROM drive has been added in the past >few weeks. It's a replacement for one that crapped out. It seems >to work fine. I can't remember whether these crashes were happening >before I put it in or not. Maybe it's a clue. Generally when these >crashes occur, the machine is idle except for the dump in progress. These chrashes appeared in 2.2 (or 2.2.1? not sure) without any changes without any changes to the SCSI setup, not even reconnecting drives. I have : 2x ahc (one older, one "utra") narrow 1x "NEC D3825 0410" type 0 fixed SCSI 2 2x (one on each ahc) "Quantum XP34300 81HB" (Altas 1 4 GB) >I'm attaching my dmesg.boot and config files. I'd be happy to run >some tests if there's anything that would help to track it down. As a hint, I'm pretty sure the problem is load/timing-related. My two hangs appeared when I had the disks very active on an asynchronous mounted ccd over the two atlas drives (no, I didn't loose any data :-), driven by a PPRO-200. I'll file a proper PR when the problem can't be fixed instantly, I just wanted to add to John's report. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin_Cracauer@wavehh.hanse.de http://cracauer.cons.org Fax.: +4940 5228536 "As far as I'm concerned, if something is so complicated that you can't ex- plain it in 10 seconds, then it's probably not worth knowing anyway"- Calvin From owner-freebsd-current Thu Apr 10 14:26:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA01435 for current-outgoing; Thu, 10 Apr 1997 14:26:24 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA01426; Thu, 10 Apr 1997 14:26:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA09726; Thu, 10 Apr 1997 14:06:08 -0700 From: Terry Lambert Message-Id: <199704102106.OAA09726@phaeton.artisoft.com> Subject: Re: NFS/mmap freeze in 2.2R To: kachun@zippo.com (Kachun Lee) Date: Thu, 10 Apr 1997 14:06:08 -0700 (MST) Cc: dyson@freebsd.org, freebsd-current@freebsd.org In-Reply-To: <199704101748.KAA25163@dopey.pathlink.com> from "Kachun Lee" at Apr 10, 97 10:38:21 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > While you are at it, maybe, you want to check this out also. We noticed we have > been getting these messages: > > ------------- > Apr 8 23:21:12 lois /kernel: vnode_pager_getpages: I/O read error > Apr 8 23:21:12 lois /kernel: vm_fault: pager input (probably hardware) error, > P > ID 11987 failure > Apr 8 23:21:12 lois /kernel: pid 11987 (in.nnrpd), uid 7003: exited on signal > 11 > -------------- > > since 2.2R or later with our NFS mounted news servers. They appeared at > the NFS clients during news was expiring at the NFS server. That leaded > me to believe that the message was triggered when someone was reading > an article while the NFS server removed it - both systems kept running > though. Are you running the INN msync() patch? There is an error in the INN use of mapped files when the file is extended. The problem occurs when: 1) The file is not a multiple of a page size in length 2) The file is mmap'ed, and the last page is zero filled 3) The file is extended 4) The mmap'ed area is accessed between the previous end of the file and the page boundry following the end of the file, without an intervening msync(). This is a bug in INN's use of the mmap() interface, not a FreeBSD bug. (If you are running the msync() patch, then never mind). 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 Thu Apr 10 16:08:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA07142 for current-outgoing; Thu, 10 Apr 1997 16:08:17 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA07135 for ; Thu, 10 Apr 1997 16:08:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA10021 for current@freebsd.org; Thu, 10 Apr 1997 15:48:44 -0700 From: Terry Lambert Message-Id: <199704102248.PAA10021@phaeton.artisoft.com> Subject: WHY? ...non-use of TAILQ macros... To: current@freebsd.org Date: Thu, 10 Apr 1997 15:48:44 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On the theory that the TAILQ_xxx macros were being avoided and the queue elemments themselves directly refernce for No Good Reason(tm), I just compiled the following: ----------------------------------------------------------------------------- #include struct node { int element; int filler; int what; }; struct node bob = { 1, 2, 3 }; main() { int j; j = bob.what; /* 111*/ printf( "j = %d\n", j); j = (&bob)->what; /* 222*/ printf( "j = %d\n", j); } ----------------------------------------------------------------------------- And got: ----------------------------------------------------------------------------- .file "try.c" gcc2_compiled.: ___gnu_compiled_c: .globl _bob .data .align 2 .type _bob,@object .size _bob,12 _bob: .long 1 .long 2 .long 3 .text LC0: .ascii "j = %d\12\0" .align 2 .globl _main .type _main,@function _main: pushl %ebp movl %esp,%ebp subl $4,%esp call ___main movl _bob+8,%eax ; 1 movl %eax,-4(%ebp) ; 1 movl -4(%ebp),%eax ; 1 pushl %eax ; 1 pushl $LC0 ; 1 call _printf ; 1 addl $8,%esp ; 1 movl _bob+8,%eax ; 2 movl %eax,-4(%ebp) ; 2 movl -4(%ebp),%eax ; 2 pushl %eax ; 2 pushl $LC0 ; 2 call _printf ; 2 addl $8,%esp ; 2 L5: leave ret Lfe1: .size _main,Lfe1-_main ----------------------------------------------------------------------------- ... in other words, the references: (x).y and (x)->y Don't somehow generate different code. I'm wondering why the following aren't written using the macros (macro versions are shown one line below): ----------------------------------------------------------------------------- kern_lockf.c: while (ltmp = overlap->lf_blkhd.tqh_first) { while (ltmp = TAILQ_FIRST(&overlap->lf_blkhd)) { kern_lockf.c: while (wakelock = listhead->lf_blkhd.tqh_first) { while (wakelock = TAILQ_FIRST(&listhead->lf_blkhd)) { kern_lockf.c: if (lock->lf_blkhd.tqh_first) if (!TAILQ_EMPTY(&lock->lf_blkhd)) kern_lockf.c: printf(" block 0x%x\n", lock->lf_blkhd.tqh_first); printf(" block 0x%x\n", TAILQ_FIRST(&lock->lf_blkhd)); kern_lockf.c: for (blk = lf->lf_blkhd.tqh_first; blk; for (blk = TAILQ_FIRST(&lf->lf_blkhd); blk; kern_lockf.c: if (blk->lf_blkhd.tqh_first) if (!TAILQ_EMPTY(&blk->lf_blkhd)) kern_synch.c: for (p = qp->tqh_first; p != NULL; p = p->p_procq.tqe_next) { for (p = TAILQ_FIRST(qp); p != NULL; p = TAILQ_NEXT(p, p_procq)) { kern_synch.c: for (p = qp->tqh_first; p != NULL; p = p->p_procq.tqe_next) { for (p = TAILQ_FIRST(qp); p != NULL; p = TAILQ_NEXT(p, p_procq)) { uipc_socket.c: if (so->so_comp.tqh_first == NULL) if (TAILQ_EMPTY(&so->so_comp)) uipc_socket.c: for (sp = so->so_incomp.tqh_first; sp != NULL; sp = sonext) { for (sp = TAILQ_FIRST(&so->so_incomp); sp != NULL; sp = sonext) { uipc_socket.c: for (sp = so->so_comp.tqh_first; sp != NULL; sp = sonext) { for (sp = TAILQ_FIRST(&so->so_comp); sp != NULL; sp = sonext) { uipc_syscalls.c: if ((head->so_state & SS_NBIO) && head->so_comp.tqh_first == NULL) { if ((head->so_state & SS_NBIO) && TAILQ_EMPTY(&head->so_comp)) { uipc_syscalls.c: while (head->so_comp.tqh_first == NULL && head->so_error == 0) { while (TAILQ_EMPTY(&head->so_comp) && head->so_error == 0) { uipc_syscalls.c: so = head->so_comp.tqh_first; so = TAILQ_FIRST(&head->so_comp); vfs_cache.c: ((ncp = nclruhead.tqh_first) == NULL || ((ncp = TAILQ_FIRST(&nclruhead)) == NULL || vfs_cache.c: } else if (ncp = nclruhead.tqh_first) { } else if (ncp = TAILQ_FIRST(&nclruhead)) { vfs_subr.c: vnode_free_list.tqh_first == NULL) { TAILQ_EMPTY(&vnode_free_list)) { vfs_subr.c: for (vp = vnode_free_list.tqh_first; for (vp = TAILQ_FIRST(&vnode_free_list); vfs_subr.c: vnode_free_list.tqh_first != vp) { TAILQ_FIRST(&vnode_free_list) != vp) { ----------------------------------------------------------------------------- It seems to me that queue structure contents should only ever be referenced or mainipulated in the context of queue structure reference macros... One would also think that there would be: #define TAILQ_ENUM(elm,head,field) \ for( elm = (head)->tqh_first; elm != NULL; elm = (elm)->field.tqe_next) In queue.h to change: kern_synch.c: for (p = qp->tqh_first; p != NULL; p = p->p_procq.tqe_next) { Into: TAILQ_ENUM(p, qp, p_procq) { 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 Thu Apr 10 16:31:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA08577 for current-outgoing; Thu, 10 Apr 1997 16:31:24 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA08569 for ; Thu, 10 Apr 1997 16:31:22 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id QAA05373 for ; Thu, 10 Apr 1997 16:37:17 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id TAA19518; Thu, 10 Apr 1997 19:30:41 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id TAA11889; Thu, 10 Apr 1997 19:30:39 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id SAA00884; Thu, 10 Apr 1997 18:30:37 -0500 (CDT) Date: Thu, 10 Apr 1997 18:30:37 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199704102330.SAA00884@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@freebsd.org Subject: FYI: cd won't play X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cdrom_freebsd.c`cdrom_play_track: ioctl fd=4 tag=CDIOCPLAYMSF data=( start <0:2:0> end <255:59:74> ) perror output is: ioctl(cdromplaymsftrk): Invalid argument The start/end frame coordinates don't seem to matter. Lots of these: Apr 10 18:20:33 compound /kernel: cd0: RECOVERED ERROR info?:f0840513 csi:84,5,13,f0 asc:0,c0 Vendor Specific ASCQ field replaceable unit: 83 sks:c4,ed ... Apr 10 18:24:12 compound /kernel: cd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB Apr 10 18:24:16 compound last message repeated 12 times This is a difference between a March 14 and April 8 current kernel. From owner-freebsd-current Thu Apr 10 16:34:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA08917 for current-outgoing; Thu, 10 Apr 1997 16:34:19 -0700 (PDT) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA08907 for ; Thu, 10 Apr 1997 16:34:15 -0700 (PDT) Received: from socrate.gea.org (ts1port3d.masternet.it [194.184.65.25]) by scotty.masternet.it (8.8.5/8.7.3) with SMTP id BAA02045 for ; Fri, 11 Apr 1997 01:34:52 GMT Message-ID: <334D8670.41C67EA6@scotty.masternet.it> Date: Fri, 11 Apr 1997 02:31:44 +0200 From: Beck Peccoz Amedeo X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: src-cur 2836 doesn't make world Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk cc -O -I/usr/src/gnu/usr.bin/gdb/gdb -I/usr/include/readline -I/usr/src/gnu/usr.bin/gdb/gdb/../bfd -DNO_MMALLOC -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/include/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/bfd/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/libiberty/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/config/. -DHAVE_CONFIG_H -c /usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/opcodes/disassemble.c make: don't know how to make bfd. Stop *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- Beck-Peccoz Amedeo Tel. +39-125-366302 GEA Software S.r.l. Fax. +39-125-366415 gea@scotty.masternet.it GSM +39-347-3837526 From owner-freebsd-current Thu Apr 10 16:46:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA10180 for current-outgoing; Thu, 10 Apr 1997 16:46:05 -0700 (PDT) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA10164 for ; Thu, 10 Apr 1997 16:45:59 -0700 (PDT) Received: from tuna.ProGroup.COM (tuna.progroup.com [206.24.122.5]) by seabass.progroup.com (8.7.5/8.7.3) with SMTP id QAA00677; Thu, 10 Apr 1997 16:44:46 -0700 (PDT) Received: by tuna.ProGroup.COM (SMI-8.6/SMI-SVR4) id QAA04627; Thu, 10 Apr 1997 16:46:20 -0700 From: craig@tuna.progroup.com (Craig W. Shaver) Message-Id: <199704102346.QAA04627@tuna.ProGroup.COM> Subject: Re: NFS/mmap freeze in 2.2R To: terry@lambert.org (Terry Lambert) Date: Thu, 10 Apr 1997 16:46:19 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: <199704102106.OAA09726@phaeton.artisoft.com> from "Terry Lambert" at Apr 10, 97 02:06:08 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > While you are at it, maybe, you want to check this out also. We noticed we have del ... > > Are you running the INN msync() patch? There is an error in the INN > use of mapped files when the file is extended. The problem occurs when: > > 1) The file is not a multiple of a page size in length > 2) The file is mmap'ed, and the last page is zero filled > 3) The file is extended > 4) The mmap'ed area is accessed between the previous end of the > file and the page boundry following the end of the file, without > an intervening msync(). > > This is a bug in INN's use of the mmap() interface, not a FreeBSD bug. > > > (If you are running the msync() patch, then never mind). Terry, where can I find the INN msync() patch, and what version of INN is it to be applied against? Thanks, -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-current Thu Apr 10 17:22:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA13392 for current-outgoing; Thu, 10 Apr 1997 17:22:49 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA13378 for ; Thu, 10 Apr 1997 17:22:46 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id UAA05660; Thu, 10 Apr 1997 20:21:58 -0400 (EDT) Date: Thu, 10 Apr 1997 20:21:58 -0400 (EDT) From: Garrett Wollman Message-Id: <199704110021.UAA05660@khavrinen.lcs.mit.edu> To: Terry Lambert Cc: current@FreeBSD.ORG Subject: WHY? ...non-use of TAILQ macros... In-Reply-To: <199704102248.PAA10021@phaeton.artisoft.com> References: <199704102248.PAA10021@phaeton.artisoft.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > I'm wondering why the following aren't written using the macros (macro > versions are shown one line below): > kern_lockf.c: while (ltmp = overlap->lf_blkhd.tqh_first) { 1. Because they are a FreeBSD (actually Justin Gibbs) invention. Obviously, original Berkeley code will not use a macro that Berkeley didn't have. 2. Because they are unnecessary. > #define TAILQ_ENUM(elm,head,field) \ > for( elm = (head)->tqh_first; elm != NULL; elm = (elm)->field.tqe_next) Go read style(9) and then say that with a straight face. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Apr 10 17:57:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA15269 for current-outgoing; Thu, 10 Apr 1997 17:57:33 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15262 for ; Thu, 10 Apr 1997 17:57:29 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id TAA01363; Thu, 10 Apr 1997 19:56:16 -0500 (EST) From: "John S. Dyson" Message-Id: <199704110056.TAA01363@dyson.iquest.net> Subject: Re: NFS/mmap freeze in 2.2R In-Reply-To: <199704102346.QAA04627@tuna.ProGroup.COM> from "Craig W. Shaver" at "Apr 10, 97 04:46:19 pm" To: craig@tuna.progroup.com (Craig W. Shaver) Date: Thu, 10 Apr 1997 19:56:16 -0500 (EST) Cc: terry@lambert.org, current@freebsd.org Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > While you are at it, maybe, you want to check this out also. We noticed we have > del ... > > > > Are you running the INN msync() patch? There is an error in the INN > > use of mapped files when the file is extended. The problem occurs when: > > Note that I am very busy right now on FreeBSD things, but will be able to fix it (the kernel VM bug that you are speaking of) this weekend. John From owner-freebsd-current Thu Apr 10 17:59:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA15357 for current-outgoing; Thu, 10 Apr 1997 17:59:45 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA15346 for ; Thu, 10 Apr 1997 17:59:40 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA10331; Thu, 10 Apr 1997 17:39:39 -0700 From: Terry Lambert Message-Id: <199704110039.RAA10331@phaeton.artisoft.com> Subject: Re: WHY? ...non-use of TAILQ macros... To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Thu, 10 Apr 1997 17:39:39 -0700 (MST) Cc: terry@lambert.org, current@FreeBSD.ORG In-Reply-To: <199704110021.UAA05660@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Apr 10, 97 08:21:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm wondering why the following aren't written using the macros (macro > > versions are shown one line below): > > > kern_lockf.c: while (ltmp = overlap->lf_blkhd.tqh_first) { > > 1. Because they are a FreeBSD (actually Justin Gibbs) invention. > Obviously, original Berkeley code will not use a macro that Berkeley > didn't have. > > 2. Because they are unnecessary. Well, that begs the question of qhy they are being used in declarations and elsewhere, then, doesn't it? > > #define TAILQ_ENUM(elm,head,field) \ > > for( elm = (head)->tqh_first; elm != NULL; elm = (elm)->field.tqe_next) > > Go read style(9) and then say that with a straight face. Well, *despite* the fact that there is still no style man page on freefall... If the tailq's are a FreeBSD invention, they should either be universally applied, or not applied at all. Style is quite binary about this kind of thing. And it's not like there is a CSRG any more. I was interested in macro versions to allow conditional compilation of locking code for mutex locking queue reference and modification (the reasoning should be obvious). 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 Thu Apr 10 18:03:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA15758 for current-outgoing; Thu, 10 Apr 1997 18:03:05 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA15745 for ; Thu, 10 Apr 1997 18:02:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA10356; Thu, 10 Apr 1997 17:43:25 -0700 From: Terry Lambert Message-Id: <199704110043.RAA10356@phaeton.artisoft.com> Subject: Re: NFS/mmap freeze in 2.2R To: craig@tuna.progroup.com (Craig W. Shaver) Date: Thu, 10 Apr 1997 17:43:25 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <199704102346.QAA04627@tuna.ProGroup.COM> from "Craig W. Shaver" at Apr 10, 97 04:46:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > (If you are running the msync() patch, then never mind). > > Terry, where can I find the INN msync() patch, and what version of INN > is it to be applied against? Ugh. That's a nice hard question. I typically don't run INN. Your best bet would be to check the -current list archives for the keywords "INN" and "msync". Barring that, if you could wait, you should be able to take John Dyson up on his offer to fix the VM problem. PS: If the problem *is* cured by the msync() patch, I think the only VM problem is in the way the error is reported as a FreeBSD error instead of an application error, and John may do well to fix *that*, rather than to compromise the mmap() behaviour for the benefit INN... 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 Thu Apr 10 18:14:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA16800 for current-outgoing; Thu, 10 Apr 1997 18:14:57 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA16794 for ; Thu, 10 Apr 1997 18:14:54 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id VAA05848; Thu, 10 Apr 1997 21:14:06 -0400 (EDT) Date: Thu, 10 Apr 1997 21:14:06 -0400 (EDT) From: Garrett Wollman Message-Id: <199704110114.VAA05848@khavrinen.lcs.mit.edu> To: Terry Lambert Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: WHY? ...non-use of TAILQ macros... In-Reply-To: <199704110039.RAA10331@phaeton.artisoft.com> References: <199704110021.UAA05660@khavrinen.lcs.mit.edu> <199704110039.RAA10331@phaeton.artisoft.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: >> > kern_lockf.c: while (ltmp = overlap->lf_blkhd.tqh_first) { >> 2. Because they are unnecessary. > Well, that begs the question of qhy they are being used in declarations > and elsewhere, then, doesn't it? I never said that the declaration macros were unnecessary. I said that macros like TAILQ_FIRST are unnecessary. Some people disagree (notably David G. and Justin). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Apr 10 18:30:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA17726 for current-outgoing; Thu, 10 Apr 1997 18:30:49 -0700 (PDT) Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA17717 for ; Thu, 10 Apr 1997 18:30:45 -0700 (PDT) Received: from dvl-1.pathlink.com (dvl-1.pathlink.com [204.30.237.241]) by dopey.pathlink.com (8.8.5/8.8.4) with SMTP id SAA25876; Thu, 10 Apr 1997 18:40:26 -0700 (PDT) Message-Id: <1.5.4.32.19970410182951.006d3a84@dopey.pathlink.com> X-Sender: kachun@dopey.pathlink.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 10 Apr 1997 18:29:51 +0000 To: Terry Lambert From: Kachun Lee Subject: Re: NFS/mmap freeze in 2.2R Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 02:06 PM 4/10/97 -0700, you wrote: >> While you are at it, maybe, you want to check this out also. We noticed we have >> been getting these messages: >> >> ------------- >> Apr 8 23:21:12 lois /kernel: vnode_pager_getpages: I/O read error >> Apr 8 23:21:12 lois /kernel: vm_fault: pager input (probably hardware) error, >> P >> ID 11987 failure >> Apr 8 23:21:12 lois /kernel: pid 11987 (in.nnrpd), uid 7003: exited on signal >> 11 >> -------------- >> >> since 2.2R or later with our NFS mounted news servers. They appeared at >> the NFS clients during news was expiring at the NFS server. That leaded >> me to believe that the message was triggered when someone was reading >> an article while the NFS server removed it - both systems kept running >> though. > >Are you running the INN msync() patch? There is an error in the INN >use of mapped files when the file is extended. The problem occurs when: > >1) The file is not a multiple of a page size in length >2) The file is mmap'ed, and the last page is zero filled >3) The file is extended >4) The mmap'ed area is accessed between the previous end of the > file and the page boundry following the end of the file, without > an intervening msync(). > >This is a bug in INN's use of the mmap() interface, not a FreeBSD bug. > [snip] Thank you for the info. I did aware of the mmap active file issue. I probably should not just tag on the NFS/MMAP thread. The problem I was referring to was related to NFS/VM and not related to MMAP at all - nnrpd (at least the one we are using) does not use MMAP to read articles or overview file. Best regards From owner-freebsd-current Thu Apr 10 18:40:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA18418 for current-outgoing; Thu, 10 Apr 1997 18:40:39 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA18413 for ; Thu, 10 Apr 1997 18:40:36 -0700 (PDT) Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id SAA24769; Thu, 10 Apr 1997 18:34:06 -0700 (PDT) Date: Thu, 10 Apr 1997 18:44:52 -0700 (PDT) From: Tom Samplonius To: Terry Lambert cc: "Craig W. Shaver" , current@FreeBSD.ORG Subject: Re: NFS/mmap freeze in 2.2R In-Reply-To: <199704110043.RAA10356@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Apr 1997, Terry Lambert wrote: > > > (If you are running the msync() patch, then never mind). > > > > Terry, where can I find the INN msync() patch, and what version of INN > > is it to be applied against? > > Ugh. That's a nice hard question. I typically don't run INN. Your > best bet would be to check the -current list archives for the keywords > "INN" and "msync". > > Barring that, if you could wait, you should be able to take John Dyson up > on his offer to fix the VM problem. > > PS: If the problem *is* cured by the msync() patch, I think the only VM > problem is in the way the error is reported as a FreeBSD error instead > of an application error, and John may do well to fix *that*, rather > than to compromise the mmap() behaviour for the benefit INN... > > > Regards, > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. The msync() changes are in INN1.5.1, which has been out for some time. Tom From owner-freebsd-current Thu Apr 10 19:01:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA19385 for current-outgoing; Thu, 10 Apr 1997 19:01:47 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA19380 for ; Thu, 10 Apr 1997 19:01:41 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id VAA01503; Thu, 10 Apr 1997 21:00:31 -0500 (EST) From: "John S. Dyson" Message-Id: <199704110200.VAA01503@dyson.iquest.net> Subject: Re: NFS/mmap freeze in 2.2R In-Reply-To: <199704110043.RAA10356@phaeton.artisoft.com> from Terry Lambert at "Apr 10, 97 05:43:25 pm" To: terry@lambert.org (Terry Lambert) Date: Thu, 10 Apr 1997 21:00:31 -0500 (EST) Cc: craig@tuna.progroup.com, terry@lambert.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > PS: If the problem *is* cured by the msync() patch, I think the only VM > problem is in the way the error is reported as a FreeBSD error instead > of an application error, and John may do well to fix *that*, rather > than to compromise the mmap() behaviour for the benefit INN... > Uhhh... You mean my new sysctl vm.modify.mmap.behavior.for.inn isn't a good idea? Geesh :-). John From owner-freebsd-current Thu Apr 10 19:12:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA20030 for current-outgoing; Thu, 10 Apr 1997 19:12:24 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA20008 for ; Thu, 10 Apr 1997 19:12:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id TAA01113; Thu, 10 Apr 1997 19:11:26 -0700 (PDT) Message-Id: <199704110211.TAA01113@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Garrett Wollman cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: WHY? ...non-use of TAILQ macros... In-reply-to: Your message of "Thu, 10 Apr 1997 21:14:06 EDT." <199704110114.VAA05848@khavrinen.lcs.mit.edu> From: David Greenman Reply-To: dg@root.com Date: Thu, 10 Apr 1997 19:11:26 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >< said: > >>> > kern_lockf.c: while (ltmp = overlap->lf_blkhd.tqh_first) { > >>> 2. Because they are unnecessary. > >> Well, that begs the question of qhy they are being used in declarations >> and elsewhere, then, doesn't it? > >I never said that the declaration macros were unnecessary. I said >that macros like TAILQ_FIRST are unnecessary. Some people disagree >(notably David G. and Justin). Actually it was Poul-Henning who added those and I don't recall agreeing that I liked it. In fact, I recall thinking that it was completely unnecessary, but I don't think I made any comment at the time. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Apr 10 20:44:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA23319 for current-outgoing; Thu, 10 Apr 1997 20:44:36 -0700 (PDT) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA23310 for ; Thu, 10 Apr 1997 20:44:31 -0700 (PDT) Received: from tuna.ProGroup.COM (tuna.progroup.com [206.24.122.5]) by seabass.progroup.com (8.7.5/8.7.3) with SMTP id UAA08454; Thu, 10 Apr 1997 20:43:18 -0700 (PDT) Received: by tuna.ProGroup.COM (SMI-8.6/SMI-SVR4) id UAA06055; Thu, 10 Apr 1997 20:44:51 -0700 From: craig@tuna.progroup.com (Craig W. Shaver) Message-Id: <199704110344.UAA06055@tuna.ProGroup.COM> Subject: Re: NFS/mmap freeze in 2.2R - msync() patch in 1.5.1 To: tom@uniserve.com (Tom Samplonius) Date: Thu, 10 Apr 1997 20:44:51 -0700 (PDT) Cc: current@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Apr 10, 97 06:44:52 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-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > On Thu, 10 Apr 1997, Terry Lambert wrote: > > > > > (If you are running the msync() patch, then never mind). del .... > > The msync() changes are in INN1.5.1, which has been out for some time. > > > Tom > > Good! I just upgraded to that version. I'll try to recompile with the mmap turned on for active and all the rest. Thanks, -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-current Thu Apr 10 20:49:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA23546 for current-outgoing; Thu, 10 Apr 1997 20:49:47 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA23540 for ; Thu, 10 Apr 1997 20:49:44 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id XAA25228; Thu, 10 Apr 1997 23:43:47 -0400 (EDT) Message-ID: <19970410234347.04317@vinyl.quickweb.com> Date: Thu, 10 Apr 1997 23:43:47 -0400 From: Mark Mayo To: Brian Tao Cc: Tom Bartol , FREEBSD-CURRENT-L Subject: Re: XFree86 3.2 causes constant 1.0 load average? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.66e In-Reply-To: ; from Brian Tao on Wed, Apr 09, 1997 at 01:47:57PM -0400 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Apr 09, 1997 at 01:47:57PM -0400, Brian Tao wrote: > On Mon, 7 Apr 1997, Tom Bartol wrote: > > > > I am running FreeBSD-3.0-970209-SNAP and AfterStep-1.0pre6 also and > > I too occasionally see this same thing (this morning, in fact). I > > have not been able to track it down. > > What X server are you using? Mach64? I also see this bogus load crap using Afterstep - but under Xinside's matrox Millenium server... Again, it seems random when the load will rise.. I've had this behaviour with Afterstep since version 1.0pre2, and since the 2.2 October SNAP up to 2.2.1R right now. > -- > Brian Tao (BT300, taob@netcom.ca) > "Though this be madness, yet there is method in't" -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-current Thu Apr 10 21:32:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA25137 for current-outgoing; Thu, 10 Apr 1997 21:32:35 -0700 (PDT) Received: from heli-fishing.eos.ncsu.edu (heli-fishing.eos.ncsu.edu [152.1.68.52]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25132 for ; Thu, 10 Apr 1997 21:32:33 -0700 (PDT) Received: (from camattin@localhost) by heli-fishing.eos.ncsu.edu (8.8.4/EC02Jan97) id EAA19522; Fri, 11 Apr 1997 04:32:15 GMT Message-Id: <199704110432.EAA19522@heli-fishing.eos.ncsu.edu> Subject: Re: XFree86 3.2 causes constant 1.0 load average? To: mark@quickweb.com (Mark Mayo) Date: Fri, 11 Apr 1997 00:32:14 -0400 (EDT) Cc: taob@nbc.netcom.ca (Brian Tao), bartol@salk.edu (Tom Bartol), freebsd-current@FreeBSD.ORG (FREEBSD-CURRENT-L) In-Reply-To: <19970410234347.04317@vinyl.quickweb.com> from "Mark Mayo" at Apr 10, 1997 11:43:47 PM From: camattin@ncsu.edu (Chris A. Mattingly) Reply-To: camattin@ncsu.edu X-Mailer: ELM [version 2.5 PL0b1/POP] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mark Mayo wrote the following about "Re: XFree86 3.2 causes constant 1.0 load average?" on Thu Apr 10 23:43:47 1997 > > On Wed, Apr 09, 1997 at 01:47:57PM -0400, Brian Tao wrote: > > On Mon, 7 Apr 1997, Tom Bartol wrote: > > > > > > I am running FreeBSD-3.0-970209-SNAP and AfterStep-1.0pre6 also and > > > I too occasionally see this same thing (this morning, in fact). I > > > have not been able to track it down. > > > > What X server are you using? Mach64? > > I also see this bogus load crap using Afterstep - but under Xinside's > matrox Millenium server... Again, it seems random when the load will rise.. > I've had this behaviour with Afterstep since version 1.0pre2, and since > the 2.2 October SNAP up to 2.2.1R right now. I've been seeing this too with -current, under XFree86 3.2 and 3.2A with fvwm95. Something else I've noticed is that serial traffic via usermode ppp causes the load to go higher than it used to.. but only some of the times, kinda like the 1.0 load. :-/ -Chris -- Chris Mattingly | My views are not necessarily those of my employers camattin@ncsu.edu | NC State University/ITECS | "Good programmers write good code; great Systems Programmer | programmers 'borrow' good code." -- Mike Gancarz From owner-freebsd-current Thu Apr 10 22:12:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA26754 for current-outgoing; Thu, 10 Apr 1997 22:12:25 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA26746 for ; Thu, 10 Apr 1997 22:12:22 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA03402 for ; Thu, 10 Apr 1997 22:12:21 -0700 (PDT) To: current@freebsd.org Subject: Trivial Nit-Pick Of The Week. Date: Thu, 10 Apr 1997 22:12:19 -0700 Message-ID: <3394.860735539@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk /usr/include/malloc.h:2: warning: #warning "this file includes which is obsoleted, use instead" Shouldn't cpp emit a more sensible: /usr/include/malloc.h:2: #warning "this file includes which is obsoleted, use instead" It would be output more consistent with that of #error, for example. Jordan From owner-freebsd-current Thu Apr 10 22:15:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA26856 for current-outgoing; Thu, 10 Apr 1997 22:15:03 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA26844 for ; Thu, 10 Apr 1997 22:15:00 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA03919 for ; Thu, 10 Apr 1997 22:14:59 -0700 (PDT) To: current@freebsd.org Subject: OK, who broke man? Date: Thu, 10 Apr 1997 22:14:57 -0700 Message-ID: <3904.860735697@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Aren't people testing stuff anymore before they commit it? :-) jkh@time-> cd /usr/src/gnu/usr.bin/man jkh@time-> make depend rm -f .depend mkdep -f .depend -a -I/usr/tmp/man/man/../lib -I/usr/tmp/man/man/../lib -DSTDC_HEADERS -DPOSIX -DHAS_TROFF -DDO_COMPRESS -DALT_SYSTEMS -DSETREUID -DCATMODE=0644 man.c manpath.c glob.c man.c:30: config.h: No such file or directory manpath.c:23: config.h: No such file or directory mkdep: compile failed. *** Error code 1 Stop. I was sort of hoping to do a 3.0 snapshot tonite, but I guess not! ;-) Jordan From owner-freebsd-current Thu Apr 10 22:20:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA27156 for current-outgoing; Thu, 10 Apr 1997 22:20:06 -0700 (PDT) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA27104; Thu, 10 Apr 1997 22:19:35 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.7.3) id FAA10606; Fri, 11 Apr 1997 05:36:30 GMT From: Adam David Message-Id: <199704110536.FAA10606@veda.is> Subject: longer usernames To: freebsd-isp@freebsd.org, freebsd-current@freebsd.org Date: Fri, 11 Apr 1997 05:36:29 +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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone have a definitive list of what versions of which files are needed to enable >8 char usernames for 2.2.1? Is this going into 2.2.5? Note this is directed to the isp and current lists, so please modify Cc: accordingly in reply. -- Adam David From owner-freebsd-current Thu Apr 10 23:13:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA28933 for current-outgoing; Thu, 10 Apr 1997 23:13:13 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28925 for ; Thu, 10 Apr 1997 23:13:10 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id QAA07220; Fri, 11 Apr 1997 16:08:39 +1000 Date: Fri, 11 Apr 1997 16:08:39 +1000 From: Bruce Evans Message-Id: <199704110608.QAA07220@godzilla.zeta.org.au> To: current@freebsd.org, jkh@time.cdrom.com Subject: Re: Trivial Nit-Pick Of The Week. Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >/usr/include/malloc.h:2: warning: #warning "this file includes which is obsoleted, use instead" > >Shouldn't cpp emit a more sensible: > >/usr/include/malloc.h:2: #warning "this file includes which is obsoleted, use instead" > >It would be output more consistent with that of #error, for example. It's actually already consistent, although not good. All warnings are prefixed by "warning: ", but there is no prefix for errors. For both #warning and #error, the full line is printed following the prefix. Other braindamage: there is no prefix for "In function `foo':" or "At top level:", so it is difficult to separate warnings from errors using a simple regexp. Fixing this might break complicated pattern matchers. Bruce From owner-freebsd-current Fri Apr 11 01:09:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA03602 for current-outgoing; Fri, 11 Apr 1997 01:09:15 -0700 (PDT) Received: from critter.dk.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03593; Fri, 11 Apr 1997 01:09:10 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id JAA01096; Fri, 11 Apr 1997 09:07:49 +0200 (CEST) To: Terry Lambert cc: current@freebsd.org From: phk@dk.tfs.com Subject: Re: WHY? ...non-use of TAILQ macros... In-reply-to: Your message of "Thu, 10 Apr 1997 15:48:44 PDT." <199704102248.PAA10021@phaeton.artisoft.com> Date: Fri, 11 Apr 1997 09:07:48 +0200 Message-ID: <1094.860742468@critter> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199704102248.PAA10021@phaeton.artisoft.com>, Terry Lambert writes: > >On the theory that the TAILQ_xxx macros were being avoided and the >queue elemments themselves directly refernce for No Good Reason(tm), >I just compiled the following: You're way behind Terry! :-) I argued this long time ago and started to introduce the _FIRST, _LAST, _NEXT, _PREV and _EMPTY macros as I have got to it. A patch for this from you would be most welcome of course. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Fri Apr 11 01:09:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA03612 for current-outgoing; Fri, 11 Apr 1997 01:09:17 -0700 (PDT) Received: from critter.dk.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03594; Fri, 11 Apr 1997 01:09:10 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id JAA01181; Fri, 11 Apr 1997 09:12:56 +0200 (CEST) To: dg@root.com cc: Garrett Wollman , Terry Lambert , current@FreeBSD.ORG From: phk@dk.tfs.com Subject: Re: WHY? ...non-use of TAILQ macros... In-reply-to: Your message of "Thu, 10 Apr 1997 19:11:26 PDT." <199704110211.TAA01113@root.com> Date: Fri, 11 Apr 1997 09:12:56 +0200 Message-ID: <1179.860742776@critter> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Actually it was Poul-Henning who added those and I don't recall >agreeing that I liked it. In fact, I recall thinking that it was >completely unnecessary, but I don't think I made any comment at the >time. Indeed, I started it, and I still have a bunch of patches, which I promised not to commit until after the LITE2 merge. I think that is a weird inconsistent mess without them, and I see no reason why we would want to hide half of the implementation behind macros, but not the other half. I fully intend to complete the migration btw. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Fri Apr 11 01:18:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA03947 for current-outgoing; Fri, 11 Apr 1997 01:18:57 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03942 for ; Fri, 11 Apr 1997 01:18:54 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id JAA19326; Fri, 11 Apr 1997 09:15:11 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Fri, 11 Apr 1997 09:08:30 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <3904.860735697@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 11 Apr 1997 09:06:07 +0100 To: "Jordan K. Hubbard" From: Bob Bishop Subject: Re: OK, who broke man? Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >[...] >I was sort of hoping to do a 3.0 snapshot tonite, but I guess not! ;-) > > Jordan Something else to worry about: I've been whingeing about slow builds with -current kernels later than about Mar 20. Building the kernel for ctm src-cur 2835 using an old (20 Mar) kernel takes 28:32 here, but the same build atop a 2835 kernel takes 3:18:34 :-( Since there hasn't been a public outcry, I have to assume there's some local factor. My -current machine is a 486 ISA with an Adaptec 1542CF and 20Mb, so I guess it could be bounce-buffer related. I'm prepared to go digging if someone will give me a clue... -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Fri Apr 11 02:39:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA06911 for current-outgoing; Fri, 11 Apr 1997 02:39:46 -0700 (PDT) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA06906 for ; Fri, 11 Apr 1997 02:39:31 -0700 (PDT) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.5/8.7.3) id LAA09877; Fri, 11 Apr 1997 11:35:21 +0200 (MET DST) From: Søren Schmidt Message-Id: <199704110935.LAA09877@ravenock.cybercity.dk> Subject: Re: OK, who broke man? In-Reply-To: from Bob Bishop at "Apr 11, 97 09:06:07 am" To: rb@gid.co.uk (Bob Bishop) Date: Fri, 11 Apr 1997 11:35:21 +0200 (MET DST) Cc: jkh@time.cdrom.com, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Bob Bishop who wrote: > > Something else to worry about: I've been whingeing about slow builds with > -current kernels later than about Mar 20. > > Building the kernel for ctm src-cur 2835 using an old (20 Mar) kernel takes > 28:32 here, but the same build atop a 2835 kernel takes 3:18:34 :-( > > Since there hasn't been a public outcry, I have to assume there's some > local factor. My -current machine is a 486 ISA with an Adaptec 1542CF and > 20Mb, so I guess it could be bounce-buffer related. I'm prepared to go > digging if someone will give me a clue... Hmm, you must have some local murphy field active, I can still build a kernel just under 2 mins, and a world well under 2 hours, so.. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Fri Apr 11 02:49:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA07417 for current-outgoing; Fri, 11 Apr 1997 02:49:43 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA07412 for ; Fri, 11 Apr 1997 02:49:40 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id MAA28535; Fri, 11 Apr 1997 12:44:27 +0300 (EET DST) From: mika ruohotie Message-Id: <199704110944.MAA28535@shadows.aeon.net> Subject: Re: wdx interrupt timeouts (fwd) In-Reply-To: <199704101022.LAA15505@albatross.mcc.ac.uk> from Ian Pallfreeman at "Apr 10, 97 11:22:35 am" To: ip@mcc.ac.uk Date: Fri, 11 Apr 1997 12:44:27 +0300 (EET DST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Apr 8 15:07:54 lurch /kernel: wd3: interrupt timeout: > > > Apr 8 15:07:54 lurch /kernel: wd3: status 58 error 0 > Nothing to do with IDE spindown (had a couple of other folks suggesting that). > This happens under heavy load -- e.g. mirroring the ftp archive. hmm. > The problem has become worse over the last few days. First it changed to: > Apr 9 14:06:48 lurch /kernel: wd3e: reverting to non-multi sector > mode reading fsbn 4213504 of 4213456-4213518 (wd3 bn 4213504; cn 4180 > tn 1 sn 1)wd3: status 59 error 40 > Apr 9 14:06:55 lurch /kernel: wd3e: hard error reading fsbn 4213506 > of 4213456-4213518 (wd3 bn 4213506; cn 4180 tn 1 sn 3)wd3: status > 59 error 40 i'm sorry to say but it looks like what i had bit over a year ago when my ide drive started to emulate helicopter. meaning, the drive is dying. > I guess I'll reformat the disks eventually; anybody got any other ideas? backup, get another drive. mickey From owner-freebsd-current Fri Apr 11 03:39:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA10018 for current-outgoing; Fri, 11 Apr 1997 03:39:57 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10013 for ; Fri, 11 Apr 1997 03:39:54 -0700 (PDT) Received: from nessie.mcc.ac.uk (nessie.mcc.ac.uk [130.88.200.20]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id DAA06587 for ; Fri, 11 Apr 1997 03:39:50 -0700 (PDT) Received: from albatross.mcc.ac.uk by nessie.mcc.ac.uk with SMTP (PP); Fri, 11 Apr 1997 11:37:15 +0100 Received: (from ip@localhost) by albatross.mcc.ac.uk (8.8.5/8.6.12) id LAA18207 for freebsd-current@freebsd.org; Fri, 11 Apr 1997 11:37:05 +0100 (BST) From: Ian Pallfreeman Message-Id: <199704111037.LAA18207@albatross.mcc.ac.uk> Subject: Re: wdx interrupt timeouts (fwd) To: freebsd-current@freebsd.org Date: Fri, 11 Apr 1997 11:37:05 +0100 (BST) In-Reply-To: <199704110944.MAA28535@shadows.aeon.net> from "mika ruohotie" at Apr 11, 97 12:44:27 pm Reply-To: ip@mcc.ac.uk X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk bsdcur@shadows.aeon.net (mika ruohotie) wrote: > backup, get another drive. Thanks for the suggestion; I probably will, but: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4e3a1bd4 fault code = supervisor read, page not present instruction pointer = 0x8:0xf010144c stack pointer = 0x10:0xf6b13d80 frame pointer = 0x10:0xf6b13d9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 7329 (perl) interrupt mask = bio panic: page fault shouldn't be happening just because I'm trying to read a possibly (but not very likely) bad drive, should it? Note the subject line -- this started with innocuous "interrupt timeout" messages, progressed to hard errors and now we're onto panics. I hate IDE, even brand-new supposedly self-correcting drives... I'm also stuck at first base with the crash dump: GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 1ef000 kernel symbol `kstack' not found. (kgdb) Any suggestions, offers of help, or brain transplants gratefully receieved... "Why does it always happen to me?" Ian. From owner-freebsd-current Fri Apr 11 06:40:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA19144 for current-outgoing; Fri, 11 Apr 1997 06:40:39 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA19138 for ; Fri, 11 Apr 1997 06:40:36 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id HAA07157; Fri, 11 Apr 1997 07:38:41 -0600 (MDT) Message-Id: <199704111338.HAA07157@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Garrett Wollman cc: Terry Lambert , current@freebsd.org Subject: Re: WHY? ...non-use of TAILQ macros... In-reply-to: Your message of "Thu, 10 Apr 1997 20:21:58 EDT." <199704110021.UAA05660@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Apr 1997 07:37:02 -0600 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >< >said: > >> I'm wondering why the following aren't written using the macros (macro >> versions are shown one line below): >> kern_lockf.c: while (ltmp = overlap->lf_blkhd >.tqh_first) { > >1. Because they are a FreeBSD (actually Justin Gibbs) invention. >Obviously, original Berkeley code will not use a macro that Berkeley >didn't have. Actually, Poul invented the macros to access the individual members. I did the SLIST and STAILQ stuff. >-GAWollman > >-- >Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the sam >e >wollman@lcs.mit.edu | O Siem / The fires of freedom >Opinions not those of| Dance in the burning flame >MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Fri Apr 11 06:54:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA19823 for current-outgoing; Fri, 11 Apr 1997 06:54:51 -0700 (PDT) Received: from dyslexic.phoenix.net (root@dyslexic.phoenix.net [199.3.233.7]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA19818 for ; Fri, 11 Apr 1997 06:54:46 -0700 (PDT) Received: (from gemohler@localhost) by dyslexic.phoenix.net (8.8.5/8.7.3) id IAA24453; Fri, 11 Apr 1997 08:52:34 -0500 (CDT) Date: Fri, 11 Apr 1997 08:52:34 -0500 (CDT) From: Geoff Mohler X-Sender: gemohler@dyslexic.phoenix.net To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: Trivial Nit-Pick Of The Week. In-Reply-To: <3394.860735539@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Apr 1997, Jordan K. Hubbard wrote: > /usr/include/malloc.h:2: warning: #warning "this file includes which is obsoleted, use instead" > Shouldn't cpp emit a more sensible: > /usr/include/malloc.h:2: #warning "this file includes which is obsoleted, use instead" Ive always wondered about that problem: #problem. =-=-=-=-=- ROMANI ITE DOMUM Geoff Mohler Operations Engineer Charter Communications/Phoenix Data Net From owner-freebsd-current Fri Apr 11 07:00:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA20170 for current-outgoing; Fri, 11 Apr 1997 07:00:48 -0700 (PDT) Received: from critter.dk.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA20165 for ; Fri, 11 Apr 1997 07:00:42 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id PAA03200 for ; Fri, 11 Apr 1997 15:59:24 +0200 (CEST) To: current@freebsd.org Subject: network buglet ? From: phk@dk.tfs.com Date: Fri, 11 Apr 1997 15:59:24 +0200 Message-ID: <3198.860767164@critter> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Any good explanations for this negative RTT ? 64 bytes from 194.19.64.133: icmp_seq=216 ttl=245 time=415.414 ms 64 bytes from 194.19.64.133: icmp_seq=217 ttl=245 time=401.798 ms 64 bytes from 194.19.64.133: icmp_seq=219 ttl=245 time=399.801 ms 64 bytes from 194.19.64.133: icmp_seq=221 ttl=245 time=385.142 ms 64 bytes from 194.19.64.133: icmp_seq=222 ttl=245 time=419.366 ms 64 bytes from 194.19.64.133: icmp_seq=223 ttl=245 time=-177.755 ms 64 bytes from 194.19.64.133: icmp_seq=224 ttl=245 time=417.157 ms 64 bytes from 194.19.64.133: icmp_seq=225 ttl=245 time=667.852 ms 64 bytes from 194.19.64.133: icmp_seq=226 ttl=245 time=393.256 ms -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Fri Apr 11 07:40:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA22077 for current-outgoing; Fri, 11 Apr 1997 07:40:11 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA22062 for ; Fri, 11 Apr 1997 07:40:04 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.5/8.7.3) with SMTP id KAA00443; Fri, 11 Apr 1997 10:39:52 -0400 (EDT) Message-Id: <199704111439.KAA00443@whizzo.transsys.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: phk@dk.tfs.com cc: current@freebsd.org From: "Louis A. Mamakos" Subject: Re: network buglet ? References: <3198.860767164@critter> In-reply-to: Your message of "Fri, 11 Apr 1997 15:59:24 +0200." <3198.860767164@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Apr 1997 10:39:52 -0400 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Did NTP happen to step-adjust your clock at that time? louie > > Any good explanations for this negative RTT ? From owner-freebsd-current Fri Apr 11 09:30:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA28946 for current-outgoing; Fri, 11 Apr 1997 09:30:54 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA28933 for ; Fri, 11 Apr 1997 09:30:48 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA11483; Fri, 11 Apr 1997 09:10:26 -0700 From: Terry Lambert Message-Id: <199704111610.JAA11483@phaeton.artisoft.com> Subject: Re: NFS/mmap freeze in 2.2R To: tom@uniserve.com (Tom Samplonius) Date: Fri, 11 Apr 1997 09:10:26 -0700 (MST) Cc: terry@lambert.org, craig@tuna.progroup.com, current@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Apr 10, 97 06:44:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The msync() changes are in INN1.5.1, which has been out for some time. Thanks; I wasn't sure if they had been integrated or not... 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 Fri Apr 11 09:47:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA00667 for current-outgoing; Fri, 11 Apr 1997 09:47:52 -0700 (PDT) Received: from linus.intrastar.net (jsuter@linus.intrastar.net [206.136.25.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00654; Fri, 11 Apr 1997 09:47:42 -0700 (PDT) Received: from localhost (jsuter@localhost) by linus.intrastar.net (8.8.5/8.8.5) with SMTP id LAA05078; Fri, 11 Apr 1997 11:47:25 -0500 (CDT) Date: Fri, 11 Apr 1997 11:47:23 -0500 (CDT) From: Jacob Suter To: Adam David cc: freebsd-isp@freebsd.org, freebsd-current@freebsd.org Subject: Re: longer usernames In-Reply-To: <199704110536.FAA10606@veda.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Apr 1997, Adam David wrote: > Does anyone have a definitive list of what versions of which files are needed > to enable >8 char usernames for 2.2.1? Is this going into 2.2.5? > > Note this is directed to the isp and current lists, so please modify Cc: > accordingly in reply. It would appear it support 16 charector limits right now on my stock 2.2.1r boxes. I haven't tested it though. JS From owner-freebsd-current Fri Apr 11 10:11:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA03662 for current-outgoing; Fri, 11 Apr 1997 10:11:04 -0700 (PDT) Received: from enst.enst.fr (2lb2W4AT5Ze4wdcumhofzatjZbHrQAiG@enst.enst.fr [137.194.2.16]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA03644 for ; Fri, 11 Apr 1997 10:10:57 -0700 (PDT) Received: from email.enst.fr (email.enst.fr [137.194.168.17]) by enst.enst.fr (8.8.4/8.8.4) with ESMTP id TAA29480; Fri, 11 Apr 1997 19:10:21 +0200 (MET DST) Received: from nikopol.enst.fr (nikopol.enst.fr [137.194.168.105]) by email.enst.fr (8.8.4/8.8.4) with ESMTP id TAA07479; Fri, 11 Apr 1997 19:10:07 +0200 (MET DST) Received: (from fenyo@localhost) by nikopol.enst.fr (8.8.4/8.8.4) id TAA20766; Fri, 11 Apr 1997 19:10:03 +0200 (MET DST) Date: Fri, 11 Apr 1997 19:10:03 +0200 (MET DST) Message-Id: <199704111710.TAA20766@nikopol.enst.fr> From: "Alex Fenyo (eowyn)" To: current@FreeBSD.ORG Subject: Bug in libc_r implementation of pthread_cond_wait Cc: jb@cimlogic.com.au X-WWW: http://home.eowyn.fr.eu.org/~fenyo/documents/axel.html X-PGP-Key: finger alex@eowyn.fr.eu.org X-NIC-Handle: AF713 X-Whois: whois -h whois.internic.net fenyo X-Pager: 06-04-30-75-94 (for emergency only) Organization: Ecole Nationale Superieure des Telecommunications de Paris Reply-to: fenyo@email.enst.fr Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I encountered a problem using pthread_cond_wait() that seems to be broken : the thread that calls pthread_cond_wait() is always rescheduled (even if there is no call to pthread_cond_signal() or other reason to be rescheduled). This is due to the fact that _thread_kern_sched() (src/lib/libc_r/uthread/uthread_kern.c) tests pthread->wakeup_time.tv_sec for the value -1 to know if the waiting thread is to timeout or wait forever. But pthread_cond_wait() doesn't set this value. Can somebody change this code (pthread_cond_wait() in src/lib/libc_r/uthread/uthread_cond.c) : ------------------------------------------------------------ /* Process according to condition variable type: */ switch ((*cond)->c_type) { /* Fast condition variable: */ case COND_TYPE_FAST: /* Queue the running thread for the condition variable: */ _thread_queue_enq(&(*cond)->c_queue, _thread_run ); ------------------------------------------------------------ by this one : ------------------------------------------------------------ /* Process according to condition variable type: */ switch ((*cond)->c_type) { /* Fast condition variable: */ case COND_TYPE_FAST: _thread_run->wakeup_time.tv_sec = -1; /* Queue the running thread for the condition variable: */ _thread_queue_enq(&(*cond)->c_queue, _thread_run ); ------------------------------------------------------------ Alexandre Fenyo From owner-freebsd-current Fri Apr 11 11:01:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA07190 for current-outgoing; Fri, 11 Apr 1997 11:01:47 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA07179; Fri, 11 Apr 1997 11:01:43 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id KAA14581; Fri, 11 Apr 1997 10:59:31 -0700 (PDT) To: Jacob Suter cc: Adam David , freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: longer usernames In-reply-to: Your message of "Fri, 11 Apr 1997 11:47:23 CDT." Date: Fri, 11 Apr 1997 10:59:31 -0700 Message-ID: <14559.860781571@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It would appear it support 16 charector limits right now on my stock > 2.2.1r boxes. I haven't tested it though. Uh, no. ;-) If you look at /usr/include/utmp.h, you'll see it's still 8 characters. I'm not sure if we'll go to longer usernames in the 2.2 branch because it would be a big transition headache for everyone, but it's certainly there in 3.0 (which will already probably be a transition headache for different reasons, so it doesn't really matter :-) Jordan From owner-freebsd-current Fri Apr 11 11:14:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA08578 for current-outgoing; Fri, 11 Apr 1997 11:14:30 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA08572 for ; Fri, 11 Apr 1997 11:14:25 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id LAA01364; Fri, 11 Apr 1997 11:11:38 -0700 (PDT) Message-ID: <334E7ED4.794BDF32@whistle.com> Date: Fri, 11 Apr 1997 11:11:32 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Garrett Wollman CC: current@FreeBSD.ORG Subject: Re: WHY? ...non-use of TAILQ macros... References: <199704110021.UAA05660@khavrinen.lcs.mit.edu> <199704110039.RAA10331@phaeton.artisoft.com> <199704110114.VAA05848@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Garrett Wollman wrote: > > < said: > > >> > kern_lockf.c: while (ltmp = overlap->lf_blkhd.tqh_first) { > > >> 2. Because they are unnecessary. > > > Well, that begs the question of qhy they are being used in declarations > > and elsewhere, then, doesn't it? > > I never said that the declaration macros were unnecessary. I said > that macros like TAILQ_FIRST are unnecessary. Some people disagree > (notably David G. and Justin). and me I think that if you are using a MACRO set for the definition, the n you should have a macro to use it.. so that debugging and locks etc, can be changed without changing the code.. otherwise the macros are not really being used for what they are good for. From owner-freebsd-current Fri Apr 11 12:05:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA12645 for current-outgoing; Fri, 11 Apr 1997 12:05:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA12636 for ; Fri, 11 Apr 1997 12:05:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA11874; Fri, 11 Apr 1997 11:45:42 -0700 From: Terry Lambert Message-Id: <199704111845.LAA11874@phaeton.artisoft.com> Subject: Re: Trivial Nit-Pick Of The Week. To: bde@zeta.org.au (Bruce Evans) Date: Fri, 11 Apr 1997 11:45:42 -0700 (MST) Cc: current@freebsd.org, jkh@time.cdrom.com In-Reply-To: <199704110608.QAA07220@godzilla.zeta.org.au> from "Bruce Evans" at Apr 11, 97 04:08:39 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ ... #warning ... ] > It's actually already consistent, although not good. All warnings are > prefixed by "warning: ", but there is no prefix for errors. For both > #warning and #error, the full line is printed following the prefix. > Other braindamage: there is no prefix for "In function `foo':" or "At > top level:", so it is difficult to separate warnings from errors using > a simple regexp. > > Fixing this might break complicated pattern matchers. Where can I download one of these complicated pattern matchers? 8-). Is there really code out there that depends on this behaviour? 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 Fri Apr 11 13:15:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA17538 for current-outgoing; Fri, 11 Apr 1997 13:15:43 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [198.180.136.138]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17532; Fri, 11 Apr 1997 13:15:37 -0700 (PDT) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.5/8.8.3) id KAA00555; Fri, 11 Apr 1997 10:14:59 -1000 (HST) Message-Id: <199704112014.KAA00555@caliban.dihelix.com> Subject: Re: longer usernames In-Reply-To: <14559.860781571@time.cdrom.com> from "Jordan K. Hubbard" at "Apr 11, 97 10:59:31 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 11 Apr 1997 10:14:59 -1000 (HST) Cc: jsuter@linus.intrastar.net, adam@veda.is, freebsd-isp@freebsd.org, freebsd-current@freebsd.org From: "David Langford" X-blank-line: This space intentionaly left blank. 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> It would appear it support 16 charector limits right now on my stock >> 2.2.1r boxes. I haven't tested it though. > >Uh, no. ;-) > >If you look at /usr/include/utmp.h, you'll see it's still 8 characters. > >I'm not sure if we'll go to longer usernames in the 2.2 branch because >it would be a big transition headache for everyone, but it's certainly >there in 3.0 (which will already probably be a transition headache for >different reasons, so it doesn't really matter :-) > > Jordan > I remember this being discussed a little while ago but I dont recall the specifics. What are the gotchas for changing the utmp.h file and doing a make world. Will FreeBSD t FreeBSD YP work? Sendmail, csh, tcsh etc.... Thanks, -David Langford langfod@dihelix.com From owner-freebsd-current Fri Apr 11 14:27:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA22157 for current-outgoing; Fri, 11 Apr 1997 14:27:47 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA22148; Fri, 11 Apr 1997 14:27:43 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id OAA25264; Fri, 11 Apr 1997 14:23:51 -0700 (PDT) To: "David Langford" cc: jsuter@linus.intrastar.net, adam@veda.is, freebsd-isp@freebsd.org, freebsd-current@freebsd.org Subject: Re: longer usernames In-reply-to: Your message of "Fri, 11 Apr 1997 10:14:59 -1000." <199704112014.KAA00555@caliban.dihelix.com> Date: Fri, 11 Apr 1997 14:23:50 -0700 Message-ID: <25243.860793830@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I remember this being discussed a little while ago but I dont recall the > specifics. The email search feature at http://www.freebsd.org is your friend. :) > What are the gotchas for changing the utmp.h file and doing a make world. You just need to make sure that you get all the non-FreeBSD stuff recompiled too (like tcsh, xterm, etc). Again, please see the archives, this has all already been discussed to death. Jordan From owner-freebsd-current Fri Apr 11 14:35:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA23023 for current-outgoing; Fri, 11 Apr 1997 14:35:56 -0700 (PDT) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA23018; Fri, 11 Apr 1997 14:35:53 -0700 (PDT) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.5/8.8.4) with SMTP id RAA05379; Fri, 11 Apr 1997 17:33:42 -0400 (EDT) Date: Fri, 11 Apr 1997 17:33:42 -0400 (EDT) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net To: David Langford cc: freebsd-isp@freebsd.org, freebsd-current@freebsd.org Subject: Re: longer usernames In-Reply-To: <199704112014.KAA00555@caliban.dihelix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk See http://www.harborcom.net/noc/freebsd/long.html for a little doc I just hacked up. I am converting it to HTML and cleaning it up as I speak...well, not RIGHT as I speak. :-) pbd -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. On Fri, 11 Apr 1997, David Langford wrote: > I remember this being discussed a little while ago but I dont recall the > specifics. > What are the gotchas for changing the utmp.h file and doing a make world. > > Will FreeBSD t FreeBSD YP work? Sendmail, csh, tcsh etc.... From owner-freebsd-current Fri Apr 11 14:42:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA23554 for current-outgoing; Fri, 11 Apr 1997 14:42:49 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA23538 for ; Fri, 11 Apr 1997 14:42:38 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA12385; Fri, 11 Apr 1997 14:22:45 -0700 From: Terry Lambert Message-Id: <199704112122.OAA12385@phaeton.artisoft.com> Subject: Re: WHY? ...non-use of TAILQ macros... To: phk@dk.tfs.com Date: Fri, 11 Apr 1997 14:22:45 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <1094.860742468@critter> from "phk@dk.tfs.com" at Apr 11, 97 09:07:48 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >On the theory that the TAILQ_xxx macros were being avoided and the > >queue elemments themselves directly refernce for No Good Reason(tm), > >I just compiled the following: > > You're way behind Terry! :-) > > I argued this long time ago and started to introduce the _FIRST, _LAST, > _NEXT, _PREV and _EMPTY macros as I have got to it. > > A patch for this from you would be most welcome of course. I am maintaining several source trees right now on the machine where I have the post-Lite2 merged source repository. I don't have another 10M for another checked out tree, unless I want to truncate some of my build environment. I assume you would want me to run a kernel with these patches installed to make sure it runs and that there are no obvious memory leaks, etc.? Unfortunately, the post Lite2 merge tree on my machine has already got local modifications to bring the namei/nameifree and EXCLUDE vop flag code up to date with -current (I have uploaded today the diffs as taken against the -current tree; they are on freefall in the file ~terry/current-namei.diff). I could do the patch for the macro references (the mail message I sent in this thread already had most of the replacement lines that would result, already, for all tqh_first reference in /sys/kern), but it touches several of the same files, so I would not be able to give you a clean diff without including the namei/nameifree and EXCLUDE stuff. Too bad I can't just branch and check in my changes and check out an untouched tree... CVS is too dumb to let me unbranch later, and the next CVSup would kill me anyway. 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 Fri Apr 11 15:09:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA24842 for current-outgoing; Fri, 11 Apr 1997 15:09:31 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [198.180.136.138]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA24831; Fri, 11 Apr 1997 15:09:22 -0700 (PDT) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.5/8.8.3) id MAA00895; Fri, 11 Apr 1997 12:03:17 -1000 (HST) Message-Id: <199704112203.MAA00895@caliban.dihelix.com> Subject: Re: longer usernames In-Reply-To: from Bradley Dunn at "Apr 11, 97 05:33:42 pm" To: bradley@dunn.org (Bradley Dunn) Date: Fri, 11 Apr 1997 12:03:17 -1000 (HST) Cc: langfod@dihelix.com, freebsd-isp@freebsd.org, freebsd-current@freebsd.org From: "David Langford" X-blank-line: This space intentionaly left blank. 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is great. This is the first time I have seen anyone actually say whether or not FreeBSD to FreeBSD NIS may work. Thank you. -David Langford langfod@dihelix.com >See >http://www.harborcom.net/noc/freebsd/long.html >for a little doc I just hacked up. I am converting it to HTML and cleaning >it up as I speak...well, not RIGHT as I speak. :-) > >pbd > >-- >Democracy is two wolves and a sheep voting on what to have for >dinner. Liberty is two wolves attempting to have a sheep for >dinner and finding a well-informed, well-armed sheep. > >On Fri, 11 Apr 1997, David Langford wrote: > >> I remember this being discussed a little while ago but I dont recall the >> specifics. >> What are the gotchas for changing the utmp.h file and doing a make world. >> >> Will FreeBSD t FreeBSD YP work? Sendmail, csh, tcsh etc.... From owner-freebsd-current Fri Apr 11 15:30:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA26019 for current-outgoing; Fri, 11 Apr 1997 15:30:41 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26012 for ; Fri, 11 Apr 1997 15:30:37 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA19060; Fri, 11 Apr 1997 15:29:11 -0700 (PDT) To: Terry Lambert cc: phk@dk.tfs.com, current@freebsd.org Subject: Re: WHY? ...non-use of TAILQ macros... In-reply-to: Your message of "Fri, 11 Apr 1997 14:22:45 PDT." <199704112122.OAA12385@phaeton.artisoft.com> Date: Fri, 11 Apr 1997 15:29:10 -0700 Message-ID: <19057.860797750@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I don't have another 10M for another checked out tree, unless I want Buy a disk! ;-) Jordan From owner-freebsd-current Fri Apr 11 15:42:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA26655 for current-outgoing; Fri, 11 Apr 1997 15:42:32 -0700 (PDT) Received: from werple.net.au (melb.werple.net.au [203.9.190.18]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA26650 for ; Fri, 11 Apr 1997 15:42:26 -0700 (PDT) Received: (qmail 16072 invoked by uid 5); 11 Apr 1997 22:42:14 -0000 Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id IAA03744; Sat, 12 Apr 1997 08:42:13 +1000 (EST) From: John Birrell Message-Id: <199704112242.IAA03744@freebsd1.cimlogic.com.au> Subject: Re: Bug in libc_r implementation of pthread_cond_wait To: fenyo@email.enst.fr Date: Sat, 12 Apr 1997 08:42:12 +1000 (EST) Cc: current@FreeBSD.org In-Reply-To: <199704111710.TAA20766@nikopol.enst.fr> from Alex Fenyo at "Apr 11, 97 07:10:03 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Alex Fenyo wrote: > > I encountered a problem using pthread_cond_wait() that seems to be > broken : the thread that calls pthread_cond_wait() is always > rescheduled (even if there is no call to pthread_cond_signal() or > other reason to be rescheduled). [...] Fixed in current. Thanks! > Alexandre Fenyo > -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, 119 Cecil Street, South Melbourne Vic 3205, Australia Tel +61 3 9690 6900 Fax +61 3 9690 6650 Mob +61 418 353 137 From owner-freebsd-current Fri Apr 11 15:50:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA26925 for current-outgoing; Fri, 11 Apr 1997 15:50:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA26918 for ; Fri, 11 Apr 1997 15:50:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12512; Fri, 11 Apr 1997 15:29:42 -0700 From: Terry Lambert Message-Id: <199704112229.PAA12512@phaeton.artisoft.com> Subject: Re: WHY? ...non-use of TAILQ macros... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 11 Apr 1997 15:29:42 -0700 (MST) Cc: terry@lambert.org, phk@dk.tfs.com, current@freebsd.org In-Reply-To: <19057.860797750@time.cdrom.com> from "Jordan K. Hubbard" at Apr 11, 97 03:29:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I don't have another 10M for another checked out tree, unless I want > > Buy a disk! ;-) Or you could just integrate the patches and I could quit carrying them around. It would save me the cost of another disk and a hell of a lot of wasted integration time, and it would save you the email I send about it... and free me up to work on other things, like queue macro patches. Sounds like a win-win situation. 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 Fri Apr 11 16:09:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA28064 for current-outgoing; Fri, 11 Apr 1997 16:09:21 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA28058; Fri, 11 Apr 1997 16:09:16 -0700 (PDT) Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id QAA20605; Fri, 11 Apr 1997 16:02:34 -0700 (PDT) Date: Fri, 11 Apr 1997 16:13:32 -0700 (PDT) From: Tom Samplonius To: David Langford cc: Bradley Dunn , freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: longer usernames In-Reply-To: <199704112203.MAA00895@caliban.dihelix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Apr 1997, David Langford wrote: > This is great. This is the first time I have seen anyone actually > say whether or not FreeBSD to FreeBSD NIS may work. > > Thank you. > > -David Langford > langfod@dihelix.com Huh? Why not? FreeBSD NIS is great: myserver# wc /var/yp/master.passwd 12516 25956 933750 /var/yp/master.passwd myserver# That's 12,516 users in a NIS table, and as I understand it, this is a small site. The developer uses NIS in a 30K user environment. Tom From owner-freebsd-current Fri Apr 11 17:24:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA02435 for current-outgoing; Fri, 11 Apr 1997 17:24:18 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [198.180.136.138]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA02412; Fri, 11 Apr 1997 17:24:12 -0700 (PDT) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.5/8.8.3) id OAA01332; Fri, 11 Apr 1997 14:22:44 -1000 (HST) Message-Id: <199704120022.OAA01332@caliban.dihelix.com> Subject: Re: longer usernames In-Reply-To: from Tom Samplonius at "Apr 11, 97 04:13:32 pm" To: tom@uniserve.com (Tom Samplonius) Date: Fri, 11 Apr 1997 14:22:44 -1000 (HST) Cc: langfod@dihelix.com, bradley@dunn.org, freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG From: "David Langford" X-blank-line: This space intentionaly left blank. 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-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius > >On Fri, 11 Apr 1997, David Langford wrote: > >> This is great. This is the first time I have seen anyone actually >> say whether or not FreeBSD to FreeBSD NIS may work. >> >> Thank you. >> >> -David Langford >> langfod@dihelix.com > > Huh? Why not? FreeBSD NIS is great: > >Tom Whoops, no the confusion was whether or not FreeBSD to FreeBSD NIS would work with long user names. In the past discusions it had usually been mentioned that NIS and long user names would cause problems but it was never clear if this was also the cause in homogenious environments. :) -David Langford langfod@dihelix.com From owner-freebsd-current Fri Apr 11 17:45:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA04603 for current-outgoing; Fri, 11 Apr 1997 17:45:35 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04595; Fri, 11 Apr 1997 17:45:31 -0700 (PDT) Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id RAA06896; Fri, 11 Apr 1997 17:38:57 -0700 (PDT) Date: Fri, 11 Apr 1997 17:49:56 -0700 (PDT) From: Tom Samplonius To: David Langford cc: bradley@dunn.org, freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: longer usernames In-Reply-To: <199704120022.OAA01332@caliban.dihelix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Apr 1997, David Langford wrote: > Whoops, no the confusion was whether or not FreeBSD to FreeBSD NIS would > work with long user names. > > In the past discusions it had usually been mentioned that NIS and long > user names would cause problems but it was never clear if this was > also the cause in homogenious environments. Misinformation being passed around by the misinformed. NIS is concerned with key-data pairs, the lengths of those pairs is imposed only by the underlying database (and a couple of other things). Even the SunOS 4.1 implementation of NIS has no problems with longer-usernames, its just that login truncates all user-ids to 8 characters before doing lookups (I guess, it is hard to verify without looking at the code). I did some real brief testing on this. Solaris 2.x has 16 character username support, and it definitely works with NIS. > :) > > -David Langford > langfod@dihelix.com > Tom From owner-freebsd-current Fri Apr 11 17:49:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA05195 for current-outgoing; Fri, 11 Apr 1997 17:49:43 -0700 (PDT) Received: from apolo.biblos.unal.edu.co ([168.176.37.75]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA05167 for ; Fri, 11 Apr 1997 17:49:29 -0700 (PDT) Received: from unalmodem.usc.unal.edu.co (unalmodem00.usc.unal.edu.co [168.176.3.30]) by apolo.biblos.unal.edu.co (8.8.5/8.8.5) with SMTP id TAA10504; Fri, 11 Apr 1997 19:51:37 -0500 (COT) Message-ID: <334E7B16.36E2@fps.biblos.unal.edu.co> Date: Fri, 11 Apr 1997 10:55:34 -0700 From: Pedro Giffuni X-Mailer: Mozilla 3.0 (Win16; I) MIME-Version: 1.0 To: Gang-Ryung Uh CC: current@freebsd.org Subject: Re: netscape4 References: <199704100347.XAA01762@sed.cs.fsu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gang-Ryung Uh wrote: > > Hello, > But, I can not run any applet on this fancy looking new web browser. > Am I missing something? (as always I did before) > I heard some noise in the ports list that this beta is worthless... --Pedro. > Thanks. > > Regards, > Gang-Ryung Uh > (uh@cs.fsu.edu) From owner-freebsd-current Fri Apr 11 18:16:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA06678 for current-outgoing; Fri, 11 Apr 1997 18:16:44 -0700 (PDT) Received: from dyslexic.phoenix.net (root@dyslexic.phoenix.net [199.3.233.7]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA06655; Fri, 11 Apr 1997 18:16:31 -0700 (PDT) Received: (from gemohler@localhost) by dyslexic.phoenix.net (8.8.5/8.7.3) id UAA28258; Fri, 11 Apr 1997 20:12:45 -0500 (CDT) Date: Fri, 11 Apr 1997 20:12:45 -0500 (CDT) From: Geoff Mohler X-Sender: gemohler@dyslexic.phoenix.net To: David Langford cc: Tom Samplonius , langfod@dihelix.com, bradley@dunn.org, freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: longer usernames In-Reply-To: <199704120022.OAA01332@caliban.dihelix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I do know that COPS complaints about long (>8) usernames in the YP maps. =-=-=-=-=- ROMANI ITE DOMUM Geoff Mohler Operations Engineer Charter Communications/Phoenix Data Net From owner-freebsd-current Fri Apr 11 18:17:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA06731 for current-outgoing; Fri, 11 Apr 1997 18:17:32 -0700 (PDT) Received: from heli-fishing.eos.ncsu.edu (heli-fishing.eos.ncsu.edu [152.1.68.52]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA06724 for ; Fri, 11 Apr 1997 18:17:25 -0700 (PDT) Received: (from camattin@localhost) by heli-fishing.eos.ncsu.edu (8.8.4/EC02Jan97) id BAA33210; Sat, 12 Apr 1997 01:17:03 GMT Message-Id: <199704120117.BAA33210@heli-fishing.eos.ncsu.edu> Subject: Re: netscape4 To: pgiffuni@fps.biblos.unal.edu.co (Pedro Giffuni) Date: Fri, 11 Apr 1997 21:17:03 -0400 (EDT) Cc: uh@NU.cs.fsu.edu (Gang-Ryung Uh), current@FreeBSD.ORG In-Reply-To: <334E7B16.36E2@fps.biblos.unal.edu.co> from "Pedro Giffuni" at Apr 11, 1997 10:55:34 AM From: camattin@ncsu.edu (Chris A. Mattingly) Reply-To: camattin@ncsu.edu X-Mailer: ELM [version 2.5 PL0b1/POP] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Pedro Giffuni wrote the following about "Re: netscape4" on Fri Apr 11 13:55:34 1997 > > Gang-Ryung Uh wrote: > > > > Hello, > > But, I can not run any applet on this fancy looking new web browser. > > Am I missing something? (as always I did before) > > > I heard some noise in the ports list that this beta is worthless... Too much like MS Explorer IMHO. -Chris -- Chris Mattingly | My views are not necessarily those of my employers camattin@ncsu.edu | NC State University/ITECS | "Good programmers write good code; great Systems Programmer | programmers 'borrow' good code." -- Mike Gancarz From owner-freebsd-current Fri Apr 11 19:26:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA09044 for current-outgoing; Fri, 11 Apr 1997 19:26:24 -0700 (PDT) Received: from Pkrw.tcn.net (Pkrw.tcn.net [199.166.4.58]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09036 for ; Fri, 11 Apr 1997 19:26:20 -0700 (PDT) Received: from localhost (krw@localhost) by Pkrw.tcn.net (8.8.5/8.8.5) with SMTP id WAA00182; Fri, 11 Apr 1997 22:29:04 -0400 (EDT) X-Authentication-Warning: Pkrw.tcn.net: krw owned process doing -bs Date: Fri, 11 Apr 1997 22:28:43 -0400 (EDT) From: "Kenneth R. Westerback" To: Pedro Giffuni cc: Gang-Ryung Uh , current@freebsd.org Subject: Re: netscape4 In-Reply-To: <334E7B16.36E2@fps.biblos.unal.edu.co> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I too had a problem with getting applets to run with b3 (and b2 for that matter) but recently found a fix. If you get a floating point exception whenever Java starts up (that was my symptom) then check to make sure your X server is running with >256 colours. 256 colours (i.e. bpp 8) is apparently insufficient. When I fixed up my XF86Config so I could 'startx -- -bpp 16' the problems went away and Java works great! Hope this helps! ---- Ken On Fri, 11 Apr 1997, Pedro Giffuni wrote: > Gang-Ryung Uh wrote: > > > > Hello, > > But, I can not run any applet on this fancy looking new web browser. > > Am I missing something? (as always I did before) > > > I heard some noise in the ports list that this beta is worthless... > > > --Pedro. > > > Thanks. > > > > Regards, > > Gang-Ryung Uh > > (uh@cs.fsu.edu) > > > > From owner-freebsd-current Fri Apr 11 21:07:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA11943 for current-outgoing; Fri, 11 Apr 1997 21:07:39 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11938 for ; Fri, 11 Apr 1997 21:07:35 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA25644; Sat, 12 Apr 1997 13:37:29 +0930 (CST) From: Michael Smith Message-Id: <199704120407.NAA25644@genesis.atrad.adelaide.edu.au> Subject: Re: network buglet ? In-Reply-To: <3198.860767164@critter> from "phk@dk.tfs.com" at "Apr 11, 97 03:59:24 pm" To: phk@dk.tfs.com Date: Sat, 12 Apr 1997 13:37:29 +0930 (CST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk phk@dk.tfs.com stands accused of saying: > > Any good explanations for this negative RTT ? xntpd time step? I see those occasionally when our link is spammed and xntpd hiccups because the link latency has changed. > 64 bytes from 194.19.64.133: icmp_seq=216 ttl=245 time=415.414 ms > 64 bytes from 194.19.64.133: icmp_seq=217 ttl=245 time=401.798 ms > 64 bytes from 194.19.64.133: icmp_seq=219 ttl=245 time=399.801 ms > 64 bytes from 194.19.64.133: icmp_seq=221 ttl=245 time=385.142 ms > 64 bytes from 194.19.64.133: icmp_seq=222 ttl=245 time=419.366 ms > 64 bytes from 194.19.64.133: icmp_seq=223 ttl=245 time=-177.755 ms > 64 bytes from 194.19.64.133: icmp_seq=224 ttl=245 time=417.157 ms > 64 bytes from 194.19.64.133: icmp_seq=225 ttl=245 time=667.852 ms > 64 bytes from 194.19.64.133: icmp_seq=226 ttl=245 time=393.256 ms > > -- > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. > http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. > whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. > Future will arrive by its own means, progress not so. > -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri Apr 11 23:49:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA17752 for current-outgoing; Fri, 11 Apr 1997 23:49:40 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA17739; Fri, 11 Apr 1997 23:48:55 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id HAA08217; Sat, 12 Apr 1997 07:45:23 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 12 Apr 1997 07:42:36 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199704111608.LAA00384@watcher.isl.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 12 Apr 1997 07:40:11 +0100 To: ortmann@sparc.isl.net From: Bob Bishop Subject: Re: kern/3259: /bin/ps: kernel kernel, lockups, performance problems Cc: FreeBSD-gnats@freefall.freebsd.org, FreeBSD-current@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Note: I've experienced performance problems as well. These problems >have appeared to be in sendmail, the gcc compiler (a make world >now takes at least 3 times longer than before!) Try 'make world' using an older kernel (Mar 20 or so). If the performance problem goes away, you are probably seeing the same problem that I am. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Sat Apr 12 00:58:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA19759 for current-outgoing; Sat, 12 Apr 1997 00:58:58 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA19749 for ; Sat, 12 Apr 1997 00:58:54 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id KAA17306; Sat, 12 Apr 1997 10:55:15 +0300 (EET DST) From: mika ruohotie Message-Id: <199704120755.KAA17306@shadows.aeon.net> Subject: Re: wdx interrupt timeouts (fwd) In-Reply-To: <199704111037.LAA18207@albatross.mcc.ac.uk> from Ian Pallfreeman at "Apr 11, 97 11:37:05 am" To: ip@mcc.ac.uk Date: Sat, 12 Apr 1997 10:55:15 +0300 (EET DST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Thanks for the suggestion; I probably will, but: > Fatal trap 12: page fault while in kernel mode > shouldn't be happening just because I'm trying to read a possibly (but not > very likely) bad drive, should it? Note the subject line -- this started with i see nothing drive like in that panic, but then again, i'm no panic wiz... to me it looks rather that you just run current (right?) and i have those page faults with it every now and then, not really recently, but few weeks ago i did... reason i'd assume a bad drive rather than ide problem is the fact i am running current with two ide drives, i use 32bit and multi blocks and async,noatime so i would assume i take as much performance out from ide drives i can, yet not having problems you do... and as i said, when my last ide broke (after one year on all the time), i had similar errors... it's bit over a year ago so i dont remember exactly, still i would bet on bad drive. > onto panics. I hate IDE, even brand-new supposedly self-correcting drives... ditto. but until i have the money, i have to live with them. > I'm also stuck at first base with the crash dump: > > Any suggestions, offers of help, or brain transplants gratefully receieved... check the handbook? i got bit further with it, not that i got any more enlighted though. it's in the section 20.1, and too much to cut&paste... =) > "Why does it always happen to me?" coz we let mr murphy to born? =) > Ian. mickey From owner-freebsd-current Sat Apr 12 04:18:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA26439 for current-outgoing; Sat, 12 Apr 1997 04:18:37 -0700 (PDT) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA26432 for ; Sat, 12 Apr 1997 04:18:30 -0700 (PDT) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id EAA10836 for ; Sat, 12 Apr 1997 04:20:42 -0700 (PDT) Received: (qmail 18559 invoked by uid 110); 12 Apr 1997 06:45:50 -0000 Message-ID: <19970412064550.18557.qmail@suburbia.net> Subject: Re: WHY? ...non-use of TAILQ macros... In-Reply-To: <334E7ED4.794BDF32@whistle.com> from Julian Elischer at "Apr 11, 97 11:11:32 am" To: julian@whistle.com (Julian Elischer) Date: Sat, 12 Apr 1997 16:45:49 +1000 (EST) Cc: wollman@khavrinen.lcs.mit.edu, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Garrett Wollman wrote: > > > > < said: > > > > >> > kern_lockf.c: while (ltmp = overlap->lf_blkhd.tqh_first) { > > > > >> 2. Because they are unnecessary. > > > > > Well, that begs the question of qhy they are being used in declarations > > > and elsewhere, then, doesn't it? > > > > I never said that the declaration macros were unnecessary. I said > > that macros like TAILQ_FIRST are unnecessary. Some people disagree > > (notably David G. and Justin). > > and me > And me. Either somthing is encapsulated or it is not. It isn't desireable to have internals "leaking out" like this. -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@suburbia.net |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-current Sat Apr 12 09:19:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA09345 for current-outgoing; Sat, 12 Apr 1997 09:19:58 -0700 (PDT) Received: from chess.inetspace.com ([206.50.163.14]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09321; Sat, 12 Apr 1997 09:19:30 -0700 (PDT) Received: (from kgor@localhost) by chess.inetspace.com (8.8.5/8.7.3) id LAA11963; Sat, 12 Apr 1997 11:18:45 -0500 (CDT) Date: Sat, 12 Apr 1997 11:18:45 -0500 (CDT) Message-Id: <199704121618.LAA11963@chess.inetspace.com> From: "Kent S. Gordon" To: rb@gid.co.uk CC: ortmann@sparc.isl.net, FreeBSD-gnats@freefall.freebsd.org, FreeBSD-current@freefall.freebsd.org In-reply-to: (message from Bob Bishop on Sat, 12 Apr 1997 07:40:11 +0100) Subject: Re: kern/3259: /bin/ps: kernel kernel, lockups, performance problems Mime-Version: 1.0 (generated by tm-edit 7.105) Content-Type: text/plain; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> "rb" == Bob Bishop writes: >> Note: I've experienced performance problems as well. These >> problems have appeared to be in sendmail, the gcc compiler (a >> make world now takes at least 3 times longer than before!) > Try 'make world' using an older kernel (Mar 20 or so). If the > performance problem goes away, you are probably seeing the same > problem that I am. My 586/100 16MB bt445 machine does not even successfully boot with a kernel newer than about Mar 20. It hangs in boot trying to find the boot disk (or finds it as a unknown device type depending on options in the kernel config and whick -current is used). > -- Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK Kent S. Gordon Senior Software Engineer INetSpace Co. voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com From owner-freebsd-current Sat Apr 12 10:44:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA12833 for current-outgoing; Sat, 12 Apr 1997 10:44:50 -0700 (PDT) Received: from veda.is (veda.is [193.4.230.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA12824; Sat, 12 Apr 1997 10:44:41 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.8.4) id RAA26331; Sat, 12 Apr 1997 17:44:39 GMT From: Adam David Message-Id: <199704121744.RAA26331@veda.is> Subject: Re: longer usernames In-Reply-To: from Jacob Suter at "Apr 11, 97 11:47:23 am" To: jsuter@linus.intrastar.net (Jacob Suter) Date: Sat, 12 Apr 1997 17:44:39 +0000 (GMT) Cc: freebsd-isp@freebsd.org, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It would appear it support 16 charector limits right now on my stock > 2.2.1r boxes. I haven't tested it though. Would someone please tell me how to enable 16-char logins on stock 2.2.1R, much appreciated. (still Cc: current because this is "recent") -- Adam David From owner-freebsd-current Sat Apr 12 12:48:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA18194 for current-outgoing; Sat, 12 Apr 1997 12:48:51 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA18188; Sat, 12 Apr 1997 12:48:44 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA15601; Sat, 12 Apr 1997 12:26:53 -0700 From: Terry Lambert Message-Id: <199704121926.MAA15601@phaeton.artisoft.com> Subject: Re: longer usernames To: tom@uniserve.com (Tom Samplonius) Date: Sat, 12 Apr 1997 12:26:52 -0700 (MST) Cc: langfod@dihelix.com, bradley@dunn.org, freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Apr 11, 97 05:49:56 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Misinformation being passed around by the misinformed. NIS is concerned > with key-data pairs, the lengths of those pairs is imposed only by the > underlying database (and a couple of other things). > > Even the SunOS 4.1 implementation of NIS has no problems with > longer-usernames, its just that login truncates all user-ids to 8 > characters before doing lookups (I guess, it is hard to verify without > looking at the code). I did some real brief testing on this. > > Solaris 2.x has 16 character username support, and it definitely works > with NIS. Yes; the problem is interoperability with systems which have historically truncated login names to 8 characters; all accounts more than 8 characters will be useless on these systems when they are configured as clients of a system which supports more than 8 character names. So if you support more than 8 character names, and send them out via NIS, older SGI, MIPS, Pyramid, and SVR3/SVR4 NIS clients will be unable to log into any account with a long name. In a homogeneous environment, there is no problem. In an environment with Solaris 2.x, there is no interoperability problem as long as you geep the names shorter than 17 characters. In other words, over 8 characters, the behaviour is undefined in all but homogeneous environments, with the above documented exceptions. Feel free to buy one of each type of UNIX box ever built, and run each OS release they've ever had, and document the remaining exceptions in a cannonical list. 8-) 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 Sat Apr 12 14:54:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA24537 for current-outgoing; Sat, 12 Apr 1997 14:54:56 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA24528; Sat, 12 Apr 1997 14:54:53 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id OAA11171; Sat, 12 Apr 1997 14:54:43 -0700 (PDT) To: Adam David cc: jsuter@linus.intrastar.net (Jacob Suter), freebsd-isp@freebsd.org, freebsd-current@freebsd.org Subject: Re: longer usernames In-reply-to: Your message of "Sat, 12 Apr 1997 17:44:39 -0000." <199704121744.RAA26331@veda.is> Date: Sat, 12 Apr 1997 14:54:41 -0700 Message-ID: <11156.860882081@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > It would appear it support 16 charector limits right now on my stock > > 2.2.1r boxes. I haven't tested it though. > > Would someone please tell me how to enable 16-char logins on stock 2.2.1R, > much appreciated. Use the search tool, Luke! :-) Jordan From owner-freebsd-current Sat Apr 12 16:02:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA29105 for current-outgoing; Sat, 12 Apr 1997 16:02:03 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA29095 for ; Sat, 12 Apr 1997 16:01:59 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wGBnx-0004Xt-00; Sat, 12 Apr 1997 17:01:57 -0600 To: current@freebsd.org Subject: make world from 2.1.6R buys the farm many times Date: Sat, 12 Apr 1997 17:01:57 -0600 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There are boatloads of problems installing 2.1.6R and then hoping a make world will get you current. Is there any interest in fixing them? Warner From owner-freebsd-current Sat Apr 12 17:39:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA05771 for current-outgoing; Sat, 12 Apr 1997 17:39:18 -0700 (PDT) Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA05747; Sat, 12 Apr 1997 17:39:09 -0700 (PDT) Received: (from davidn@localhost) by unique.usn.blaze.net.au (8.8.5/8.8.5) id KAA01871; Sun, 13 Apr 1997 10:38:56 +1000 (EST) Message-ID: <19970413103855.23362@usn.blaze.net.au> Date: Sun, 13 Apr 1997 10:38:55 +1000 From: David Nugent To: "Jordan K. Hubbard" Cc: Adam David , Jacob Suter , freebsd-isp@freebsd.org, freebsd-current@freebsd.org Subject: Re: longer usernames References: <199704121744.RAA26331@veda.is> <11156.860882081@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <11156.860882081@time.cdrom.com>; from Jordan K. Hubbard on Sat Apr 12 14:54:41 EST 1997 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat Apr 12 14:54:41 EST 1997, Jordan K. Hubbard writes: > > > It would appear it support 16 charector limits right now on my stock > > > 2.2.1r boxes. I haven't tested it though. > > > > Would someone please tell me how to enable 16-char logins on stock 2.2.1R, > > much appreciated. > > Use the search tool, Luke! :-) And cvs log entries. There were a few other subtle changes that have leaked through since. FWIW, FreeBSD-current supports *15* character login names, not 16. In addition to the headers, there was a problem with the 'proc' struct in the kernel (setlogin(), I think) and a few userland changes involved as well where the size was assumed to be 8. The only unresolved problem I know about is in libskey, which currently truncates the size of the username to significant characters [skeylogin.c]. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Sat Apr 12 19:40:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA11194 for current-outgoing; Sat, 12 Apr 1997 19:40:02 -0700 (PDT) Received: from mailhost (user-37kb4h1.dialup.mindspring.com [207.69.146.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA11158 for ; Sat, 12 Apr 1997 19:39:58 -0700 (PDT) Received: from rlb by mailhost with smtp (Smail3.1.29.1 #1) id m0wGFCs-000G0KC; Sat, 12 Apr 97 22:39 EDT Message-ID: <33504778.48E6@mindspring.com> Date: Sat, 12 Apr 1997 22:39:52 -0400 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: IPFILTER 2.2RELENG_2_2 Broke Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I had ipfilter ip_fil3.2a4 working with releng_2_2 until I cvsup today. Now the modload routine will not load any modules. Is there any plan to integrate ipfilter into 2.2.X like 3.0 is in contrib? Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ http://rlb.users.mindspring.com gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 Work: 770-263-2411 From owner-freebsd-current Sat Apr 12 21:42:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA15240 for current-outgoing; Sat, 12 Apr 1997 21:42:43 -0700 (PDT) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.57.99]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA15235 for ; Sat, 12 Apr 1997 21:42:39 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.5/3.4W4) with ESMTP id NAA07247 for ; Sun, 13 Apr 1997 13:42:26 +0900 (JST) Message-Id: <199704130442.NAA07247@gneiss.eps.nagoya-u.ac.jp> To: current@freebsd.org Subject: libc stuffs in sys/miscfs/union should be removed X-Mailer: Mew version 1.69 on Emacs 19.28.1 / Mule 2.3 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 Date: Sun, 13 Apr 1997 13:42:25 +0900 From: KATO Takenori Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In the directory /sys/misc/union contains files in libc/gen. 1. The file libc.readdir.c is identical to libc/gen/readdir.c. 2. The difference between libc.fts.c and libc/gen/fts.c may not be functional change. 3. The file libc/gen/opendir.c supports whiteout, now (c.f. log of revsion 1.5). So, I think above files and README should be removed. ---- 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 Sat Apr 12 21:57:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA15740 for current-outgoing; Sat, 12 Apr 1997 21:57:43 -0700 (PDT) Received: from perki0.connect.com.au (perki0.connect.com.au [192.189.54.85]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA15733 for ; Sat, 12 Apr 1997 21:57:40 -0700 (PDT) Received: from nemeton.UUCP (Unemeton@localhost) by perki0.connect.com.au with UUCP id OAA09642 (8.8.5/IDA-1.6); Sun, 13 Apr 1997 14:57:33 +1000 (EST) Received: from topaz.nemeton.com.au (topaz.nemeton.com.au [203.8.3.18]) by nemeton.com.au (8.8.5/8.8.5) with ESMTP id OAA07222; Sun, 13 Apr 1997 14:40:10 +1000 (EST) Received: from localhost.nemeton.com.au (localhost.nemeton.com.au [127.0.0.1]) by topaz.nemeton.com.au (8.8.5/8.8.5) with SMTP id OAA01481; Sun, 13 Apr 1997 14:40:23 +1000 (EST) Message-Id: <199704130440.OAA01481@topaz.nemeton.com.au> To: Warner Losh cc: current@freebsd.org Subject: Re: make world from 2.1.6R buys the farm many times In-reply-to: Date: Sun, 13 Apr 1997 14:40:21 +1000 From: Giles Lean Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Apr 1997 17:01:57 -0600 Warner Losh wrote: > There are boatloads of problems installing 2.1.6R and then hoping a > make world will get you current. > > Is there any interest in fixing them? Nah, not here. 2.2-BETA built a then -current OK via 'make world'. If there are problems building from 2.2.1R then they might be worth fixing, but from 2.1.7? Giles From owner-freebsd-current Sat Apr 12 22:39:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA17020 for current-outgoing; Sat, 12 Apr 1997 22:39:34 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA17001 for ; Sat, 12 Apr 1997 22:39:31 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wGHx4-0004tE-00; Sat, 12 Apr 1997 23:35:46 -0600 To: Giles Lean Subject: Re: make world from 2.1.6R buys the farm many times Cc: current@freebsd.org In-reply-to: Your message of "Sun, 13 Apr 1997 14:40:21 +1000." <199704130440.OAA01481@topaz.nemeton.com.au> References: <199704130440.OAA01481@topaz.nemeton.com.au> Date: Sat, 12 Apr 1997 23:35:46 -0600 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199704130440.OAA01481@topaz.nemeton.com.au> Giles Lean writes: : Nah, not here. 2.2-BETA built a then -current OK via 'make world'. : If there are problems building from 2.2.1R then they might be worth : fixing, but from 2.1.7? OK. In 10-15 days it won't matter to me any more either. Or whenever the 2.2.1 CDROMs are ready. The problems that I've encountered so far relate to flags to ld in the make depend part of the builds, and dependencies in xinstall (or was that ls) on -current only features. Or at least post 2.1 features. This prevented even make bootstrap from working. If it was only one problem, I'd likely try to fix it. Since it seems to be multiple problems, I'm likely going to give it a miss. The new system is fast, but it isn't that fast. At least not with the JAZ drive I'm using for root and swap. Maybe the Quantum Fireball that I'm getting will be significantly faster. Warner From owner-freebsd-current Sat Apr 12 22:55:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA17656 for current-outgoing; Sat, 12 Apr 1997 22:55:31 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17651 for ; Sat, 12 Apr 1997 22:55:27 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id PAA21403; Sun, 13 Apr 1997 15:50:16 +1000 Date: Sun, 13 Apr 1997 15:50:16 +1000 From: Bruce Evans Message-Id: <199704130550.PAA21403@godzilla.zeta.org.au> To: current@freebsd.org, kato@eclogite.eps.nagoya-u.ac.jp Subject: Re: libc stuffs in sys/miscfs/union should be removed Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >In the directory /sys/misc/union contains files in libc/gen. >... >So, I think above files and README should be removed. Go ahead and remove them. I thought that we already removed some of them and Lite2 brought the removed ones back, but I can't see any evidence of this in the history. Bruce From owner-freebsd-current Sat Apr 12 22:56:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA17717 for current-outgoing; Sat, 12 Apr 1997 22:56:18 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17710 for ; Sat, 12 Apr 1997 22:56:14 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id PAA21481; Sun, 13 Apr 1997 15:52:30 +1000 Date: Sun, 13 Apr 1997 15:52:30 +1000 From: Bruce Evans Message-Id: <199704130552.PAA21481@godzilla.zeta.org.au> To: current@freebsd.org, kato@eclogite.eps.nagoya-u.ac.jp Subject: Re: libc stuffs in sys/miscfs/union should be removed Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 2. The difference between libc.fts.c and libc/gen/fts.c may not be > functional change. PS: libc.fts.c is identical with Lite2's libc/gen/fts.c. Bruce From owner-freebsd-current Sat Apr 12 22:56:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA17760 for current-outgoing; Sat, 12 Apr 1997 22:56:44 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17747 for ; Sat, 12 Apr 1997 22:56:40 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA17135; Sat, 12 Apr 1997 22:56:23 -0700 (PDT) To: Warner Losh cc: Giles Lean , current@freebsd.org Subject: Re: make world from 2.1.6R buys the farm many times In-reply-to: Your message of "Sat, 12 Apr 1997 23:35:46 MDT." Date: Sat, 12 Apr 1997 22:56:22 -0700 Message-ID: <17132.860910982@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In message <199704130440.OAA01481@topaz.nemeton.com.au> Giles Lean writes: > : Nah, not here. 2.2-BETA built a then -current OK via 'make world'. > : If there are problems building from 2.2.1R then they might be worth > : fixing, but from 2.1.7? > > OK. In 10-15 days it won't matter to me any more either. Or whenever > the 2.2.1 CDROMs are ready. Good opportunity as any to say this I guess: They'll be here in 3 more days! Hurrah! Jordan