From owner-freebsd-stable Mon Mar 23 15:22:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08459 for freebsd-stable-outgoing; Mon, 23 Mar 1998 15:22:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08284 for ; Mon, 23 Mar 1998 15:21:23 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA27192; Mon, 23 Mar 1998 15:21:13 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: David Malone cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-reply-to: Your message of "Mon, 23 Mar 1998 20:52:43 GMT." <9803232052.aa01569@salmon.maths.tcd.ie> Date: Mon, 23 Mar 1998 15:21:13 -0800 Message-ID: <27187.890695273@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Any chance of applying the fact that restore coredumps on filesystems > with a blocksize of 512? I tried to get John Dyson to apply the patch > but he seems too busy. The gnats tag is bin/5704. Argh. It never even got committed to -current, which meant that it got no shake-out period. I've applied it to -current and closed the PR. If nobody reports a problem with it in -current, I'll merge the change into the 2.2 branch after the release. Sorry, but it's just too close to the wire to bring in a change to restore that I don't understand the full ramifications of. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message