Date: Tue, 9 Feb 1999 14:41:06 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Mark Hannon <mark.hannon@stockholm.mail.telia.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Change to inherit nodump flag? Message-ID: <199902092241.OAA61365@apollo.backplane.com> References: <36C0A3C4.E9CDA301@stockholm.mail.telia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:Hi,
:I dump some of my filesystems to my (small) floppy tape drive as backup.
:
:This works quite well as long as I only dump my own data files. To
:avoid
:dumping easily recoverable files I run a script which runs:
:
: chflags -R nodump /home/ncvs
:...
:is a time consuming affair. As a way around this I thought maybe the
:...
:I had a quick look in the code and I am guessing that I should implement
:
:such a change in:
:
: /sys/ufs/ufs/ufs_vnops.c in functions ufs_makeinode & ufs_mkdir
:
:Is this where the functionality should be implemented?
:...
:Regards/Mark
Yes, somewhere around line 2091 of ufs_vnops.c ( ufs_create() ).
Also around line 1296 of ufs_vnops.c ( ufs_mkdir() ). Just after
the gid inheritance.
...
ip = VTOI(tvp);
ip->i_gid = pdir->i_gid;
<-------------------- here
...
The 'i_flags' field ( not to be confused with 'i_flag' ) would have
to inherit the directory's nodump flag.
Personally, I think this is the correct way of doing it - nodump
would be inherited just as directory gid is inherited.
Another solution would be to hack the 'dump' program to be able to
remember 'nodump' recursively. I don't think that is as good a
solution as adjusting i_flags on create.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902092241.OAA61365>