X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Tue, 22 Jul 2008 12:26:20 -0400 From: "Mark J. Reed" To: cygwin@cygwin.com Subject: Re: Strange things with cygdrive In-Reply-To: <48860253.4010707@alice.it> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48850832.8020804@alice.it> <4885B516.1030700@alice.it> <48860253.4010707@alice.it> X-Google-Sender-Auth: dccc1b92e9d59881 X-IsSubscribed: yes 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 On Tue, Jul 22, 2008 at 11:52 AM, Angelo Graziosi wrote: > If I have well understood '/proc' is a virtual directory like '/cygdrive', > but for it > > dr-xr-xr-x 1 Administrator Administrators 0 Dec 1 2006 proc Well, now, that's a very good point. The mod time on /proc seems to be set to Dec 1st, 2006 at midnight UTC (same on my system) - where did that number come from? It seems like some consistency among virtual directories isn't too much to ask. Although for /proc it would also make sense for the mod time to be the boot time, or, fully embracing the the directory metaphor, the time the last process was created or destroyed. -- 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/