From owner-freebsd-arch Sun Dec 10 4:23:54 2000 From owner-freebsd-arch@FreeBSD.ORG Sun Dec 10 04:23:50 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 42CFE37B400 for ; Sun, 10 Dec 2000 04:23:47 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBACNRL97642; Sun, 10 Dec 2000 13:23:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: alex@big.endian.de (Alexander Langer) Cc: arch@FreeBSD.ORG Subject: Re: inheriting the "nodump" flag ? In-Reply-To: Your message of "Sun, 10 Dec 2000 12:35:16 +0100." <20001210123516.A12435@cichlids.cichlids.com> Date: Sun, 10 Dec 2000 13:23:27 +0100 Message-ID: <97640.976451007@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001210123516.A12435@cichlids.cichlids.com>, Alexander Langer writ es: >Thus spake Poul-Henning Kamp (phk@FreeBSD.ORG): > >> 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 think it is just a logical conclusion. > >To be honest, I can't even understand how files in a directory can be >dumped if the directory itself is marked as nodump. Yeah, dump(8) violates POLA a bit there, but it is that way due to the way it is implemented. It would also be nice to be able to give dump(8) a list of exclude/include patterns: -X '*.core' -X 'ktrace.out' -I '*.rej' (volounteers welcome :-) -- 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