X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40 X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4B8EB178.20104@redhat.com> References: <4B8EB178.20104@redhat.com> Date: Wed, 3 Mar 2010 20:04:47 +0000 Message-ID: Subject: Re: ln command in Cygwin (hard links) From: John Gilmartin To: Eric Blake , cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Solved. :-) Apologies Larry, I will know to look up the reporting guidelines for next t= ime. Eric, thanks, you've hit the nail on the head. I didn't realise this could be due to a file system type limitation, but I know now. :-) Always learning! Thanks. John On 3 March 2010 18:59, Eric Blake wrote: > According to John Gilmartin on 3/3/2010 11:48 AM: >> Am I going mad? Why doesn't the following work for me? >> >> $ ln hardlink1 hardlink2 >> ln: creating hard link `hardlink2' =3D> `hardlink1': Operation not permi= tted > > $ df -T . > > I bet you are trying this on FAT, which does not support hard links. > > Consider using NTFS instead. > > -- > Eric Blake =A0 eblake@redhat.com =A0 =A0+1-801-349-2682 > Libvirt virtualization library http://libvirt.org > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple