From owner-freebsd-current Sat Sep 9 13:40:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA28811 for current-outgoing; Sat, 9 Sep 1995 13:40:37 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA28804 for ; Sat, 9 Sep 1995 13:40:33 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id NAA01288; Sat, 9 Sep 1995 13:39:24 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id NAA00255; Sat, 9 Sep 1995 13:41:35 -0700 Message-Id: <199509092041.NAA00255@corbin.Root.COM> To: John Hay cc: archive@cps.cmich.edu (Mail Archive), freebsd-current@freebsd.org Subject: Re: sig 11 In-reply-to: Your message of "Sat, 09 Sep 95 22:19:11 +0200." <199509092019.WAA18054@zibbi.mikom.csir.co.za> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 09 Sep 1995 13:41:33 -0700 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. No, it won't...in fact, doing that will have all sorts of strange and unpredictable consequences. 2.1 system binaries and kernel are not compatible with 2.2 system binaries and kernel - you can't mix them successfully. Is that what you're doing??? -DG