> > James Harper wrote: > > The docs > > http://www.bacula.org/manuals/en/install/install/Configuring_Director.ht > > ml#SECTION00870000000000000000 state of windows filesets: > > > > " > > In addition, on Windows machines, you should always prefix the directory > > or filename with the drive specification in lower case (e.g. c:/xxx) > > using Unix directory name separators (forward slash). > > " > > > > But then under "A Windows Example FileSet", upper case drive letters are > > used everywhere > > I believe using upper or lower case gives the same results. > > I wonder if there is merit is using one or the other. > > The OP's point is: The documentation says to use lower case, but our > examples use upper case. > > Is there any reason we mention lower case? >
D'oh. I forgot to reference the post from -users. Look for a post from "Mike Ruskai" with a subject of "Paths for Windows file daemons". The contents here: " Exclude = "E:/path/directory" = ignored Exclude = "e:/path/directory" = respected I have never been a fan of case-sensitive file systems. There's no good reason to have them, and plenty of good reasons to not have them. But the fact is, Windows is case-preservative, not case-sensitive. Shouldn't Bacula, since it wants to support Windows, be able to function without case-sensitivity? Ignoring that, at least the documentation should be updated to use lower-case drive letters, since upper-case ones don't work. " ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
