From owner-freebsd-arch Wed Dec 13 6:11: 3 2000 From owner-freebsd-arch@FreeBSD.ORG Wed Dec 13 06:11:00 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id 9F44F37B402; Wed, 13 Dec 2000 06:10:59 -0800 (PST) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id PAA76585; Wed, 13 Dec 2000 15:10:58 +0100 (CET) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id PAA37143; Wed, 13 Dec 2000 15:10:58 +0100 (CET) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 13 Dec 2000 15:10:58 +0100 (CET) From: Marius Bendiksen To: Poul-Henning Kamp Cc: arch@freebsd.org Subject: Re: inheriting the "nodump" flag ? In-Reply-To: <97286.976447504@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: 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 ? This appears entirely sensible, though you might want a sysctl to toggle the behaviour, or maybe a mount option. Alternately, you might want to put this in a seperate flag, but that mostly defeats the purpose unless you do some hairy magic to lazily propagate the real nodump flag. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message