Message-Id: <200508032354.j73NsbcK024278@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Gary R. Van Sickle" To: Subject: RE: Cygwin and NTFS Junction Points Date: Wed, 3 Aug 2005 18:55:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <0B9EBBE7CA79D7118FD00002B3B2B9B9108F4FB9@nm75ex51.das.honeywell.com> X-IsSubscribed: yes > From: cygwin-owner AT cygwin DOT com > [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Baksik, Frederick (NM75) > From the links below it seems that windows itself doesn't > handle NTFS junctions points well. Sounds like another > feature that wasn't well thought out, kind of like NTFS > alternate data streams. > > "More than four years after this functionality became > available, it seems Microsoft still has barely documented it, > and hasn't exposed it in Windows except in the most cursory > way. It is still a far bigger chore than necessary finding > information about this functionality in Microsoft's knowledge > base. Anyone who want to learn about it can only resort to > scrounging across the web. Links on Windows exist, but they > are useable only due to the efforts of a handful of third > party tools developers." > > -- Frodak > Weren't we supposed to have ditched filesystems entirely by now, and be storing all of our ASCII text files with their completely-intractable combination of "\r\n"/"\n"/"\r" line endings in some sort of object-oriented database or some such madness? -- Gary R. Van Sickle -- 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/