From owner-freebsd-arch  Sun Dec 10  9:38: 1 2000
From owner-freebsd-arch@FreeBSD.ORG  Sun Dec 10 09:37:58 2000
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mail.interware.hu (mail.interware.hu [195.70.32.130])
	by hub.freebsd.org (Postfix) with ESMTP id 3316937B400
	for <arch@freebsd.org>; Sun, 10 Dec 2000 09:37:58 -0800 (PST)
Received: from gaborone-42.budapest.interware.hu ([195.70.52.170] helo=elischer.org)
	by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian))
	id 145APy-0002gQ-00; Sun, 10 Dec 2000 18:37:46 +0100
Sender: julian@FreeBSD.ORG
Message-ID: <3A33BF4B.97EE1BCC@elischer.org>
Date: Sun, 10 Dec 2000 09:37:15 -0800
From: Julian Elischer <julian@elischer.org>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en, hu
MIME-Version: 1.0
To: "Jeroen C. van Gelderen" <jeroen@vangelderen.org>
Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, arch@FreeBSD.ORG
Subject: Re: inheriting the "nodump" flag ?
References: <97668.976451080@critter> <3A33BCCE.844B35B4@vangelderen.org>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Jeroen C. van Gelderen" wrote:
> 
>
> This answer does not address the real point Julian is trying
> to make. Trying to fix a buggy dump implementation by patching
> the kernel is the wrong approach. It doesn't matter how peculiar
> the tree walker is, if it's buggy the fixing needs to be done
> there.

thanks:
well the patch is there on the URL given below.
I fully support implementing it on FreeBSD as well.
(with a little testing)

> 
> 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
> [...]
> >Release-Note:
> >Audit-Trail:
> State-Changed-From-To: open->closed
> State-Changed-By: bouyer
> State-Changed-When: Tue Mar 9 09:32:08 PST 1999
> State-Changed-Why:
> Functionality added [to dump I presume], but differently.
> ^^^^^^^^^^^^^^^^^^^
> 
> It seems that fixing dump is the correct approach. Changing
> the semantics to nodump almost certainly is not as Julian
> pointed out in his other mail (<3A336EA3.9F1FE318@elischer.org>).
> 
> I can now even add another reason why changing the kernel isn't
> such a good plan: inter-BSD compatibility.
> 
> Cheers,
> Jeroen
> --
> Jeroen C. van Gelderen          o      _     _         _
> jeroen@vangelderen.org  _o     /\_   _ \\o  (_)\__/o  (_)
>                       _< \_   _>(_) (_)/<_    \_| \   _|/' \/
>                      (_)>(_) (_)        (_)   (_)    (_)'  _\o_

-- 
      __--_|\  Julian Elischer
     /       \ julian@elischer.org
    (   OZ    ) World tour 2000
---> X_.---._/  presently in:  Budapest
            v


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message