From owner-freebsd-stable Tue Aug 13 10:22:58 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28558 for stable-outgoing; Tue, 13 Aug 1996 10:22:58 -0700 (PDT) Received: from netcomsv.netcom.com (uucp12.netcom.com [163.179.3.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA28552 for ; Tue, 13 Aug 1996 10:22:56 -0700 (PDT) Received: from asic11.UUCP by netcomsv.netcom.com with UUCP (8.6.12/SMI-4.1) id JAA28308; Tue, 13 Aug 1996 09:11:09 -0700 Received: from madmax.iecorp.com by asic11.iecorp.com (4.1/SMI-4.1) id AA17768; Tue, 13 Aug 96 09:01:00 PDT Received: by madmax.iecorp.com (4.1/SMI-4.1) id AA13680; Tue, 13 Aug 96 09:00:59 PDT From: bartleym@iecorp.com (Matt Bartley) Message-Id: <9608131600.AA13680@madmax.iecorp.com> Subject: usr.bin/kzip doesn't make clean To: stable@freebsd.org Date: Tue, 13 Aug 1996 09:00:59 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After I've done a make world, a make clean(dir) skips over usr.bin/kzip: Script started on Tue Aug 13 08:43:39 1996 bash# pwd /usr/src/usr.bin bash# ls kzip .depend kzip* kzip.o Makefile kzip.c bash# make -n | grep kzip for entry in apply ar at banner [...] cmp kzip look systat tail vmstat; do (if test -d /usr/src/usr.bin/${entry}.i386; then echo "===> ${entry}.i386"; edir=${entry}.i386; cd /usr/src/usr.bin/${edir}; else echo "===> $entry"; edir=${entry}; cd /usr/src/usr.bin/${edir}; fi; make all DIRPRFX=$edir/); done bash# make -n clean | grep kzip bash# make -n cleandir | grep kzip bash# cat /usr/src/.ctm_status src-2.1 152 bash# exit Script done on Tue Aug 13 08:44:45 1996 I'm running -stable, CTM level 0152. Last make world was last night. This glitch has been around for a long time. From owner-freebsd-stable Tue Aug 13 11:11:25 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA01031 for stable-outgoing; Tue, 13 Aug 1996 11:11:25 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA01026 for ; Tue, 13 Aug 1996 11:11:21 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id LAA16365; Tue, 13 Aug 1996 11:11:12 -0700 From: "Rodney W. Grimes" Message-Id: <199608131811.LAA16365@GndRsh.aac.dev.com> Subject: Re: usr.bin/kzip doesn't make clean To: bartleym@iecorp.com (Matt Bartley) Date: Tue, 13 Aug 1996 11:11:12 -0700 (PDT) Cc: stable@freebsd.org In-Reply-To: <9608131600.AA13680@madmax.iecorp.com> from Matt Bartley at "Aug 13, 96 09:00:59 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > After I've done a make world, a make clean(dir) skips over usr.bin/kzip: > > Script started on Tue Aug 13 08:43:39 1996 > bash# pwd > /usr/src/usr.bin > bash# ls kzip > .depend kzip* kzip.o > Makefile kzip.c > bash# make -n | grep kzip > for entry in apply ar at banner [...] cmp kzip look systat tail vmstat; do > (if test -d /usr/src/usr.bin/${entry}.i386; then echo "===> ${entry}.i386"; > edir=${entry}.i386; cd /usr/src/usr.bin/${edir}; else echo "===> $entry"; > edir=${entry}; cd /usr/src/usr.bin/${edir}; fi; make all DIRPRFX=$edir/); > done > bash# make -n clean | grep kzip > bash# make -n cleandir | grep kzip > bash# cat /usr/src/.ctm_status > src-2.1 152 > bash# exit > Script done on Tue Aug 13 08:44:45 1996 > > I'm running -stable, CTM level 0152. Last make world was last night. > This glitch has been around for a long time. The following patch will fix this, I'll commit it in a minute or two to -stable: Index: Makefile =================================================================== RCS file: /home/ncvs/src/usr.bin/Makefile,v retrieving revision 1.52.4.3 diff -u -r1.52.4.3 Makefile --- Makefile 1996/07/10 03:51:26 1.52.4.3 +++ Makefile 1996/08/13 18:09:59 @@ -29,9 +29,9 @@ # Cmp, look and tail all use mmap, so new-VM only. # F77 and pascal are VAX/Tahoe only. .if make(clean) || make(cleandir) -# XXX Should have `f77', `pascal' & `vmstat.sparc' judging by the +# XXX Should have `ld', `f77', `pascal' & `vmstat.sparc' judging by the # machine dependant lines, but we don't have them -SUBDIR+=cmp look systat tail vmstat +SUBDIR+=cmp kzip look systat tail vmstat .elif ${MACHINE} == "hp300" SUBDIR+=cmp ld look systat tail vmstat .elif ${MACHINE} == "i386" -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-stable Tue Aug 13 15:04:25 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15377 for stable-outgoing; Tue, 13 Aug 1996 15:04:25 -0700 (PDT) Received: from robin.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA15363; Tue, 13 Aug 1996 15:04:18 -0700 (PDT) Received: by robin.mcnc.org (8.6.9/MCNC/8-10-92) id SAA23541; Tue, 13 Aug 1996 18:03:54 -0400 for Date: Tue, 13 Aug 1996 18:03:54 -0400 From: "Frank E. Terhaar-Yonkers" Message-Id: <199608132203.SAA23541@robin.mcnc.org> To: freebsd-stable@FreeBSD.ORG Subject: busted stuff in ports Cc: stable@FreeBSD.ORG X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk tcsh: sh.glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment sh.glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment Or is this not supposed to work in release/stable? \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-stable Tue Aug 13 15:27:26 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA17057 for stable-outgoing; Tue, 13 Aug 1996 15:27:26 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA17052 for ; Tue, 13 Aug 1996 15:27:24 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id SAA27504; Tue, 13 Aug 1996 18:27:15 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: "Frank E. Terhaar-Yonkers" cc: freebsd-stable@FreeBSD.ORG From: "Gary Palmer" Subject: Re: busted stuff in ports In-reply-to: Your message of "Tue, 13 Aug 1996 18:03:54 EDT." <199608132203.SAA23541@robin.mcnc.org> Date: Tue, 13 Aug 1996 18:27:15 -0400 Message-ID: <27501.839975235@orion.webspan.net> Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Frank E. Terhaar-Yonkers" wrote in message ID <199608132203.SAA23541@robin.mcnc.org>: > tcsh: > sh.glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment > sh.glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment > glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment > glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment > Or is this not supposed to work in release/stable? You are grabbing the -current ports, which have features which will only work in -current. You shoul use the stuff from ports-2.1.5 on the ftp site. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-stable Wed Aug 14 04:41:00 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA24701 for stable-outgoing; Wed, 14 Aug 1996 04:41:00 -0700 (PDT) Received: from american.com (biscayne.american.com [204.253.96.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA24696 for ; Wed, 14 Aug 1996 04:40:58 -0700 (PDT) Received: from muir-woods.american.com (muir-woods.american.com [204.253.96.201]) by american.com (8.6.12/8.6.12) with ESMTP id HAA22072 for ; Wed, 14 Aug 1996 07:40:26 -0400 Received: (from brad@localhost) by muir-woods.american.com (8.7.5/8.6.12) id HAA01604; Wed, 14 Aug 1996 07:40:26 -0400 (EDT) Date: Wed, 14 Aug 1996 07:40:26 -0400 (EDT) Message-Id: <199608141140.HAA01604@muir-woods.american.com> From: Brad Parker To: freebsd-stable@freebsd.org Subject: kernel rot after a week or so Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm running 2.1.5-R on a P133 w/32mb, pci adaptec (2970?) controller. It's on the MBONE and is running mrouted-3.8. Every week or so it starts core dumping executables right and left. (rshd, login, ftpd, reboot... you name it). It did this yesterday - I looked at reboot.core and found that the "code" it was executing was all zeros - at least in the core file. I have seen this behavior, once, correlated with massive routing updates from the MBONE. (also note, I saw this behavior once and a while with 2.1.0-R) I have not subscribed to -stable before today (I didn't realize it existed - oops - I've been reading -current), so take pity if this is know. -brad From owner-freebsd-stable Wed Aug 14 05:26:49 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA26477 for stable-outgoing; Wed, 14 Aug 1996 05:26:49 -0700 (PDT) Received: from hawk.gnome.co.uk (gnome-gnome.cerbernet.co.uk [193.243.224.22]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA26472 for ; Wed, 14 Aug 1996 05:26:44 -0700 (PDT) Received: (from jacs@localhost) by hawk.gnome.co.uk (8.7.5/8.7.3) id NAA01616; Wed, 14 Aug 1996 13:26:40 +0100 (BST) Date: Wed, 14 Aug 1996 13:26:40 +0100 (BST) From: Chris Stenton Subject: policy statement. To: stable@FreeBSD.org Message-Id: Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I lost my mail connection during the discussion period on what was to happen to the stable source tree. Could someone e-mail me a copy of any policy statement on either the future of stable or its replacement. Thanks Chris From owner-freebsd-stable Thu Aug 15 04:50:56 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03867 for stable-outgoing; Thu, 15 Aug 1996 04:50:56 -0700 (PDT) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03861 for ; Thu, 15 Aug 1996 04:50:53 -0700 (PDT) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id GAA29574; Thu, 15 Aug 1996 06:50:07 -0500 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 15 Aug 1996 06:50:07 -0500 To: "Christoph P. Kukulies" From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: -stable (still worth supping?) Cc: freebsd-stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The subject says it. Is -stable stil alive or should one >abandon supping it? The demise of -stable is, IMHO, somewhat exaggerated. I expect that thare will continue to be occasional corrections that will be incorporated. If "stable" is more appropriate than "current" for your needs, I encourage you to continue to track it. However, you might wish to switch to CTM as your update mechanism. That way you will automatically get notification of any changes without placing a burden on the servers. Since it is a slowly changing target, it is not difficult to fake the conversion from sup to CTM. For those who cannot maintain the entire tree, it is also reasonable to manually bypass an occasional update to the portion of the tree which you are not maintaining. If nothing else, you can use the arrival of a CTM update as a trigger to use sup to update your tree. From owner-freebsd-stable Thu Aug 15 15:13:05 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28701 for stable-outgoing; Thu, 15 Aug 1996 15:13:05 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA28691 for ; Thu, 15 Aug 1996 15:12:59 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id PAA25865; Thu, 15 Aug 1996 15:12:06 -0700 (PDT) To: John Polstra cc: davidg@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, stable@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c In-reply-to: Your message of "Thu, 15 Aug 1996 15:02:23 PDT." <199608152202.PAA26974@austin.polstra.com> Date: Thu, 15 Aug 1996 15:12:06 -0700 Message-ID: <25863.840147126@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Are we still supposed to be maintaining RELENG_2_1_0? I thought that > ended when 2.1.5 came out. Just asking -- either way is fine with me. The concensus seems to be that we'll use it as a "support branch" up until the point where some variant of 2.2 is stable enough to upgrade to, then it truly will fade away. I don't expect to be doing any more releases along that branch, mind you, but there's no reason not to throw the folks who are still following it the occasional bone. Speaking of which, what do folks think about shutting down sup access to -stable and forcing a move towards CTM and CVSup for -stablefolk? It's *very* wasteful to have all those supfilesrv process's scanning the entire source tree for what are, at most, a couple of changes a week, not to mention the overhead of cvs updating the checked out version of -stable for sup on freefall. Jordan From owner-freebsd-stable Thu Aug 15 15:36:00 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA00844 for stable-outgoing; Thu, 15 Aug 1996 15:36:00 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA00835 for ; Thu, 15 Aug 1996 15:35:57 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA03483; Thu, 15 Aug 1996 16:35:38 -0600 (MDT) Date: Thu, 15 Aug 1996 16:35:38 -0600 (MDT) Message-Id: <199608152235.QAA03483@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: John Polstra , davidg@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, stable@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c In-Reply-To: <25863.840147126@time.cdrom.com> References: <199608152202.PAA26974@austin.polstra.com> <25863.840147126@time.cdrom.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Speaking of which, what do folks think about shutting down sup access > to -stable and forcing a move towards CTM and CVSup for -stablefolk? > > It's *very* wasteful to have all those supfilesrv process's scanning > the entire source tree for what are, at most, a couple of changes a > week, not to mention the overhead of cvs updating the checked out > version of -stable for sup on freefall. CVSup using checkout mode could easily be at least as compute bound as sup in checkout mode if it has to stat all the files everytime (which SUP with supscan running does only once), but John would be better suited to answer with the details. Nate From owner-freebsd-stable Thu Aug 15 16:15:44 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA03195 for stable-outgoing; Thu, 15 Aug 1996 16:15:44 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA03183 for ; Thu, 15 Aug 1996 16:15:41 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id QAA27581; Thu, 15 Aug 1996 16:15:16 -0700 (PDT) Message-Id: <199608152315.QAA27581@austin.polstra.com> To: Nate Williams cc: "Jordan K. Hubbard" , davidg@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, stable@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c In-reply-to: Your message of "Thu, 15 Aug 1996 16:35:38 MDT." <199608152235.QAA03483@rocky.mt.sri.com> Date: Thu, 15 Aug 1996 16:15:15 -0700 From: John Polstra Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Speaking of which, what do folks think about shutting down sup access > > to -stable and forcing a move towards CTM and CVSup for -stablefolk? > > > > It's *very* wasteful to have all those supfilesrv process's scanning > > the entire source tree for what are, at most, a couple of changes a > > week, not to mention the overhead of cvs updating the checked out > > version of -stable for sup on freefall. > > CVSup using checkout mode could easily be at least as compute bound as sup > in checkout mode if it has to stat all the files everytime (which SUP > with supscan running does only once), but John would be better suited to > answer with the details. I think Nate is right. You use supfilescan for the -stable release, don't you? If so, then supfilesrv should definitely be cheaper in terms of CPU cycles and disk accesses. About the overhead of cvs updating the checked out version, CVSup's checkout mode is actually much more efficient than that. (I've measured it.) But with cvs, you only do it once a day. With CVSup, the (lesser) work would be repeated for each client. So it would depend on the number of clients per day, among other things. The one reason I can think of for shutting down sup access to -stable would be if you want to free up all the disk space that's currently needed for the checked-out copy on the server. -- John From owner-freebsd-stable Thu Aug 15 19:59:40 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24435 for stable-outgoing; Thu, 15 Aug 1996 19:59:40 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA24424 for ; Thu, 15 Aug 1996 19:59:34 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id TAA26521; Thu, 15 Aug 1996 19:58:41 -0700 (PDT) To: John Polstra cc: Nate Williams , davidg@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, stable@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c In-reply-to: Your message of "Thu, 15 Aug 1996 16:15:15 PDT." <199608152315.QAA27581@austin.polstra.com> Date: Thu, 15 Aug 1996 19:58:41 -0700 Message-ID: <26519.840164321@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The one reason I can think of for shutting down sup access to -stable > would be if you want to free up all the disk space that's currently > needed for the checked-out copy on the server. That would be nice, yes. Perhaps then we should simply say "CTM only" since CTM is a good way of distributing bits which don't change frequently. Jordan From owner-freebsd-stable Thu Aug 15 20:06:53 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA24986 for stable-outgoing; Thu, 15 Aug 1996 20:06:53 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA24865 for ; Thu, 15 Aug 1996 20:04:54 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA17001; Fri, 16 Aug 1996 12:52:23 +0930 From: Michael Smith Message-Id: <199608160322.MAA17001@genesis.atrad.adelaide.edu.au> Subject: Re: cvs commit: src/sys/kern vfs_subr.c To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 16 Aug 1996 12:52:22 +0930 (CST) Cc: jdp@polstra.com, nate@mt.sri.com, davidg@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, stable@freebsd.org In-Reply-To: <26519.840164321@time.cdrom.com> from "Jordan K. Hubbard" at Aug 15, 96 07:58:41 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > That would be nice, yes. Perhaps then we should simply say "CTM only" > since CTM is a good way of distributing bits which don't change > frequently. When this is finalised and announced formally (it _will_ be announced formally, right? 8), could the announcement please contain a reference directing those of us who are sup-only shops to a set of destructions for taking a supped tree and converting it to CTM? Ta. > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-stable Thu Aug 15 20:12:34 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA25514 for stable-outgoing; Thu, 15 Aug 1996 20:12:34 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA25496 for ; Thu, 15 Aug 1996 20:12:30 -0700 (PDT) Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.103.21]) by po2.glue.umd.edu (8.7.5/8.7.3) with ESMTP id XAA06540; Thu, 15 Aug 1996 23:12:28 -0400 (EDT) Received: from localhost (chuckr@localhost) by gilligan.eng.umd.edu (8.7.5/8.7.3) with SMTP id XAA14481; Thu, 15 Aug 1996 23:12:27 -0400 (EDT) X-Authentication-Warning: gilligan.eng.umd.edu: chuckr owned process doing -bs Date: Thu, 15 Aug 1996 23:12:27 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@gilligan.eng.umd.edu To: "Jordan K. Hubbard" cc: John Polstra , Nate Williams , davidg@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, stable@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c In-Reply-To: <26519.840164321@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 15 Aug 1996, Jordan K. Hubbard wrote: > > The one reason I can think of for shutting down sup access to -stable > > would be if you want to free up all the disk space that's currently > > needed for the checked-out copy on the server. > > That would be nice, yes. Perhaps then we should simply say "CTM only" > since CTM is a good way of distributing bits which don't change > frequently. Am I confused? If you would distribute it via CTM, then you'd still need that checked out copy of -stable, for CTM to diff against, right? Of course, it would mean less ftp and machine time load ... Jordan, I see your port of rsync builds fine, are you going to commit it? Do you have any plans to test it? Would you mind if I did? > > Jordan > ----------------------------+----------------------------------------------- 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 n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-stable Fri Aug 16 11:42:01 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA06235 for stable-outgoing; Fri, 16 Aug 1996 11:42:01 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [206.117.70.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA06229 for ; Fri, 16 Aug 1996 11:41:57 -0700 (PDT) Received: from [127.0.0.1] ([127.0.0.1]) by kachina.jetcafe.org (8.7.5/8.7.3) with SMTP id LAA27636; Fri, 16 Aug 1996 11:41:41 -0700 (PDT) Message-Id: <199608161841.LAA27636@kachina.jetcafe.org> X-Authentication-Warning: kachina.jetcafe.org: Host [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" Cc: stable@freebsd.org Subject: Sup-ing stable Date: Fri, 16 Aug 1996 11:41:36 -0700 From: Dave Hayes Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Pardon me if I'm clueless. However, you said before that sup-ing the stable tree would upgrade one to 2.1.5-RELEASE. If that's true, why is uname -a giving me 2.1-RELEASE? I've sup'd the entire stable tree as of last night even. ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet "When you are in it up to your ears, keep your mouth shut." From owner-freebsd-stable Fri Aug 16 12:13:20 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08644 for stable-outgoing; Fri, 16 Aug 1996 12:13:20 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA08635 for ; Fri, 16 Aug 1996 12:13:16 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA01077; Fri, 16 Aug 1996 12:12:50 -0700 From: "Rodney W. Grimes" Message-Id: <199608161912.MAA01077@GndRsh.aac.dev.com> Subject: Re: Sup-ing stable To: dave@kachina.jetcafe.org (Dave Hayes) Date: Fri, 16 Aug 1996 12:12:49 -0700 (PDT) Cc: jkh@time.cdrom.com, stable@freebsd.org In-Reply-To: <199608161841.LAA27636@kachina.jetcafe.org> from Dave Hayes at "Aug 16, 96 11:41:36 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Pardon me if I'm clueless. However, you said before that sup-ing the > stable tree would upgrade one to 2.1.5-RELEASE. If that's true, why is > uname -a giving me 2.1-RELEASE? I've sup'd the entire stable tree as > of last night even. You sure it doesn't say something like: FreeBSD SkyRsh.aac.dev.com 2.1-STABLE FreeBSD 2.1-STABLE #0: Sun Aug 11 12:46:13 PDT 1996 root@SkyRsh.aac.dev.com:/usr/src/sys/compile/SKYRSH i386 Note, 2.1-STABLE, not 2.1-RELEASE. Also, Jordan, FYI, 3 or 4 of my clients have also sent me notices saying ``I though you said these would be loaded with 2.1.5 + fixes, why does it say 2.1''. I think there is enough confusion out there that the strings should be changed to this: TYPE="FreeBSD" REVISION="2.1.5" BRANCH="STABLE" It's still the ``STABLE'' branch, but PAST the 2.1.5 release tag... ``STABLE'' == the cvs RELENG_2_1_0 tag, so I don't want to here the cvs tag confustion again please... Just me $0.10 worth... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-stable Fri Aug 16 12:15:17 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08774 for stable-outgoing; Fri, 16 Aug 1996 12:15:17 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA08769 for ; Fri, 16 Aug 1996 12:15:15 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id MAA02092; Fri, 16 Aug 1996 12:15:06 -0700 (PDT) To: Dave Hayes cc: stable@freebsd.org Subject: Re: Sup-ing stable In-reply-to: Your message of "Fri, 16 Aug 1996 11:41:36 PDT." <199608161841.LAA27636@kachina.jetcafe.org> Date: Fri, 16 Aug 1996 12:15:06 -0700 Message-ID: <2090.840222906@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Pardon me if I'm clueless. However, you said before that sup-ing the > stable tree would upgrade one to 2.1.5-RELEASE. If that's true, why is Well, you have to *build* it too, just supping alone won't upgrade anything but your source tree. :-) Do a make world, build and install the kernel, you'll be effectively running 2.1.5 (with a few post-release bug fixes). Jordan > uname -a giving me 2.1-RELEASE? I've sup'd the entire stable tree as > of last night even. > ------ > Dave Hayes - Altadena CA, USA - dave@jetcafe.org > Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet > > "When you are in it up to your ears, keep your mouth shut." > From owner-freebsd-stable Fri Aug 16 12:20:11 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09167 for stable-outgoing; Fri, 16 Aug 1996 12:20:11 -0700 (PDT) Received: from yoda.fdt.net (root@yoda.fdt.net [205.229.48.17]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA09161 for ; Fri, 16 Aug 1996 12:20:08 -0700 (PDT) Received: from Kryten.nina.org (dyn051-gnv.51.fdt.net [205.229.51.52]) by yoda.fdt.net (8.6.12/8.6.12) with SMTP id PAA01454; Fri, 16 Aug 1996 15:19:50 -0400 Date: Fri, 16 Aug 1996 15:19:25 -0400 (EDT) From: Frank Seltzer X-Sender: frankd@Kryten.nina.org To: Dave Hayes cc: "Jordan K. Hubbard" , stable@freebsd.org Subject: Re: Sup-ing stable In-Reply-To: <199608161841.LAA27636@kachina.jetcafe.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 16 Aug 1996, Dave Hayes wrote: > Pardon me if I'm clueless. However, you said before that sup-ing the > stable tree would upgrade one to 2.1.5-RELEASE. If that's true, why is > uname -a giving me 2.1-RELEASE? I've sup'd the entire stable tree as > of last night even. You are not the only one to see this. I supped -stable about 3-4 weeks ago on another machine and got 2.1.5-RELEASE. I supped on this machine 2 days ago and get 2.1.0-STABLE. > ------ > Dave Hayes - Altadena CA, USA - dave@jetcafe.org > Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet > > "When you are in it up to your ears, keep your mouth shut." > Frank -- Only in America can a homeless veteran sleep in a cardboard box while a draft dodger sleeps in the White House - anonymous From owner-freebsd-stable Fri Aug 16 12:59:10 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11420 for stable-outgoing; Fri, 16 Aug 1996 12:59:10 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [206.117.70.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA11386 for ; Fri, 16 Aug 1996 12:58:55 -0700 (PDT) Received: from [127.0.0.1] ([127.0.0.1]) by kachina.jetcafe.org (8.7.5/8.7.3) with SMTP id MAA28130; Fri, 16 Aug 1996 12:58:41 -0700 (PDT) Message-Id: <199608161958.MAA28130@kachina.jetcafe.org> X-Authentication-Warning: kachina.jetcafe.org: Host [127.0.0.1] didn't use HELO protocol To: "Rodney W. Grimes" Cc: jkh@time.cdrom.com, stable@freebsd.org Subject: Re: Sup-ing stable Date: Fri, 16 Aug 1996 12:58:40 -0700 From: Dave Hayes Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > You sure it doesn't say something like: FreeBSD SkyRsh.aac.dev.com > 2.1-STABLE FreeBSD 2.1-STABLE #0: Sun Aug 11 12:46:13 PDT 1996 > root@SkyRsh.aac.dev.com:/usr/src/sys/compile/SKYRSH i386 Sure. But here's two machines I have loaded this on to: FreeBSD avalon.jetcafe.org 2.1-STABLE FreeBSD 2.1-STABLE #0: Sun Aug 11 23:12:32 1996 dave@avalon.jetcafe.org:/usr/src/sys/compile/AVALON i386 FreeBSD elxr.jetcafe.org 2.1.5-RELEASE FreeBSD 2.1.5-RELEASE #0: Mon Jul 29 05:01:05 PDT 1996 dave@elxr.jetcafe.org:/usr/src/sys/compile/ELXR i386 Note the time differences, those are approximately when I sup'd the distributions. > Note, 2.1-STABLE, not 2.1-RELEASE. I know. However, I agree with this 100%: > I think there is enough confusion out there that the strings should be > changed to this: > TYPE="FreeBSD" > REVISION="2.1.5" > BRANCH="STABLE" Also... > It's still the ``STABLE'' branch, but PAST the 2.1.5 release tag... > ``STABLE'' == the cvs RELENG_2_1_0 tag, so I don't want to here the > cvs tag confustion again please... Are people still patching this tree? I thought you guys wanted to freeze this code. ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet The practice of study only too often makes people mere repeaters and producers of cliches and sayings. Such study has been all but wasted. The product has taken the form in which we find it because it is an unsuitable graft upon an unprepared basis. From owner-freebsd-stable Fri Aug 16 13:40:43 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15485 for stable-outgoing; Fri, 16 Aug 1996 13:40:43 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA15466 for ; Fri, 16 Aug 1996 13:40:36 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id NAA01407; Fri, 16 Aug 1996 13:40:05 -0700 From: "Rodney W. Grimes" Message-Id: <199608162040.NAA01407@GndRsh.aac.dev.com> Subject: Re: Sup-ing stable To: dave@kachina.jetcafe.org (Dave Hayes) Date: Fri, 16 Aug 1996 13:40:05 -0700 (PDT) Cc: jkh@time.cdrom.com, stable@freebsd.org In-Reply-To: <199608161958.MAA28130@kachina.jetcafe.org> from Dave Hayes at "Aug 16, 96 12:58:40 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > You sure it doesn't say something like: FreeBSD SkyRsh.aac.dev.com > > 2.1-STABLE FreeBSD 2.1-STABLE #0: Sun Aug 11 12:46:13 PDT 1996 > > root@SkyRsh.aac.dev.com:/usr/src/sys/compile/SKYRSH i386 > > Sure. But here's two machines I have loaded this on to: Loading it does not build you a kernel and install it... > > FreeBSD avalon.jetcafe.org 2.1-STABLE FreeBSD 2.1-STABLE #0: Sun Aug > 11 23:12:32 1996 dave@avalon.jetcafe.org:/usr/src/sys/compile/AVALON > i386 > > FreeBSD elxr.jetcafe.org 2.1.5-RELEASE FreeBSD 2.1.5-RELEASE #0: Mon > Jul 29 05:01:05 PDT 1996 dave@elxr.jetcafe.org:/usr/src/sys/compile/ELXR i386 > > Note the time differences, those are approximately when I sup'd the > distributions. ---------------------------- revision 1.16.4.6 date: 1996/08/02 01:11:10; author: peter; state: Exp; lines: +3 -3 Now that 2.1.5-RELEASE is done, and the -stable code has had two commits, it's time to stop calling it -RELEASE anymore. Revert last change and set the "name" back to 2.1-STABLE again. Reviewed by: jkh (about a week ago) ---------------------------- revision 1.16.4.5 date: 1996/07/13 14:29:13; author: peter; state: Exp; lines: +3 -3 Bump REVISION to "2.1.5" and BRANCH to "RELEASE" in preperation for 2.1.5 tree tagging. Reviewed by: davidg ---------------------------- 07/29 falls into the 2.1.5-RELEASE section of these 2 commits... > > Note, 2.1-STABLE, not 2.1-RELEASE. > > I know. However, I agree with this 100%: > > > I think there is enough confusion out there that the strings should be > > changed to this: > > TYPE="FreeBSD" > > REVISION="2.1.5" > > BRANCH="STABLE" > > Also... > > > It's still the ``STABLE'' branch, but PAST the 2.1.5 release tag... > > ``STABLE'' == the cvs RELENG_2_1_0 tag, so I don't want to here the > > cvs tag confustion again please... > > Are people still patching this tree? I thought you guys wanted to > freeze this code. Yes, I am still patching this tree, and if the FreeBSD project kills the tree I will be setting up my own area to maintain this realease. With several 100 customers dependant upon being able to run this and have bugs fixed it would be too important to me to have support for it totally dropped. If I have to go to a ``patchkit'' to do it, I will. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-stable Fri Aug 16 13:42:31 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15647 for stable-outgoing; Fri, 16 Aug 1996 13:42:31 -0700 (PDT) Received: from mailgw.acs.utah.edu (mailgw.acs.utah.edu [128.110.165.95]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA15635 for ; Fri, 16 Aug 1996 13:42:28 -0700 (PDT) Received: from acs.utah.edu by mailgw.acs.utah.edu; Fri, 16 Aug 96 14:46 MST Received: from EDU-UTAH-ADP-CASE/SpoolDir by case.acs.utah.edu (Mercury 1.13); Fri, 16 Aug 96 14:42:20 MDT Received: from SpoolDir by EDU-UTAH-ADP-CASE (Mercury 1.13); Fri, 16 Aug 96 14:42:08 MDT From: "Lloyd M Caldwell" Content-Type: text Organization: Univ. Of Utah, Admin. Comp. Serv. To: stable@freebsd.org Date: Fri, 16 Aug 1996 14:42:05 MDT Subject: make world problems Priority: normal X-mailer: Pegasus Mail/Windows (v1.22) Message-ID: <19C38145A0B@case.acs.utah.edu> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I'm a new sup-er of stable freebsd. I sup'ed the stuff into a different tree than the /usr tree, /src/stable. I set DESTDIR to /src/stable.build and did a 'make world'. So far the build hasn't been able to complete. ~/gnu/lib/libgpm/Makefile ~/share/examples/Makefile ~/lib/libutil/Makefile These makefiles needed the ${INSTALL} -C changed to ${INSTALL} -c. i.e. upper case 'C' to lower case 'c'. Now I get: make: don't know how to make /src/stable.build/usr/lib/c++rt0.o. Stop Also a bunch of stuff has been placed on my /usr filesystem under /usr/obj/src/stable, which is a problem as that file system is not got much free space. Where should I be looking for instructions, problems and workarounds on the stable build process? Thanks Lloyd M Caldwell 53131 lcaldwell@acs.utah.edu A vote: please keep sup, we use sup for lots of things here. From owner-freebsd-stable Fri Aug 16 14:09:33 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18258 for stable-outgoing; Fri, 16 Aug 1996 14:09:33 -0700 (PDT) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA18245 for ; Fri, 16 Aug 1996 14:09:29 -0700 (PDT) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id QAA02823; Fri, 16 Aug 1996 16:09:11 -0500 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 16 Aug 1996 16:09:11 -0500 To: "Rodney W. Grimes" From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Sup-ing stable Cc: stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney Grimes writes: >I think there is enough confusion out there that the strings should be >changed to this: >TYPE="FreeBSD" >REVISION="2.1.5" >BRANCH="STABLE" Well, that is your opinion. My opinion is slightly different. Here is my interpretation of the way things should be... "Stable", and for that matter "current", do not really designate development branches. I feel that they are simply aliases that reflect the state of development. Using both "2.1.5" and "STABLE" is redundant. I think that "2.1" is the proper name of the branch. We are awaiting the CD for revision "RELEASE-5" Those who have gotten today's update are at revision "CTM-154" However, to help avoid confusion among the uninitiated, perhaps we should call today's version "FreeBSD 2.1.5-154","FreeBSD 2.1.5p154", or something similar. From owner-freebsd-stable Fri Aug 16 14:24:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA19307 for stable-outgoing; Fri, 16 Aug 1996 14:24:28 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA19300 for ; Fri, 16 Aug 1996 14:24:21 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA01548; Fri, 16 Aug 1996 14:22:34 -0700 From: "Rodney W. Grimes" Message-Id: <199608162122.OAA01548@GndRsh.aac.dev.com> Subject: Re: Sup-ing stable To: rkw@dataplex.net (Richard Wackerbarth) Date: Fri, 16 Aug 1996 14:22:34 -0700 (PDT) Cc: stable@freebsd.org In-Reply-To: from Richard Wackerbarth at "Aug 16, 96 04:09:11 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Rodney Grimes writes: > > >I think there is enough confusion out there that the strings should be > >changed to this: > >TYPE="FreeBSD" > >REVISION="2.1.5" > >BRANCH="STABLE" > > Well, that is your opinion. My opinion is slightly different. > Here is my interpretation of the way things should be... > > > "Stable", and for that matter "current", do not really designate > development branches. I feel that they are simply aliases that reflect the > state of development. Using both "2.1.5" and "STABLE" is redundant. Erhh.. try again ``Stable'' has a direct corresponding CVS tag, that tag happens to be a branch tag (cvs tag -b) and as of almost a year ago has the value ``RELENG_2_1_0''. ``Current'' has a direct correspoding CVS tag, all be it invisible, known as ``HEAD''. ``2.1.5'' is a POINT on a BRANCH, it has a corresponding tag value of ``RELENG_2_1_5''. You can _NOT_ sup ``2.1.5-RELEASE'' except for the window of dates I pointed out in the message about the commits to newvers.sh. > I think that "2.1" is the proper name of the branch. Not really, that is a version on a branch (namely the cvs tag ``RELENG_2_1_0_RELEASE'', which has been superceded by ``RELENG_2_1_5_RELEASE). NEITHER of which are ``BRANCHES'' per se. > We are awaiting the CD for revision "RELEASE-5" > Those who have gotten today's update are at revision "CTM-154" > > However, to help avoid confusion among the uninitiated, perhaps we should > call today's version "FreeBSD 2.1.5-154","FreeBSD 2.1.5p154", or something > similar. Been discussed, find an ``elegant'' way to do it and it might be done... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-stable Fri Aug 16 14:31:58 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA19693 for stable-outgoing; Fri, 16 Aug 1996 14:31:58 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA19686 for ; Fri, 16 Aug 1996 14:31:51 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.7.5/8.7.3) id OAA08745; Fri, 16 Aug 1996 14:31:19 -0700 (PDT) From: "Steven G. Kargl" Message-Id: <199608162131.OAA08745@troutmask.apl.washington.edu> Subject: Re: Sup-ing stable To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Fri, 16 Aug 1996 14:31:19 -0700 (PDT) Cc: dave@kachina.jetcafe.org, jkh@time.cdrom.com, stable@freebsd.org In-Reply-To: <199608162040.NAA01407@GndRsh.aac.dev.com> from "Rodney W. Grimes" at "Aug 16, 96 01:40:05 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I 've lost track of the attributions. >> >>> It's still the ``STABLE'' branch, but PAST the 2.1.5 release tag... >>> ``STABLE'' == the cvs RELENG_2_1_0 tag, so I don't want to here the >>> cvs tag confustion again please... >> >> Are people still patching this tree? I thought you guys wanted to >> freeze this code. > > Yes, I am still patching this tree, and if the FreeBSD project kills the > tree I will be setting up my own area to maintain this realease. With > several 100 customers dependant upon being able to run this and have > bugs fixed it would be too important to me to have support for it totally > dropped. If I have to go to a ``patchkit'' to do it, I will. > FreeBSD Org does send patches to CERT for security related problems. Supping the -stable branch to acquire these patches is preferable over a possible manual patching from the CERT announcement. The -stable branch should be a maintenance branch. No new features. No new drivers. Just fixes. $0.02 -- Steve From owner-freebsd-stable Fri Aug 16 14:45:59 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20707 for stable-outgoing; Fri, 16 Aug 1996 14:45:59 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA20699 for ; Fri, 16 Aug 1996 14:45:51 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA08447; Fri, 16 Aug 1996 15:45:01 -0600 (MDT) Date: Fri, 16 Aug 1996 15:45:01 -0600 (MDT) Message-Id: <199608162145.PAA08447@rocky.mt.sri.com> From: Nate Williams To: "Rodney W. Grimes" Cc: dave@kachina.jetcafe.org (Dave Hayes), jkh@time.cdrom.com, stable@freebsd.org Subject: Re: Sup-ing stable In-Reply-To: <199608162040.NAA01407@GndRsh.aac.dev.com> References: <199608161958.MAA28130@kachina.jetcafe.org> <199608162040.NAA01407@GndRsh.aac.dev.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I think there is enough confusion out there that the strings should be > > > changed to this: > > > TYPE="FreeBSD" > > > REVISION="2.1.5" > > > BRANCH="STABLE" I just modified it to be as above, to imply that the -stable branch is now post 2.1.5R. Nate From owner-freebsd-stable Fri Aug 16 14:59:25 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21944 for stable-outgoing; Fri, 16 Aug 1996 14:59:25 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA21935 for ; Fri, 16 Aug 1996 14:59:17 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA08561; Fri, 16 Aug 1996 15:59:06 -0600 (MDT) Date: Fri, 16 Aug 1996 15:59:06 -0600 (MDT) Message-Id: <199608162159.PAA08561@rocky.mt.sri.com> From: Nate Williams To: rkw@dataplex.net (Richard Wackerbarth) Cc: "Rodney W. Grimes" , stable@freebsd.org Subject: Re: Sup-ing stable In-Reply-To: References: Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I think there is enough confusion out there that the strings should be > >changed to this: > >TYPE="FreeBSD" > >REVISION="2.1.5" > >BRANCH="STABLE" > > Well, that is your opinion. My opinion is slightly different. > Here is my interpretation of the way things should be... > > "Stable", and for that matter "current", do not really designate > development branches. But, they *do* designate development branches. >I feel that they are simply aliases that reflect the > state of development. Using both "2.1.5" and "STABLE" is redundant. If so, then why do we have '2.1-STABLE'? You just said that 2.1.5 and STABLE are the same. > I think that "2.1" is the proper name of the branch. It is the name of the branch, but the confusion lies in the users, not the developers. Recent usage has been that 2.1-STABLE is 2.1 + stable patches. Keeping the -stable branch named to '2.1-STABLE' is true, although somewhat misleading since it really is 2.1.5 + stable patches'. In any case, I changed the strings to avoid the confusion which I felt occurred and agree with, or else we wouldn't be having this discussion. > However, to help avoid confusion among the uninitiated, perhaps we should > call today's version "FreeBSD 2.1.5-154","FreeBSD 2.1.5p154", or something > similar. This implies the users use CTM, which is definitely not the case for many users. CTM is only one of the 4 (5?) different distribution methods used. 1) CD-ROM (I'll lump all users of 'Releases' in the same manner). There is very little room for confusion here, except when a release is re-rolled using the same name. :) 2) Remote CVS - The release is designated by the date of the most recent update, so one can return to it using a particular date if necessary (although this doesn't work on branches). The state of the system is determined by the particular revisions on the files. 3) CTM - Richard' favorite, which uses numbers to designate a particular revision. 4) SUP - No way of getting back to where you were before or knowing where you are except by knowing what data you last did a sup, but generally this isn't a big deal. 5) CVSup - This is a combination of Remove CVS and SUP, with the ability to checkout via date (on branches even), or if you get the actual CVS tree you can determine where you are via dates as well. Nate From owner-freebsd-stable Fri Aug 16 15:15:15 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23747 for stable-outgoing; Fri, 16 Aug 1996 15:15:15 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA23717 for ; Fri, 16 Aug 1996 15:15:00 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id BAA01489; Sat, 17 Aug 1996 01:17:46 +0300 Date: Sat, 17 Aug 1996 01:17:45 +0300 (EET DST) From: Narvi To: "Steven G. Kargl" cc: "Rodney W. Grimes" , dave@kachina.jetcafe.org, jkh@time.cdrom.com, stable@freeBSD.ORG Subject: Re: Sup-ing stable In-Reply-To: <199608162131.OAA08745@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 16 Aug 1996, Steven G. Kargl wrote: > I 've lost track of the attributions. > > >> > >>> It's still the ``STABLE'' branch, but PAST the 2.1.5 release tag... > >>> ``STABLE'' == the cvs RELENG_2_1_0 tag, so I don't want to here the > >>> cvs tag confustion again please... > >> > >> Are people still patching this tree? I thought you guys wanted to > >> freeze this code. > > > > Yes, I am still patching this tree, and if the FreeBSD project kills the > > tree I will be setting up my own area to maintain this realease. With > > several 100 customers dependant upon being able to run this and have > > bugs fixed it would be too important to me to have support for it totally > > dropped. If I have to go to a ``patchkit'' to do it, I will. > > > > FreeBSD Org does send patches to CERT for security related problems. > Supping the -stable branch to acquire these patches is preferable over > a possible manual patching from the CERT announcement. > > The -stable branch should be a maintenance branch. No new features. > No new drivers. Just fixes. But it is as that on the moment! Sander > > $0.02 > > -- > Steve > From owner-freebsd-stable Sat Aug 17 03:18:55 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA13094 for stable-outgoing; Sat, 17 Aug 1996 03:18:55 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA13073 for ; Sat, 17 Aug 1996 03:18:48 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id NAA05494; Sat, 17 Aug 1996 13:22:10 +0300 Date: Sat, 17 Aug 1996 13:22:09 +0300 (EET DST) From: Narvi To: Dave Hayes cc: "Rodney W. Grimes" , jkh@time.cdrom.com, stable@FreeBSD.org Subject: Re: Sup-ing stable In-Reply-To: <199608161958.MAA28130@kachina.jetcafe.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 16 Aug 1996, Dave Hayes wrote: > > You sure it doesn't say something like: FreeBSD SkyRsh.aac.dev.com > > 2.1-STABLE FreeBSD 2.1-STABLE #0: Sun Aug 11 12:46:13 PDT 1996 > > root@SkyRsh.aac.dev.com:/usr/src/sys/compile/SKYRSH i386 > > Sure. But here's two machines I have loaded this on to: > > FreeBSD avalon.jetcafe.org 2.1-STABLE FreeBSD 2.1-STABLE #0: Sun Aug > 11 23:12:32 1996 dave@avalon.jetcafe.org:/usr/src/sys/compile/AVALON > i386 > > FreeBSD elxr.jetcafe.org 2.1.5-RELEASE FreeBSD 2.1.5-RELEASE #0: Mon > Jul 29 05:01:05 PDT 1996 dave@elxr.jetcafe.org:/usr/src/sys/compile/ELXR i386 > > Note the time differences, those are approximately when I sup'd the > distributions. > > > Note, 2.1-STABLE, not 2.1-RELEASE. > > I know. However, I agree with this 100%: > > > I think there is enough confusion out there that the strings should be > > changed to this: > > TYPE="FreeBSD" > > REVISION="2.1.5" > > BRANCH="STABLE" > > Also... > > > It's still the ``STABLE'' branch, but PAST the 2.1.5 release tag... > > ``STABLE'' == the cvs RELENG_2_1_0 tag, so I don't want to here the > > cvs tag confustion again please... > > Are people still patching this tree? I thought you guys wanted to > freeze this code. Freeze? You mean the code freeze before the release? It is long over. But the -stable brance is no more developed - *only* bug fixes go to it. Sander > ------ > Dave Hayes - Altadena CA, USA - dave@jetcafe.org > Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet > > The practice of study only too often makes people mere repeaters and > producers of cliches and sayings. Such study has been all but wasted. > The product has taken the form in which we find it because it is an > unsuitable graft upon an unprepared basis. > > >