e8b059a274
Changes: Add support for logger -k, early log to /dev/kmsg. Useful when logging from early system startup scripts before syslogd has started Support for extracting non-kernel log messages from /dev/kmsg Ignore EINVAL from kernel, caused warning message at first startup Use journald socket on systemd systems, not /dev/log Issue #38: add support for syslogd -C file to use file for caching the last seen kernel sequence number, default: /run/syslogd.cache. Note: syslogd relies on the location of this file to be wiped at system boot. The default, /run, is a RAM disk on modern systems Fixes Issue #34: regression in v2.2.3, causing loss of syslogd log messages like syslogd v2.2.3: restart. Issue #35: man pages lists -v as verbose mode, is actually version Issue #36: retry DNS lookup of remote syslog servers with res_init() to ensure name resolution at bootup when a remote DNS may temporarily be unreachable. Retry at most every five seconds, to prevent syslogd from monopolizing the CPU when emptying the kernel ring buffer Issue #39: update tests to use -P fn and -C fn Issue #40: improve documentation for syslogd.cache file requirements Issue #41: add missing documentation for -H option Issue #42: add option (-K) to always trust kernel timestamp. By default syslogd only trusts the kernel timestamp for the initial emptying of the kernel ring buffer Issue #43: avoid asserting (exiting) on and around Jan 19, 2038, when the UNIX epoch wraps around on 32-bit time_t systems libsyslog: handle EOVERFLOW from gettimeofday() on Jan 19, 2038 Avoid NULL pointers to internal logit() function, only triggered when in debug mode Replace \m with \n (missing newline) in logger usage text (From OE-Core rev: 84de7a1f3863989c437a8fcf34255399c10e4143) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.