From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH] udev: get rid of 'timestamp in the future' tar messages
Date: Fri, 29 Jan 2010 15:44:29 +0100 [thread overview]
Message-ID: <1264776269.7864.0.camel@gnutoo-desktop> (raw)
In-Reply-To: <1264615116-13972-1-git-send-email-ynezz@true.cz>
On Wed, 2010-01-27 at 18:58 +0100, Petr Štetiar wrote:
> This patch tries to get rid of spew of the useless tar messages durring boot
> process on machines without RTC, such as the Beagleboard. Example:
>
> Please wait: booting...
> Starting udev
> tar: dev/.udev/uevent_seqnum: time stamp 1970-01-01 01:00:21 is 14.122497521 s in the future
> tar: dev/.udev/rules.d: time stamp 1970-01-01 01:00:07 is 0.119201623 s in the future
> tar: dev/.udev/db/\x2fdevices\x2fvirtual\x2fblock\x2fram9: time stamp 1970-01-01 01:00:22 is 15.118713341 s in the future
>
> [ more then 100 similar lines cutted off]
Nice,I had the issue with the bug device.
Denis.
prev parent reply other threads:[~2010-01-30 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 17:58 [RFC][PATCH] udev: get rid of 'timestamp in the future' tar messages Petr Štetiar
2010-01-27 18:02 ` Chris Larson
2010-01-27 19:02 ` Koen Kooi
2010-01-29 14:44 ` GNUtoo [this message]
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=1264776269.7864.0.camel@gnutoo-desktop \
--to=gnutoo@no-log.org \
--cc=openembedded-devel@lists.openembedded.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