From owner-freebsd-current Sat Sep 9 13:07:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA26856 for current-outgoing; Sat, 9 Sep 1995 13:07:24 -0700 Received: from cps201.cps.cmich.edu (cps201.cps.cmich.edu [141.209.20.201]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA26850 for ; Sat, 9 Sep 1995 13:07:21 -0700 Received: from cps201 (cps201.cps.cmich.edu [141.209.20.201]) by cps201.cps.cmich.edu (8.6.12/8.6.12) with SMTP id QAA22315; Sat, 9 Sep 1995 16:07:19 -0400 Date: Sat, 9 Sep 1995 16:07:18 -0400 (EDT) From: Mail Archive X-Sender: archive@cps201 To: John Capo cc: davidg@Root.COM, roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: sig 11 In-Reply-To: <199509091851.OAA16895@irbs.irbs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Sat, 9 Sep 1995, John Capo wrote: > Mail Archive writes: > > > > On Sat, 9 Sep 1995, David Greenman wrote: > > > > > ... > > > >pid 123: sed: uid 8: exited on signal 11 > > > >pid 126: sed: uid 8: exited on signal 11 > > These kinds of problems are all part of running -current. Current > is a development tree and is quite often broken for one reason or > another. Like the docs say, "The bleeding edge". > > Sounds like you should be running -stable rather than -current. I have been compiling -stable for the last 4 hours it just finished rebooted and got the EXACT same thing... You explain why it doesn't matter....