From owner-freebsd-current Fri Jan 21 7: 9:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from argon.blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 3903C14F3E for ; Fri, 21 Jan 2000 07:09:16 -0800 (PST) (envelope-from will@blackdawn.com) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 69D071984; Fri, 21 Jan 2000 10:09:13 -0500 (EST) Date: Fri, 21 Jan 2000 10:09:13 -0500 From: Will Andrews To: "Matt M." Cc: current@FreeBSD.ORG Subject: Re: cvsup 3.4-release to -current Message-ID: <20000121100913.C436@argon.blackdawn.com> References: <3887ECC9.7A2625F5@boda.virtualave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3887ECC9.7A2625F5@boda.virtualave.net>; from matt@boda.virtualave.net on Thu, Jan 20, 2000 at 09:21:13PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 20, 2000 at 09:21:13PM -0800, Matt M. wrote: > Just wondering what potential problems I am facing by going from > 3.4-release to -current. I was told on irc that my chances may not be > well. You should read /usr/src/UPDATING (for -CURRENT). I won't say you shouldn't use it since 4.0-RELEASE is probably going out within a month, and bugs need to be worked out. However, I wouldn't upgrade if I was using that particular machine for production purposes. My -CURRENT box can crash to hell for all I care. My -STABLE will stay -STABLE since it needs to be depended on. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message