Kirk McKusick [EMAIL PROTECTED] writes:
You would think I would remember code that I wrote (though in my
defense it was written over 20 years ago :-)
hey, I can't even remember code that I wrote 20 days ago, much less 20
years, so I won't be the one to cast the first stone :)
DES
--
Kirk McKusick [EMAIL PROTECTED] writes:
You would think I would remember code that I wrote (though in my
defense it was written over 20 years ago :-)
hey, I can't even remember code that I wrote 20 days ago, much less 20
years, so I won't be the one to cast the first stone :)
it's not that
Hello!
I'd like the entire contents of each user's .mozilla/firefox/*/Cache directory
to be excluded from the regular filesystem dumps.
Running ``chflags -R nodump /home/*/.mozilla/firefox/*/Cache'' does the trick,
but this needs to be redone daily -- prior to running the backup -- because
Mikhail Teterin wrote:
I'd like the entire contents of each user's .mozilla/firefox/*/Cache directory
to be excluded from the regular filesystem dumps.
Running ``chflags -R nodump /home/*/.mozilla/firefox/*/Cache'' does the trick,
but this needs to be redone daily -- prior to running the
Mikhail Teterin [EMAIL PROTECTED] writes:
I'd like the entire contents of each user's .mozilla/firefox/*/Cache
directory to be excluded from the regular filesystem dumps.
Running ``chflags -R nodump /home/*/.mozilla/firefox/*/Cache'' does
the trick, but this needs to be redone daily -- prior
Mikhail Teterin wrote:
Hello!
I'd like the entire contents of each user's .mozilla/firefox/*/Cache directory
to be excluded from the regular filesystem dumps.
Running ``chflags -R nodump /home/*/.mozilla/firefox/*/Cache'' does the trick,
but this needs to be redone daily -- prior to running
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= [EMAIL PROTECTED]
To: Mikhail Teterin [EMAIL PROTECTED]
Date: Wed, 30 Jan 2008 18:54:02 +0100
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Automatic `nodump' flag?
Mikhail Teterin [EMAIL PROTECTED] writes:
I'd like the entire contents
Kirk McKusick wrote:
The dump program runs on the raw disk partition dumping sequentially
by inode number. So, it has no idea of the file-tree hierarchy.
I was just looking at the source to dump, specifically traverse.c and
from what I can see, doesn't dump pass #2 scan through all
The dump program runs on the raw disk partition dumping sequentially
by inode number. So, it has no idea of the file-tree hierarchy. Thus
any propagation of the nodump flag would have to be done by the
Yes, dump DO descend to check for nodump flags - while doing backup for
raw filesystem.
Date: Wed, 30 Jan 2008 16:13:54 -0600
From: Barry Pederson [EMAIL PROTECTED]
To: Kirk McKusick [EMAIL PROTECTED]
CC: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= [EMAIL PROTECTED], [EMAIL
PROTECTED],
[EMAIL PROTECTED]
Subject: Re: Automatic `nodump' flag?
X-ASK-Info: Message Queued
10 matches
Mail list logo
