1.5 Filenames and paths
Filenames in Unix-lik operating systems
The directory separator is the forward slash '/' character. All references
to file locations must be absolute names in cfengine, i.e. they must begin
with a complete specification of which directory they are in. For example:
The only place where it makes sense to refer to a file without a complete
directory specification is when searching through directories for different
kinds of file, e.g.
/home/user pattern=core age=0 recurse=inf
Here, one can write `core' without a path, because one is looking for any
file of that name in a number of directories.
Cfengine was implemented primarily on Unix-like operating systems, but
has since been ported to Windows operating systems and MacOS X. The Windows
operating systems traditionally use a different filename convention.
The following are all valid absolute file names under Windows:
The `drive' name "C:" in Windows refers to a partition or device. Unlike Unix,
Windows does not integrate these seamlessly into a single file-tree.
This is not a valid absolute filename:
Paths beginning with a backslash are assumed to be win32 paths. They
must begin with a drive letter or double-slash server name.