From: Matt Zimmerman <mdz@debian.org>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: 224215-forwarded@bugs.debian.org
Subject: [uml-devel] [inkblot@movealong.org: Bug#224215: incorrect /proc timestamp]
Date: Sun, 11 Jan 2004 22:46:20 -0800 [thread overview]
Message-ID: <20040112064620.GU1436@alcor.net> (raw)
----- Forwarded message from Nate Riffe <inkblot@movealong.org> -----
Date: Tue, 16 Dec 2003 19:17:10 -0600
From: Nate Riffe <inkblot@movealong.org>
Resent-From: Nate Riffe <inkblot@movealong.org>
To: submit@bugs.debian.org
Subject: Bug#224215: incorrect /proc timestamp
Package: user-mode-linux
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 causes problems for some distributions running as UML systems
using the user-mode-linux kernel, including Debian, which relies on the
timestamp of /proc to clear out the contents of /var/run and
/var/lock. Comments in the "bootmisc.sh" initscript indicate that the
/proc timestamp is normally the time at which /proc is mounted.
I have also seen this issue with every other UML kernel to which I
have access, and so I believe it is probably an upstream bug.
--
--< ((\))< >----< inkblot@movealong.org >----< http://www.movealong.org/ >--
pub 1024D/05A058E0 2002-03-07 Nate Riffe (06-Mar-2002) <inkblot@movealong.org>
Key fingerprint = 0DAC F5CB D182 3165 D757 C466 CD42 12A8 05A0 58E0
----- End forwarded message -----
--
- mdz
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-01-12 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 6:46 Matt Zimmerman [this message]
2004-02-14 0:43 ` [uml-devel] [inkblot@movealong.org: Bug#224215: incorrect /proc timestamp] Jeff Dike
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=20040112064620.GU1436@alcor.net \
--to=mdz@debian.org \
--cc=224215-forwarded@bugs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.