From owner-freebsd-current Wed Dec 9 17:51:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02848 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:51:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02828 for ; Wed, 9 Dec 1998 17:50:57 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id RAA08856; Wed, 9 Dec 1998 17:49:54 -0800 (PST) (envelope-from marcs@znep.com) Date: Wed, 9 Dec 1998 17:49:54 -0800 (PST) From: Marc Slemko To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: Current ready for prime time web server ? In-Reply-To: <199812092149.NAA51668@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Dec 1998, Amancio Hasty wrote: > May ask why do you think that 3.0 is not ready for prime time? A few things. First, the big statement saying: This is our first release of 3.0-CURRENT and is aimed primarily at early adopters and developers. Second, the massive number of changes that were rushed into the tree soon before 3.0 came out. Things take time to settle. There are no specifics really. Well, some of the things new in 3.0 still need more work but that alone shouldn't discourage people who only need to use things that already were in 2.x. Third, I'm not aware of the dying daemons thing being fixed. I don't like it when programs randomly start dying due to vm wackyness or whatever it is. While the failure mode that appears to be typical may not normally happen on many servers, I wouldn't want to put my faith in that. My 3.0 workstation has seen this, and it has prevented me from accessing it remotely. Good thing it isn't a server. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message