From owner-freebsd-current  Tue Apr  7 22:27:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA20756
          for freebsd-current-outgoing; Tue, 7 Apr 1998 22:27:06 -0700 (PDT)
          (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 WAA20750
          for <freebsd-current@freebsd.org>; Tue, 7 Apr 1998 22:27:05 -0700 (PDT)
          (envelope-from scottm@mordred.cs.ucla.edu)
Received: (qmail 9839 invoked from network); 8 Apr 1998 05:26:13 -0000
Received: from mordred.cs.ucla.edu (131.179.48.34)
  by taliesin.cs.ucla.edu with SMTP; 8 Apr 1998 05:26:13 -0000
Received: (from scottm@localhost)
	by mordred.cs.ucla.edu (8.8.8/8.8.8) id WAA28699
	for freebsd-current@freebsd.org; Tue, 7 Apr 1998 22:27:04 -0700 (PDT)
	(envelope-from scottm)
Date: Tue, 7 Apr 1998 22:27:04 -0700 (PDT)
From: Scott Michel <scottm@cs.ucla.edu>
Message-Id: <199804080527.WAA28699@mordred.cs.ucla.edu>
To: freebsd-current@FreeBSD.ORG
Subject: Stabler current
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a kernel cvsup'd from this morning, on or about 10am PDT.
Was able to do a buildworld w/o strange warning or compiler aborts
(I don't want to hear about bad RAM -- I've actually replaced the
SIMMs twice and duplicated the same symptoms. I don't think that's
a coincidence.)

There was one weird hang on NFS, but was unable to duplicate that.
Will see how much uptime I can get out of it before I have to
actually reboot.


-scooter

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message