From owner-freebsd-stable Sat Sep 25 19:45:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (castles560.castles.com [208.214.165.124]) by hub.freebsd.org (Postfix) with ESMTP id 4F39C14BD4 for ; Sat, 25 Sep 1999 19:45:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA08908; Sat, 25 Sep 1999 19:37:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909260237.TAA08908@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mandm@alaska.com Cc: "Daniel C. Sobral" , thomas@hentschel.net, freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 3.3 installation In-reply-to: Your message of "Sat, 25 Sep 1999 18:27:28 -0800." <19990926023124.255A514CEF@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Sep 1999 19:37:38 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just a update on 3.3 > Today (25Sept) I downloaded the latest snap of 3.3 (19990925) and tried to > install it. I got the same signal 11 at the exact same spot as before! To > help with memory, it was just after filling in the blanks on the network > configuration screen. When I then clicked on the ok button, up popped the > "caught signal 11" screen! Now the weird part. I then used these same > disks to upgrade my 3.2 and it worked great! No problems on the software > side (I made a mistake on what to mount, but that was my fault). Perhaps > this should be sent to hackers or current? No. You haven't included anything like enough information yet for the report to be at all useful. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message