From owner-freebsd-current Sat Mar 21 13:52:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08056 for freebsd-current-outgoing; Sat, 21 Mar 1998 13:52:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA08051 for ; Sat, 21 Mar 1998 13:52:56 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 781 invoked from network); 21 Mar 1998 21:52:20 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 21 Mar 1998 21:52:20 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id NAA00417 for freebsd-current@freebsd.org; Sat, 21 Mar 1998 13:52:43 -0800 (PST) (envelope-from scottm) Date: Sat, 21 Mar 1998 13:52:43 -0800 (PST) From: Scott Michel Message-Id: <199803212152.NAA00417@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: John's latest round of changes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been running a CVSup'd kernel from yesterday, relatively trouble free. I'd concur with John: it seems OK for the moment, but be prepared to back out at a moment's notice. Do not use soft updates. That's still pretty unstable (although I've yet to get a decent panic and traceback -- machine spontaneously reboots under load.) Also, I did manage to get through a 'make world' w/minimal problems last night, and my disks (I'm a WD wanker too!) pass fsck checks. I'm going to try to track down the problems I've encountered, but since the kernel doesn't panic, these are notoriously NP hard to locate. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message