James Turnbull wrote:
According to
http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap03.html#tag_03_266:
"Multiple successive slashes are considered to be the same as one
slash.", so '//tmp/xxx' is a valid POSIX pathname.
You should probably read section 3.2 then as well:
3.2 Absolute Pathname
A pathname beginning with a single or more than two slashes;
see also Pathname.
Note that a pathname starting with exactly two slashes is *not*
an absolute pathname according to Posix. And 4.11 (Pathname
Resolution) says:
A pathname that begins with two successive slashes may be
interpreted in an implementation-defined manner, although
more than two leading slashes shall be treated as a single
slash.
Posix has this rule to accomodate DomainOS, which was a Unix-
like OS from Apollo, where paths on the form "//foo/bar/gazonk"
meant the file "/bar/gazonk" on the machine named "foo". You may
recognize this format from URLs, or MS Windows SMB paths (with
backslashes instead of forward slashes).
You should however not take this as me thinking the change is bad.
I actually think it is quite reasonable to allow such paths in
file resources. But maybe the commit message could be better. :-)
(And it *would* be nice to break that superlong line so it becomes
readable.)
/Bellman
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
