X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Tue, 22 Jul 2008 09:23:06 -0400 From: "Mark J. Reed" To: cygwin AT cygwin DOT com Subject: Re: Strange things with cygdrive In-Reply-To: <4885B516.1030700@alice.it> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48850832 DOT 8020804 AT alice DOT it> <4885B516 DOT 1030700 AT alice DOT it> X-Google-Sender-Auth: 8773da59d8ec46ce X-IsSubscribed: yes 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 On Tue, Jul 22, 2008 at 6:23 AM, Angelo Graziosi wrote: > Oh thanks having reassured me. But is there some tricks to change that > user(0) and (horrible) date (01.01.1970)? /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? I think having it return zero is perfectly reasonable, but there are other reasonable choices. I suppose it could be set to some otherwise meaningful value like the build date.. -- Mark J. Reed -- 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/