[uml-devel] [[email protected]: Bug#224215: incorrect /proc timestamp]

----- Forwarded message from Nate Riffe <[email protected]> -----

Date: Tue, 16 Dec 2003 19:17:10 -0600
From: Nate Riffe <[email protected]>
Resent-From: Nate Riffe <[email protected]>
To: [email protected]
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.

--< ((\))< >----< [email protected] >----< http://www.movealong.org/ >--
pub  1024D/05A058E0 2002-03-07 Nate Riffe (06-Mar-2002) <[email protected]>
     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
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

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 [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Jeff,

Looking at uml-patch-2.6.3-rc2-1, I noticed it needs the RTC fix (mhz to unsigned
long long) for CPUs > 2.1Ghz This is just a friendly reminder to make sure that
change makes it into your 2.6 tree (looks good on 2.4)..

Thanks,
-Chris

-------------------------------------------------------
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 [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Right. Generic fixes (2.4 and 2.6) usually start off in my 2.4 tree, then get migrated into my 2.6 tree when I get around to it.

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 [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel