From owner-freebsd-bugs Mon Aug 14 5:10: 4 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1F0EF37B9B0 for ; Mon, 14 Aug 2000 05:10:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA59539; Mon, 14 Aug 2000 05:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 14 Aug 2000 05:10:02 -0700 (PDT) Message-Id: <200008141210.FAA59539@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/20572: cannot safely remove COMPAT_43 from the kernel config Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/20572; it has been noted by GNATS. From: Sheldon Hearn To: Darren Reed Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/20572: cannot safely remove COMPAT_43 from the kernel config Date: Mon, 14 Aug 2000 14:06:04 +0200 On Mon, 14 Aug 2000 21:56:51 +1000, Darren Reed wrote: > I think the email from Mike (just recently) explained the situation - there > has been a "problem" created by changes to the signal code. If that's all that's standing in the way of COMPAT_43 becoming optional, then you should assign the PR to marcel, who'll probably have it sorted out in short order. I must admit, my impression was that this would take a lot of work to fix and that it wasn't a simple case of correcting one area of the kernel. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message