From owner-freebsd-current Sun May 11 00:54:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA17228 for current-outgoing; Sun, 11 May 1997 00:54:49 -0700 (PDT) Received: from almond.elite.net (root@almond.elite.net [205.199.220.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA17223 for ; Sun, 11 May 1997 00:54:47 -0700 (PDT) Received: (from jpm@localhost) by almond.elite.net (8.8.3/ELITE) id AAA02653; Sun, 11 May 1997 00:54:46 -0700 (PDT) From: Jon Moldenhauer Message-Id: <199705110754.AAA02653@almond.elite.net> Subject: Re: "java" bytecode working in -current? To: ortmann@sparc.isl.net (Daniel Ortmann) Date: Sun, 11 May 1997 00:54:46 -0700 (PDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199705110230.VAA00377@watcher.isl.net> from "Daniel Ortmann" at May 10, 97 09:30:42 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Two quick questions: > 1) Is anyone able to run kaffe on 3.0-current? I have an older vesion of 3.0-current on which kaffe runs just fine (my 3.0-current was built 2 or 3 days before the Lite-2 merge). > 2) May I expect serious stability difficulties with "java" on -current? My experience has been generally good, but if you have problems then you could try running the java programs under Netscape or try using kaffe in interpreter only mode (disable the just-in-time compiler). Jonathon jpm@elite.net From owner-freebsd-current Sun May 11 01:40:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18638 for current-outgoing; Sun, 11 May 1997 01:40:12 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18624; Sun, 11 May 1997 01:40:07 -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 JAA05939; Sun, 11 May 1997 09:39:58 +0100 (BST) Date: Sun, 11 May 1997 09:39:58 +0100 (BST) From: Doug Rabson To: "Jordan K. Hubbard" cc: current@freebsd.org, announce@freebsd.org Subject: Re: A 3.0-current SNAP building machine has been found! In-Reply-To: <18077.863238129@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 Fri, 9 May 1997, Jordan K. Hubbard wrote: > ACC TelEnterprises & James FitzGibbon have stepped forward and > created, how shall I put it, a very *attractively* configured and > connected machine for this purpose, complete with administrative > support. > > Therefore, once I have it set up to start building SNAPs, I'll start > up the cron job and have David G. point "current.freebsd.org" at this > machine so that it people can ftp the latest 3.0-SNAPs from it in the > same way they currently have releng22.freebsd.org for the RELENG_2_2 > (2.2-stable) branch. > > Of course, this raises an interesting question: Now that it's truly > possible to get daily releases from the 3.0 & 2.2 bits (and, if > someone else is still up to volunteer a box, I guess we could also > create a releng210.freebsd.org for the 2.1-stable branch?) - what > differentiates a "good" one from a bad one? Which ones should we copy > over to ftp.freebsd.org, periodically? > > I suppose that Terry will now suggest some sort of voting system and I > can't even say that it's such a bad idea (just so long as I don't have > to write the vote collection and tabulation software :-). At Micro$oft, we used the daily build system for everything. If you weren't working on it though, you didn't just install a random build of Win95. There were usually a few 'known good builds' which were worth installing. Not sure how you can figure out automatically what a 'good build' is though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Sun May 11 01:40:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18678 for current-outgoing; Sun, 11 May 1997 01:40:55 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18673 for ; Sun, 11 May 1997 01:40:52 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id IAA03675; Sun, 11 May 1997 08:40:33 GMT Date: Sun, 11 May 1997 17:40:33 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: ac199@hwcn.org, freebsd-current@FreeBSD.ORG Subject: Re: byacc and Perl In-Reply-To: <199705101949.MAA04349@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 Sat, 10 May 1997, Terry Lambert wrote: > > > Would upgrading byacc to the Perl capable version cause any uproar? For > > > example you can do: > > > > If you want to have real fun, try the Java-capable version! :-) > > (Search Yahoo for "byacc/java") > > I have, with the permission of the maintainer, added C++ code > generation support to yacc (it generates interface implementations > for a yacc parser class). > > I expected to merge the Perl and Java generation into the code > as part of the cleanup. Great! > Has anyone else (besides me) contacted the official maintainer? Yacc in our tree hasn't been touched for quite awhile aside from the recent -o addition. Is Robert Corbett actively maintaining yacc and if so how far out of sync are we? I was browsing the source and noticed transitive closure routines in it. Kinda figures doesn't it? ;-) Regards, Mike Hancock From owner-freebsd-current Sun May 11 01:59:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA19193 for current-outgoing; Sun, 11 May 1997 01:59:06 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA19188; Sun, 11 May 1997 01:59:03 -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 JAA05979; Sun, 11 May 1997 09:58:11 +0100 (BST) Date: Sun, 11 May 1997 09:58:11 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: hackers@freebsd.org, current@freebsd.org Subject: Re: PATCHES: NFS server locking support In-Reply-To: <199705090127.SAA29328@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, 8 May 1997, Terry Lambert wrote: > > I have just uploaded patches for kernel support of NFS server locking. > > They are on freefall in the file: > > ~terry/LOCK.DIFF Thanks Terry! I won't have time to look at this today but I will definitely look at this early next week. It seems likely that I can commit most of this stuff. The NAMEI changes are, I think, the right way to go and (without actually reading the diff) shouldn't take us too much farther away from the 4.4BSD line. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-current Sun May 11 03:03:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA21036 for current-outgoing; Sun, 11 May 1997 03:03:49 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA21031 for ; Sun, 11 May 1997 03:03:45 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA15908 for freebsd-current@FreeBSD.org; Sun, 11 May 1997 12:03:43 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id MAA00341; Sun, 11 May 1997 12:01:55 +0200 (MET DST) Message-ID: <19970511120155.RZ16393@uriah.heep.sax.de> Date: Sun, 11 May 1997 12:01:55 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: cx(4) anybody? 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) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hiya, is anybody using the cx(4) (Cronyx HDLC) driver, together with sync PPP? I plan to reuse Serge Vakulenko's sync PPP layer (/sys/net/if_sppp*) for PPP over ISDN. I will shortly commit a first change that improves the debug output, and plan to add further improvements. If anybody is using it on cx(4) (where it has originally been written for), i would like to hear from you so to make sure i don't break this. Before you're asking: the sppp layer has a clear API towards the HDLC layer, and ISDN is basically in the same boat as the cx(4) hardware HDLC here, so this makes sppp much more attractive than the existing (async) kernel ppp. I've already got it talk LCP (though they still don't negotiate successfully), and this was with about one day of work. -- 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 May 11 04:32:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA24524 for current-outgoing; Sun, 11 May 1997 04:32:19 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA24518 for ; Sun, 11 May 1997 04:32:17 -0700 (PDT) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by agora.rdrop.com (8.8.5/8.8.5) with SMTP id EAA19490 for ; Sun, 11 May 1997 04:26:45 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id RAA04359 for current@freebsd.org; Sun, 11 May 1997 17:40:05 +0700 Received: by itfs.nsk.su; Sun, 11 May 97 18:08:57 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.7.5/8.6.12) id RAA09591; Sun, 11 May 1997 17:49:02 +0700 (NSD) From: "Nickolay N. Dudorov" To: current@freebsd.org Subject: Re: cx(4) anybody? Date: 11 May 1997 10:49:00 GMT Message-ID: <5l486t$7ru@news.itfs.nsk.su> References: <19970511120155.RZ16393@uriah.heep.sax.de> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > Hiya, > is anybody using the cx(4) (Cronyx HDLC) driver, together with sync > PPP? It seems to me that the situation with this driver in FreeBSD is not so normal ;-) Authors of hardware (Cronyx Sigma adapters) long ago have commited driver in FreeBSD and "forget about it" ... They have now new version of this driver (with some preliminary Frame Relay support even) on their Web. page (www.cronyx.ru). As I can see support of this driver in compilable and even working state was done by some generous people but not by authors ;-( May be your interest to their software can change the situation now ? N.Dudorov P.S. Yes, I use cx driver with sync PPP now in FreeBSD-2.2 of about august 1996 with some patches from author's version of about december 1996 and this is even my base link to Internet and due to that reason I can not test your possible patches for 3.0 or even 2.2-CURRENT ;-( From owner-freebsd-current Sun May 11 04:46:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA25129 for current-outgoing; Sun, 11 May 1997 04:46:22 -0700 (PDT) Received: from X2296 (ppp6470.on.sympatico.ca [206.172.208.62]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA25119 for ; Sun, 11 May 1997 04:46:17 -0700 (PDT) Received: from localhost (tim@localhost) by X2296 (8.7.6/8.7.3) with SMTP id HAA00230; Sun, 11 May 1997 07:44:57 -0400 (EDT) Date: Sun, 11 May 1997 07:44:56 -0400 (EDT) From: Tim Vanderhoek Reply-To: ac199@hwcn.org To: Michael Hancock cc: Terry Lambert , ac199@hwcn.org, freebsd-current@FreeBSD.ORG Subject: Re: byacc and Perl In-Reply-To: Message-ID: X-OS: FreeBSD 2.2 X-Mailer: Pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 11 May 1997, Michael Hancock wrote: > Yacc in our tree hasn't been touched for quite awhile aside from the > recent -o addition. Is Robert Corbett actively maintaining yacc and if so > how far out of sync are we? Speaking of which, when the -o was added back to yacc, somebody forgot to add it to the manpage. Grab the diffs from yacc.1 Rev 1.1 -> Rev 1.2 and apply... -- tIM...HOEk Whoever told you I had a .signature was lying. From owner-freebsd-current Sun May 11 08:59:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA02276 for current-outgoing; Sun, 11 May 1997 08:59:46 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA02268 for ; Sun, 11 May 1997 08:59:43 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id OAA03943; Sun, 11 May 1997 14:06:00 +0200 (SAT) From: John Hay Message-Id: <199705111206.OAA03943@zibbi.mikom.csir.co.za> Subject: Re: cx(4) anybody? In-Reply-To: <19970511120155.RZ16393@uriah.heep.sax.de> from J Wunsch at "May 11, 97 12:01:55 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 11 May 1997 14:06:00 +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 > > is anybody using the cx(4) (Cronyx HDLC) driver, together with sync > PPP? It is also being used by the Arnet/Digi SYNC570i ar(4) and SDL RISCom/N2 sr(4) cards. I do have both cards here so I can test it. > > Before you're asking: the sppp layer has a clear API towards the HDLC > layer, and ISDN is basically in the same boat as the cx(4) hardware > HDLC here, so this makes sppp much more attractive than the existing > (async) kernel ppp. I've already got it talk LCP (though they still > don't negotiate successfully), and this was with about one day of > work. > I would be interrested in the ISDN stuff too, if it is for a card that I can get here in South Africa.... and if it will work with our telco. :-/ John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Sun May 11 09:11:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02643 for current-outgoing; Sun, 11 May 1997 09:11:57 -0700 (PDT) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.19.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02636; Sun, 11 May 1997 09:11:54 -0700 (PDT) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id MAA28152; Sun, 11 May 1997 12:11:51 -0400 (EDT) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id MAA10855; Sun, 11 May 1997 12:10:31 -0400 Date: Sun, 11 May 1997 12:10:31 -0400 Message-Id: <199705111610.MAA10855@jenolan.caipgeneral> From: "David S. Miller" To: terry@lambert.org CC: terry@lambert.org, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <199705091734.KAA00646@phaeton.artisoft.com> (message from Terry Lambert on Fri, 9 May 1997 10:34:42 -0700 (MST)) Subject: Re: PATCHES: NFS server locking support Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Terry Lambert Date: Fri, 9 May 1997 10:34:42 -0700 (MST) For people without freefall accounts, these files have also been placed for FTP at: ftp://cdrom.com/pub/FreeBSD/incoming/TERRY.LOCK.README ftp://cdrom.com/pub/FreeBSD/incoming/TERRY.LOCK.DIFF ftp://cdrom.com/pub/FreeBSD/incoming/TERRY.NAMEI.FREEZE Can someone put these somewhere where they can be read? From owner-freebsd-current Sun May 11 10:11:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04956 for current-outgoing; Sun, 11 May 1997 10:11:30 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04951 for ; Sun, 11 May 1997 10:11:27 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.7.6/8.7.3) id TAA06018; Sun, 11 May 1997 19:09:52 +0200 (MET DST) Date: Sun, 11 May 1997 19:09:52 +0200 (MET DST) Message-Id: <199705111709.TAA06018@bitbox.follo.net> From: Eivind Eklund To: Terry Lambert CC: current@FreeBSD.ORG In-reply-to: Terry Lambert's message of Sat, 10 May 1997 12:43:05 -0700 (MST) Subject: Regression tests (was Re: A 3.0-current SNAP building machine has been found!) References: <18077.863238129@time.cdrom.com> <199705101943.MAA04327@phaeton.artisoft.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Cc: to announce removed - PLEASE do this for any other followups in the same thread! > > I suppose that Terry will now suggest some sort of voting system and I > > can't even say that it's such a bad idea (just so long as I don't have > > to write the vote collection and tabulation software :-). > > > > Comments? > > I was actually against using "voting"; I prefer forcing developers to > verify that compiles work and the resulting code does not trivially > fail prior to it being committed. That way the tree would always work; > the best you can get out of "voting" is "provided with high confidence > that it might work". Regression tests. We really should have this integrated into the build system. I have been thinking a bit about this, but haven't come up with any system I feel entirely satisfied with yet, and thus haven't brought it up for discussion (Besides, I have a lot of other FreeBSD-related projects not completed yet, and thus feel a bit timid). For my personal projects, I use one of the following systems (depending on the size/complexity of the project): -DTEST - every source file define a main(), and calling this return OK if the test passes or is not present. If the test fails, the program print a message and exit with failure. Advantages: Extremely simple, requires thought about writing testable code Disadvantages: Often too simple, requires thought about writing testable code -DREGRESS - Each object file exports _regress(), and a new source file is created calling each of these. The auto-generated file is compiled and called. Advantages: Fairly simple, allow dependencies between modules. Still requires thought about testability. Disadvantages: Often too simple. None of the above adapt well to a large established code base. :-( I'd guess we need a combination of something like -DREGRESS, as well as a directory with shell scripts to run to test. These could then do the necessary creation of datafiles and actual testing. They should probably be run in a pre-set order, to allow a later test to depend on a former test and the datafiles created by it. (This might mean that a Makefile for them would be a good idea.) Anyway; being able to do a 'make regress' on the entire FreeBSD source tree and know all new code and a lot of old code got tested would be a _good_ feeling. Eivind. From owner-freebsd-current Sun May 11 12:02:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09323 for current-outgoing; Sun, 11 May 1997 12:02:53 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09318 for ; Sun, 11 May 1997 12:02:50 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA05834; Sun, 11 May 1997 11:57:24 -0700 From: Terry Lambert Message-Id: <199705111857.LAA05834@phaeton.artisoft.com> Subject: Re: Regression tests (was Re: A 3.0-current SNAP building machine has been found!) To: perhaps@yes.no (Eivind Eklund) Date: Sun, 11 May 1997 11:57:24 -0700 (MST) Cc: terry@lambert.org, current@FreeBSD.ORG In-Reply-To: <199705111709.TAA06018@bitbox.follo.net> from "Eivind Eklund" at May 11, 97 07:09: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 > > I was actually against using "voting"; I prefer forcing developers to > > verify that compiles work and the resulting code does not trivially > > fail prior to it being committed. That way the tree would always work; > > the best you can get out of "voting" is "provided with high confidence > > that it might work". > > Regression tests. We really should have this integrated into the > build system. This is scary, in that it starts requiring developers to have "big iron". The POSIX tests (for example) take a while to run. [ ... ] > Anyway; being able to do a 'make regress' on the entire FreeBSD > source tree and know all new code and a lot of old code got tested > would be a _good_ feeling. Yes, very much so! I would limit its application, though; if the CVS went "split tree with snapshot", then the process could be automated, but it's probably too much overhead otherwise. 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 Sun May 11 12:29:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10042 for current-outgoing; Sun, 11 May 1997 12:29:24 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA10037; Sun, 11 May 1997 12:29:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA06039; Sun, 11 May 1997 12:24:29 -0700 From: Terry Lambert Message-Id: <199705111924.MAA06039@phaeton.artisoft.com> Subject: CHANGED PATCHES: NFS server locking support To: davem@jenolan.rutgers.edu (David S. Miller) Date: Sun, 11 May 1997 12:24:28 -0700 (MST) Cc: terry@lambert.org, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199705111610.MAA10855@jenolan.caipgeneral> from "David S. Miller" at May 11, 97 12:10:31 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 Well, I was playing with NFS client locking support a bit (nothing that I'm willing to release at this point; the net access code is seriously gross, given the way NFS sockets are handled by the nfs_mount command: Bletch!). It seems that the patches would work the way they are for the existing code, since a veto never occurs... but would fail to remove the provisional locks in the veto case. Go figure. 8-). In any case, I've updated the patches (added a "discard" parameter to lf_commit() for the veto case) and everything seems to be working. > For people without freefall accounts, these files have also been placed > for FTP at: > > ftp://cdrom.com/pub/FreeBSD/incoming/TERRY.LOCK.README > ftp://cdrom.com/pub/FreeBSD/incoming/TERRY.LOCK.DIFF > ftp://cdrom.com/pub/FreeBSD/incoming/TERRY.NAMEI.FREEZE > > Can someone put these somewhere where they can be read? I have taken ben@narcissus.ml.org (Snob Art Genre) up on his offer; the files can be found at: ftp://narcissus.ml.org/incoming/TERRY.LOCK.DIFF ftp://narcissus.ml.org/incoming/TERRY.LOCK.DIFF.README ftp://narcissus.ml.org/incoming/TERRY.NAMEI.DIFF.FREEZE Let me know if anyone finds any problems. 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 Sun May 11 14:12:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13025 for current-outgoing; Sun, 11 May 1997 14:12:45 -0700 (PDT) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA13020 for ; Sun, 11 May 1997 14:12:41 -0700 (PDT) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA21142; Sun, 11 May 97 23:13:14 +0100 Date: Sun, 11 May 97 23:13:14 +0100 Message-Id: <9705112213.AA21142@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: current@freebsd.org Subject: no luck with make world X-Mailer: Emacs Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cc -O2 -m486 -pipe -c /u3/src/usr.bin/tip/tip/hunt.c In file included from /u3/src/usr.bin/tip/tip/hunt.c:38: /usr/include/libutil.h:47: parse error before `uid_t' *** Error code 1 Missing #include Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Sun May 11 14:21:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13306 for current-outgoing; Sun, 11 May 1997 14:21:08 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13301 for ; Sun, 11 May 1997 14:21:05 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.7.6/8.7.3) id XAA09282; Sun, 11 May 1997 23:19:22 +0200 (MET DST) Date: Sun, 11 May 1997 23:19:22 +0200 (MET DST) Message-Id: <199705112119.XAA09282@bitbox.follo.net> From: Eivind Eklund To: Terry Lambert CC: perhaps@yes.no, current@FreeBSD.ORG In-reply-to: Terry Lambert's message of Sun, 11 May 1997 11:57:24 -0700 (MST) Subject: Re: Regression tests (was Re: A 3.0-current SNAP building machine has been found!) References: <199705111709.TAA06018@bitbox.follo.net> <199705111857.LAA05834@phaeton.artisoft.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > I was actually against using "voting"; I prefer forcing developers to > > > verify that compiles work and the resulting code does not trivially > > > fail prior to it being committed. That way the tree would always work; > > > the best you can get out of "voting" is "provided with high confidence > > > that it might work". > > > > Regression tests. We really should have this integrated into the > > build system. > > This is scary, in that it starts requiring developers to have "big iron". > > The POSIX tests (for example) take a while to run. I don't believe everybody should run the full regression tests each time. Full regression tests are expensive. However, if you e.g. do a modification in dump/restore, one can run the regression tests for dump/restore. You'd be much more certain of not having broken anything than you are today; a full 'make regress' could be done on need (whenever something seems to break, or if you believe there is a chance you've broken something else.) We've already got a limited form of this - 'make world' - but explicitly supporting regression would likely make it better. > > Anyway; being able to do a 'make regress' on the entire FreeBSD > > source tree and know all new code and a lot of old code got tested > > would be a _good_ feeling. > > Yes, very much so! I would limit its application, though; if the > CVS went "split tree with snapshot", then the process could be > automated, but it's probably too much overhead otherwise. 8-(. You're thinking of disk space requirements? I wouldn't worry too much. The regression suite take time to write, and I consider it unlikely that it will grow faster than price of disk space drop :-) For large test files, we could solve part of the problem by making them available through ftp, with an automated download system a la ports. However, as I said, I don't believe I've got The Solution to the problem; I just feel that a good solution to this would be a very nice addition to the build structure. Eivind. From owner-freebsd-current Sun May 11 14:52:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14381 for current-outgoing; Sun, 11 May 1997 14:52:43 -0700 (PDT) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14372 for ; Sun, 11 May 1997 14:52:41 -0700 (PDT) Received: from bsampley.vip.best.com (bsampley.vip.best.com [206.184.160.196]) by proxy3.ba.best.com (8.8.5/8.8.3) with SMTP id OAA04256 for ; Sun, 11 May 1997 14:50:39 -0700 (PDT) Date: Sun, 11 May 1997 14:48:52 -0700 (PDT) From: Burton Sampley To: current@FreeBSD.org Subject: CVSUP date = ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Can some1 running -current give me the date and time -current was last able to build without puking up errors. I tried CVSUPing Friday night, but it puked out an error message about something (I don't remember what it actually said) before I could even take my finger off the key. I think that's the fastest I have ever seen 'make world' die. I've tried previous dates that I thought I was able to build w/o errors, but every date I try keeps dying at some point before that magical little statement of 'Make World completed on at