From owner-freebsd-current Wed Sep 23 02:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17604 for freebsd-current-outgoing; Wed, 23 Sep 1998 02:29:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17591 for ; Wed, 23 Sep 1998 02:28:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA02954; Wed, 23 Sep 1998 02:29:43 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: Current is Really Broken(tm) In-reply-to: Your message of "Wed, 23 Sep 1998 03:39:20 CDT." Date: Wed, 23 Sep 1998 02:29:43 -0700 Message-ID: <2950.906542983@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (if you are involved with devfs, libdisk or CAM it's important that you > read this imo) If you want to test 3.0-current as it relates to 3.0-RELEASE, please do not use DEVFS. It will not be the default in 3.0-RELEASE nor is it even recommended for general use at this time. It's there the same way that things like LFS and NFSv3 are there - available for people to play with but not considered robust enough to use in anything but purely experimental setups. There's lots of experimental code in FreeBSD and we already know it blows up if you push on it, that's why it's experimental. :-) Far better to work with the set of options in GENERIC (or a subset thereof) and report problems you encounter there. Those would be true priority issues for 3.0-RELEASE. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message