From owner-freebsd-current Fri Dec 13 12:38:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAC5237B401 for ; Fri, 13 Dec 2002 12:38:36 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 959D543EC5 for ; Fri, 13 Dec 2002 12:38:36 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 37103 invoked by uid 1000); 13 Dec 2002 20:38:37 -0000 Date: Fri, 13 Dec 2002 12:38:37 -0800 (PST) From: Nate Lawson To: current@FreeBSD.ORG Subject: Re: Losing the battle with RC1 In-Reply-To: <20021213202608.GB27316@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 13 Dec 2002, Dan Nelson wrote: > In the last episode (Dec 13), Julian Elischer said: > > It's always been there. the question is > > "Who has broken it?" > > I think it has just slowly bitrotted. I opened a PR on this in > November. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/45777 This is definitely something which needs to be fixed for 5.0. I think the minimal fix is updating the sysctl handler for dumpdev to warn if the device is smaller than mem and range checking in dumpsys which refuses to dump if there is not enough space (along with an error message). -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message