From owner-freebsd-current Wed Sep 23 02:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19679 for freebsd-current-outgoing; Wed, 23 Sep 1998 02:41:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19618 for ; Wed, 23 Sep 1998 02:41:24 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with SMTP id FAA08610 for ; Wed, 23 Sep 1998 05:42:45 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 23 Sep 1998 05:42:45 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: Re: Current is Really Broken(tm) In-Reply-To: <2950.906542983@time.cdrom.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, 23 Sep 1998, Jordan K. Hubbard wrote: > > (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 ok, but DEVFS is mmm mmm gewd. i would like to test it, it's going off my work machine, can't loose another day rebuiling a box again, but i'll continue to play at home with it. the offer remains if anyone wants any more info about these crashes, i'll semi freeze the home machine as i don't see anything going into DEVFS lately though. as a side note i've been using NFSv3 as a client with 3.0 and it seems kinda stable, had a crash or two the other day vie reading mail over a NFS drive but after a cvsup the problems went away. mmm, LFS... is that back in the tree again? doesn't seem so. :( thanks for the feedback, Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message