On 11/12/2007 21:22 PM, "Jan Steinman" <email@hidden> wrote:
Since TM relies on folder hard links, that could be an issue.
That is not my understanding of how it works. A POSIX-compliant file
system cannot have directory hard links.
Well, for one, I don't think HFS+ is particularly POSIX-compliant...
That may explain it...
... but even
if it is not, it is HFS+ in leopard that supports Directory Hard
links. As
well, from what I've read, there's nothing in POSIX that forbids
directory
hard links...
I didn't just blurt this out. I did do some minimal research. (# man 2
link :-)
Someone needs to update the man page that comes with XCode 3.0, latest
download from developer.apple.com. I did read the mactech.com article,
and it would be cool if this new behavior were officially documented
somewhere besides what some guy discovered by tracing system calls.
But if you're a good little programmer, you'll still pay attention to
the man page. I'd deem this behavior "for Apple use only" at this point!
LINK(2) BSD System Calls Manual
LINK(2)
NAME
link -- make a hard file link
SYNOPSIS
#include <unistd.h>
int
link(const char *path1, const char *path2);
DESCRIPTION
...
As mandated by POSIX.1, path1 may not be a directory.
ERRORS
Link() will fail and no link will be created if:
...
[EPERM] The file named by path1 is a directory.
:::: I will not be as those who spend the day in complaining of
headache, and the night in drinking the wine that gives it. --
Göthe ::::
:::: Jan Steinman <http://www.VeggieVanGogh.com> ::::
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
