From: Jeff Dike <jdike@addtoit.com>
To: Matt Zimmerman <mdz@debian.org>
Cc: user-mode-linux-devel@lists.sourceforge.net,
224215-forwarded@bugs.debian.org
Subject: Re: [uml-devel] [inkblot@movealong.org: Bug#224215: incorrect /proc timestamp]
Date: Fri, 13 Feb 2004 19:43:07 -0500 [thread overview]
Message-ID: <200402140043.i1E0h7sq004297@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Sun, 11 Jan 2004 22:46:20 PST." <20040112064620.GU1436@alcor.net>
mdz@debian.org said:
> The timestamp of /proc after mounting the proc filesystem is fixed at
> Jan 1, 1970 (likely initialized to 0 in Unix time and then never set).
This will be fixed in the next patch. The problem was that no timer interrupts
had fired by the time /proc was first mounted, so xtime, which is used to
initialize the /proc inode times, was still 0.
Jeff
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-02-14 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 6:46 [uml-devel] [inkblot@movealong.org: Bug#224215: incorrect /proc timestamp] Matt Zimmerman
2004-02-14 0:43 ` Jeff Dike [this message]
2004-02-14 1:52 ` [uml-devel] uml-patch-2.6.3-rc2-1, RTC, CPU > 2.1 Ghz Christopher S. Aker
2004-02-14 4:00 ` [uml-devel] " Jeff Dike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200402140043.i1E0h7sq004297@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=224215-forwarded@bugs.debian.org \
--cc=mdz@debian.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox