From owner-freebsd-arch Sun Dec 10 4:24:48 2000 From owner-freebsd-arch@FreeBSD.ORG Sun Dec 10 04:24:46 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 9335437B400 for ; Sun, 10 Dec 2000 04:24:45 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBACOeL97670; Sun, 10 Dec 2000 13:24:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: arch@FreeBSD.ORG Subject: Re: inheriting the "nodump" flag ? In-Reply-To: Your message of "Sun, 10 Dec 2000 03:47:52 PST." <3A336D68.2B454829@elischer.org> Date: Sun, 10 Dec 2000 13:24:40 +0100 Message-ID: <97668.976451080@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A336D68.2B454829@elischer.org>, Julian Elischer writes: >> I would like to propose that directories and files inherit the >> nodump flag if it is set on the directory they are created in. >> >> Comments ? protests ? > >I thought that it was supposed to stop the tree walker from walking >down through the tree beyond that point if it is on a directory.. > >in other words, if you set it on a directory it is supposed to >'prune' the entire tree.. sounds like a problem with the >tree walker rather than the kernel. Well, dump's tree walker is rather peculiar, so I don't blame anyone for the way it is implemented currently. -- 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