From owner-freebsd-current Fri Oct 16 21:40:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26990 for freebsd-current-outgoing; Fri, 16 Oct 1998 21:40:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26888 for ; Fri, 16 Oct 1998 21:40:01 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id AAA04868; Sat, 17 Oct 1998 00:37:55 -0400 (EDT) Date: Sat, 17 Oct 1998 00:37:55 -0400 (EDT) From: Chuck Robey To: "Steven P. Donegan" cc: freebsd-current@FreeBSD.ORG Subject: Re: softupdates/smp In-Reply-To: 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 Fri, 16 Oct 1998, Steven P. Donegan wrote: > After a long biz trip and other adventures... > > I finally got back to the list, and compiled today's kernel (SMP). Tried > a boot - no problem. Turned on softupdates on the disk (tunefs -n > enable). Boot proceeded and then tombstone. Is softupdates viable on > anyone's hardware at present under SMP? Solid here. With CAM and softupdates. Buildworlds like crazy. Wasn't always that way, but is now. Real good, this machine get's used heavily for schoolwork (I shouldn't run current on it, but I've been too heavily infected with FreeBSD). It's a dual P6-166, Tyan Titan II. Wouldn't part with it for the world. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message