From owner-freebsd-stable Fri Apr 25 04:31:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA08975 for stable-outgoing; Fri, 25 Apr 1997 04:31:36 -0700 (PDT) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA08970 for ; Fri, 25 Apr 1997 04:31:31 -0700 (PDT) Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id NAA06963; Fri, 25 Apr 1997 13:29:02 +0200 (MET DST) Received: from oo7 ([192.0.0.136]) by dimaga.com (8.7.5/8.7.2) with SMTP id MAA14430; Fri, 25 Apr 1997 12:45:37 +0200 (MET DST) Message-Id: <3.0.32.19970425114753.01220eb0@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 25 Apr 1997 11:47:55 +0200 To: "Jordan K. Hubbard" From: Eivind Eklund Subject: Re: Is there a perceived need for a 2.1.8 release? Cc: "Jay D. Nelson" , Masaya Kinoshita , stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:21 PM 4/20/97 -0700, Jordan K. Hubbard wrote: >> Actually, I'm inclined to agree. If Walnut Creek doesn't wan't additional >> inventory, why not scrap the live filesystem on disk 2 and deliver 2.1.x >> instead? > >What if I put it on disk #2 of the SNAPshot CDs? They're cheaper to >subscribe to ($14.95 a copy) and now that I've got a double-CD set for >the SNAPs (a single CD was getting too squeezed) I can put a fair bit >on the 2nd CD. People wanting to keep running 2.1.x do so because they want extreme stability, and are already up and running on 2.1.x. This indicate vital machines, probably running in a production environment. Anybody willing to take down such a machine and actually replace the underlying system by doing a re-install should IMHO upgrade to 2.2. (Especially if Justin keep his SCSI-changes away until they have been tested really thouroughly in -current ;) However, for people that want to make an upgrade in place, by recompiling without taking down the server, the SNAP CDs are probably already what they want, without knowing it yet. The SNAPs include a full CVS-tree (or I'm just babbling), so an upgrade of the 2.1.x sources can be done by just typing cd /usr cvs -d /cdrom/cvsroot checkout src cd src make depend make make install cd sys/i386/conf config MYKERNEL cd ../../MYKERNEL make make install reboot If we add a script for doing this to the SNAP CDs, as well as a static version of cvs for those having really old distributions, people can easily use this to upgrade. Eivind.