summaryrefslogtreecommitdiff
path: root/bitbake
diff options
context:
space:
mode:
authorGary Thomas <gary@mlbassoc.com>2011-02-17 11:35:41 -0700
committerRichard Purdie <rpurdie@linux.intel.com>2011-03-01 11:46:37 +0000
commitd0c42255619992392ca98fb871f8781bb2691543 (patch)
tree3b5d1678c24b9325b12146630101a8270ba8c3a1 /bitbake
parent949f85cdd79536e35cb7f983c52e5f8eca9736df (diff)
downloadopenembedded-core-d0c42255619992392ca98fb871f8781bb2691543.tar.gz
openembedded-core-d0c42255619992392ca98fb871f8781bb2691543.tar.bz2
openembedded-core-d0c42255619992392ca98fb871f8781bb2691543.tar.xz
openembedded-core-d0c42255619992392ca98fb871f8781bb2691543.zip
Suppress useless warnings during udev startup
I have a number of platforms which have no realtime clock (i.e. no sense of what day/time it is). On these platforms, poky dutifully tries to keep somewhat sane with stored time stamps that are saved on reboot and restored early on during initialization. A fair compromise. However, before that code runs, the udev script tries to restore well known devices using tar. This will often lead to messages such as these since the kernel has no way to set the time: tar: dev/pts: implausibly old time stamp 1970-01-01 00:00:00 tar: dev/char/3:134: time stamp 1970-01-01 00:00:09 is 0.435041705 s in the future The attached patch filters these messages out as they don't convey anything useful and indeed are worrisome to more naive users. -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ >From a6773d3e00dbd168817730fff1c3fc7e1b6950f5 Mon Sep 17 00:00:00 2001 From: Gary Thomas <gary@mlbassoc.com> Date: Thu, 17 Feb 2011 11:30:18 -0700 Subject: [PATCH] Suppress messages about bad time stamps during initial device setup Signed-off-by: Gary Thomas <gary@mlbassoc.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'bitbake')
0 files changed, 0 insertions, 0 deletions