X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18565.62440.276122.674758@amman.clic.cs.columbia.edu> Date: Tue, 22 Jul 2008 10:51:20 -0400 In-Reply-To: To: "Mark J. Reed" Cc: cygwin AT cygwin DOT com Subject: Re: Strange things with cygdrive References: <48850832 DOT 8020804 AT alice DOT it> <4885B516 DOT 1030700 AT alice DOT it> X-Mailer: VM 7.19 under Emacs 22.1.1 From: lennox AT cs DOT columbia DOT edu Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Mark J. Reed writes: > /cygdrive is not a real directory. That "horrible" metadata you're > complaining about isn't actually stored anywhere, it's generated by > the system when you ask for it. A modification to the cygwin > filesystem code could change what it reports, but what would you have > it report? What's the meaning of the "last modified" date on a > nonexistent directory that can't actually be modified? The most recent time a drive was mounted or unmounted, presumably, since that's what causes the contents of that directory to change. Actually keeping track of this is probably not worth the effort, though (especially since it's not clear where you'd store it). -- Jonathan Lennox lennox at cs dot columbia dot edu -- 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/