| Summary: | [busybox] date command does not accept linux time setting format | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Jiajun Xu <jiajun.xu> |
| Component: | meta-yocto | Assignee: | Saul Wold <sgw> |
| Status: | VERIFIED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, kevin.tian, kunwei.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw, xianchao.zhang |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
Jiajun Xu
2010-09-29 20:29:13 UTC
There are 2 different date commands as you noticed, depending on which image you are looking at it will either be from busybox as you noted or from coreutils. Yes the behaviour of the 2 is subtly different.
You will find busybox version in minimal and sato, while the coreutils version will be in sdk, basic and lsb.
The busybox version uses the following options:
date [OPTIONS] [+FMT] [TIME]
Display time (using +FMT), or set time
Options:
[-s] TIME Set time to TIME
-u Work in UTC (don't convert to local time)
-R Output RFC-822 compliant date string
-I[SPEC] Output ISO-8601 compliant date string
SPEC='date' (default) for date only,
'hours', 'minutes', or 'seconds' for date and
time to the indicated precision
-r FILE Display last modification time of FILE
-d TIME Display TIME, not 'now'
-D FMT Use FMT for -d TIME conversion
Recognized TIME formats:
hh:mm[:ss]
[YYYY.]MM.DD-hh:mm[:ss]
YYYY-MM-DD hh:mm[:ss]
[[[[[YY]YY]MM]DD]hh]mm[.ss]
While the coreutils version of date has the following expanded options:
date [option]... [+format]
date [-u|--utc|--universal]
[ MMDDhhmm[[CC]YY][.ss] ]
Notice the difference in the nesting of optional date with the [] between the 2 versions.
See: http://www.gnu.org/software/coreutils/manual/coreutils.html#date-invocation
for more details
Thanks for your explanation, it's clear for me now. Verify the bug. |