From owner-freebsd-hackers Tue Feb 9 15:34:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26446 for freebsd-hackers-outgoing; Tue, 9 Feb 1999 15:34:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26441 for ; Tue, 9 Feb 1999 15:34:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id PAA61881; Tue, 9 Feb 1999 15:34:28 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Feb 1999 15:34:28 -0800 (PST) From: Matthew Dillon Message-Id: <199902092334.PAA61881@apollo.backplane.com> To: Julian Elischer Cc: Mark Hannon , freebsd-hackers@FreeBSD.ORG Subject: Re: Change to inherit nodump flag? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I don't think this is a good idea : :a better idea is to make th eapplication not descend into trees that have :the nodump bit set on the directory. : :you can't "inherrit" all the way up a directory tree when it's moved :into a directory with the nodump flag set. : :(I have the same problem with the SUIDDIR option in around the same :piece of code..) : :julian True, but on the otherhand the FS implementation of 'nodump' inheritance would save your butt if you accidently renamed a directory/file into a 'nodump' subdirectory that you really wanted to dump - it would still back it up. After all, what happens when you rename a file with group A into a directory with group B ? The group doesn't change. And it shouldn't. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message