From owner-freebsd-current  Fri Jan 15 09:59:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA15941
          for freebsd-current-outgoing; Fri, 15 Jan 1999 09:59:08 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15928
          for <current@freebsd.org>; Fri, 15 Jan 1999 09:59:04 -0800 (PST)
          (envelope-from matt@megaweapon.zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.8.8/8.8.8) with ESMTP id MAA06762
	for <current@freebsd.org>; Fri, 15 Jan 1999 12:59:01 -0500 (EST)
	(envelope-from matt@megaweapon.zigg.com)
Date: Fri, 15 Jan 1999 12:59:00 -0500 (EST)
From: Matt Behrens <matt@megaweapon.zigg.com>
To: current@FreeBSD.ORG
Subject: sig11 from 3.0.0-19990106-SNAP
Message-ID: <Pine.BSF.4.05.9901151256450.6751-100000@megaweapon.zigg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I must have missed this on the list, but I caught a sig11 on
sysinstall from 3.0.0-19990106-SNAP.  DEBUG on VTY2 reports:

DEBUG: diskPartitionWrite: Examining 1 devices
DEBUG: bootalloc: can't stat /boot/boot1
DEBUG: bootalloc: can't stat /boot/boot2
DEBUG: Signal 11 caught!  That's bad!

Ideas?  Different SNAPs to try?  (This is completely reproducible.)

- Matt Behrens <matt@zigg.com>
  Network Administrator, zigg.com <http://www.zigg.com/>
  Engineer, Nameless IRC Network <http://www.nameless.net/>


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