From owner-freebsd-arch Sun Dec 10 3:25:11 2000 From owner-freebsd-arch@FreeBSD.ORG Sun Dec 10 03:25:06 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 30C0537B400 for ; Sun, 10 Dec 2000 03:25:05 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBABP4L97288 for ; Sun, 10 Dec 2000 12:25:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org Subject: inheriting the "nodump" flag ? From: Poul-Henning Kamp Date: Sun, 10 Dec 2000 12:25:04 +0100 Message-ID: <97286.976447504@critter> Sender: phk@critter.freebsd.dk Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know how many of you know or even use the "nodump" file flag. It's utility is somewhat limited by the fact that it is not inherited from the parent directory. I like to mark my cvs tree as "nodump", there is no point in backing it up for me. Unfortunately, since the nodump flag is not inherited on creation I need to run "chflags -R nodump /home/ncvs" first every time I want to make a backup. 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 ? -- 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