From owner-freebsd-stable Thu Nov 25 1:16:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id 6DD6614CAD for ; Thu, 25 Nov 1999 01:16:46 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id KAA27765 for ; Thu, 25 Nov 1999 10:16:40 +0100 (MET) Date: Thu, 25 Nov 1999 10:16:36 +0100 (MET) From: Marcin Cieslak To: stable@FreeBSD.ORG Subject: Re: speaking of 3.4... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Forrest W. Christian wrote: > It would be really cool if FreeBSD would be able to do something like > this. In other words, I have to upgrade all my systems once a year and > apply "bug fixes" the rest of the year. Perhaps it's just a matter of taste. But I'd prefer having one or two development tracks (-stable,-current) and not diverting into many directions, like Cisco does. If you want to have ssh, you have to use 12.0(X)S release. But you this may not support all your hardware, supported in 12.0(7)X-whatever. In FreeBSD, you have simple choice - if you want to experiment with "Early Deployment" - go ahead with -current. If you'd rather stay with "General Deployment" - go with -stable. My personal opinion of a frequent cvsup'per is that one release a year is sufficient, but I understand the need for off-line or low-bandwitdth people on one side and the FreeBSD project on the other side to deliver CD-ROMs frequently. -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message