Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!rochester!pt.cs.cmu.edu!f.gp.cs.cmu.edu!dtw
From: dtw@f.gp.cs.cmu.edu (Duane Williams)
Newsgroups: comp.sys.mac
Subject: Re: DiskFit VS Redux: My DEFINITE conclusion
Keywords: diskfit redux backup
Message-ID: <3305@pt.cs.cmu.edu>
Date: 15 Oct 88 01:45:53 GMT
References: <1988Oct4.162537.8158@mntgfx.mentor.com> <1988Oct5.085923.97@mntgfx.mentor.com> <446@husc6.harvard.edu>
Sender: netnews@pt.cs.cmu.edu
Organization: Carnegie-Mellon University, CS/RI
Lines: 20


In article <446@husc6.harvard.edu>, Rich Siegel writes:
| 2) DiskFit allows you to automatically exclude folders from a backup
| by putting their names in square brackets ( [ ] ). Therefore, if I
| create a new folder that I don't want backed up, I just name it, for
| example, "[Junk]". The next time I back up with DiskFit, I know that
| [Junk] and all folders and files within it will be skipped.

The [FolderName] convention seems like a pretty stupid idea to me.

Being able to specify a list of folders to be excluded is very nice.
Having to change their names in order to do so is not nice at all.
DiskFit should allow the user to specify the names of folders/files
to be excluded in some less ad hoc manner, preferably involving a
wildcard mechanism.  Why not a simple text file containing a list of
folder/file names?

-- 
uucp: ...!seismo!cmucspt!me.ri.cmu.edu!dtw
arpa: dtw@cs.cmu.edu