From owner-freebsd-arch Sun Dec 10 11:25:30 2000 From owner-freebsd-arch@FreeBSD.ORG Sun Dec 10 11:25:29 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 4B38937B400 for ; Sun, 10 Dec 2000 11:25:28 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBAJPML00442; Sun, 10 Dec 2000 20:25:22 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: "Jeroen C. van Gelderen" , arch@FreeBSD.ORG Subject: Re: inheriting the "nodump" flag ? In-Reply-To: Your message of "Sun, 10 Dec 2000 09:37:15 PST." <3A33BF4B.97EE1BCC@elischer.org> Date: Sun, 10 Dec 2000 20:25:22 +0100 Message-ID: <440.976476322@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A33BF4B.97EE1BCC@elischer.org>, Julian Elischer writes: >> It looks like NetBSD have already addressed the problem a >> year ago: >> >> http://lists.openresources.com/NetBSD/tech-kern/msg00453.html >> >> for the beginning of a thread discussing the problem. This >> was the first hit Google returned for "nodump flag". Basic >> research is cheap these days... >> >> A look at the NetBSD PR in question (6705) reveals: >> http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=6705 Well, then we just need somebody to MFN it... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message