From: Mark Hatle <mark.hatle@windriver.com>
To: poky@pokylinux.org
Subject: Re: Inconsistent timestamp use
Date: Wed, 03 Nov 2010 10:05:38 -0500 [thread overview]
Message-ID: <4CD17A42.9070103@windriver.com> (raw)
In-Reply-To: <4CD16A8E.7090100@mlbassoc.com>
I was wondering why that wasn't working before.
It was also mentioned to me by someone at CELF that a lot of devices check the
superblock times to set their clocks as well. I don't know if Poky has this
behavior, but if it does that is not working either.
--Mark
On 11/3/10 8:58 AM, Gary Thomas wrote:
> The Poky root file system (init scripts) has a mechanism for
> supporting systems without a working hardware [time of day] clock.
> It seems that this has suffered some rot recently and is now
> quite inconsistent:
> * rootfs_update_timestamp() uses a different format for the time stamp
> * the init scripts look for /etc/timestamp2, not /etc/timestamp which
> is created with the image
>
> The attached patch makes this consistent and the system clock now works
> much better (about as good as a machine without a hardware clock can!)
>
next prev parent reply other threads:[~2010-11-03 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 13:58 Inconsistent timestamp use Gary Thomas
2010-11-03 15:05 ` Mark Hatle [this message]
2010-11-03 15:35 ` Saul Wold
2010-11-03 15:45 ` Gary Thomas
2010-11-03 22:34 ` Saul Wold
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=4CD17A42.9070103@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@pokylinux.org \
/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