From owner-freebsd-current Fri Jan 15 10:03:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16855 for freebsd-current-outgoing; Fri, 15 Jan 1999 10:03:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16848 for ; Fri, 15 Jan 1999 10:03:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01331; Fri, 15 Jan 1999 10:00:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901151800.KAA01331@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matt Behrens cc: current@FreeBSD.ORG Subject: Re: sig11 from 3.0.0-19990106-SNAP In-reply-to: Your message of "Fri, 15 Jan 1999 12:59:00 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Jan 1999 10:00:04 -0800 From: Mike Smith 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.) It's fixed. I just did a two-floppy install of the 12'th SNAP, it worked fine. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message