From owner-freebsd-current Sat Sep 9 13:20:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA27642 for current-outgoing; Sat, 9 Sep 1995 13:20:47 -0700 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA27634 for ; Sat, 9 Sep 1995 13:20:40 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.9) id WAA18054; Sat, 9 Sep 1995 22:19:11 +0200 From: John Hay Message-Id: <199509092019.WAA18054@zibbi.mikom.csir.co.za> Subject: Re: sig 11 To: archive@cps.cmich.edu (Mail Archive) Date: Sat, 9 Sep 1995 22:19:11 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Mail Archive" at Sep 9, 95 04:07:18 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 924 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.... > Did you recompile the kernel also when you went to -stable? Because I think that the problem may be in the kernel. In any case I don't think a -current kernel will work well with -stable user level programs. -- John Hay -- jhay@mikom.csir.co.za