X-Spam-Check-By: sourceware.org
Message-ID: <4390B04F.9060709@ieee.org>
Date: Fri, 02 Dec 2005 20:36:31 +0000
From: Jason Pearce <jason DOT pearce AT ieee DOT org>
User-Agent: Thunderbird 1.5 (Windows/20051025)
MIME-Version: 1.0
To: Cygwin List <cygwin AT cygwin DOT com>
CC: Hermann DOT Schinagl AT gmx DOT net
Subject: Re: Hard links on a UDF file system
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

This is just a post back from my earlier question.
I discovered that my "direct to disc" utility creates a UDF file system 
on my DVD burner. I never realised these utilities used something of a 
standard... Anyway that allowed me to experiment with UDF on my XP machine.

XP has the fsutil functions (that were not available under Win2K with 
the REV drive was)
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx

So after formatting the disc with UDF I gave it a try and discovered 
that it truly is windows that imposes the restriction
[/cygdrive/e]$ fsutil hardlink create link file
The FSUTIL utility requires a local NTFS volume.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/