OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705
Go to file
Robert Yang ffef4dad89 Add a skeleton for init scripts
Add a skeleton for init scripts, the original structure is from
/etc/init.d/skeleton of Ubuntu 10.10, it is in sysvinit_2.87dsf, so add
the COPYRIGHT(GPLv2) of sysvinit_2.87dsf. Modified the original skeleton
a lot to make it as easy as possible, just use posix shell command, and
have tested it with core-image-minimal.

* The skeleton implements the following actions:
  - start, stop, restart, status, try-restart and force-reload.
    # force-reload is a alias of try-restart.

  - not implements reload, since only a few programs have it, just leave
    it as placeholder.

* Add /usr/sbin/skeleton-test to test /etc/init.d/skeleton

* The /etc/init.d/skeleton can be run and output the example messages:
  1) #./skeleton start (test start)
     Starting skeleton ...

  2) #./skeleton start (test start again when running)
     skeleton already running (1078).

  3) #./skeleton status (test status when running)
     skeleton is running (1078).

  4) #./skeleton stop (test stop)
     Stopped skeleton (1078).

  5) #./skeleton stop (test stop again)
     skeleton is not running; none killed.

  6) #./skeleton status (test status when stopped)
     skeleton is not running.

  7) #./skeleton restart (test restart when running)
     Stopped skeleton (1128).
     Starting skeleton ...

  8) #./skeleton restart (test restart when stopped)
     skeleton is not running; none killed.
     Starting skeleton ...

  9)  try-restart (or force-reload) means restart the service if the
      service is already running

     #./skeleton try-restart (test try-restart when stopped)
     skeleton is not running; none killed.

     #./skeleton try-restart (test try-restart when running)
      Stopped skeleton (1181).
      Starting skeleton ...

* Have used syslogd to test it in a real world(with both
  core-image-minimal and core-image-sato)

(From OE-Core rev: c1b6f840ad7c483e905f9a19eb2b5a8eac0b9973)

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-18 14:32:45 +01:00
bitbake git fetcher: add support for rebaseable git repo 2011-05-17 15:19:36 +01:00
documentation documentation/bsp-guide/bsp.xml: Updated Example Filesystem Layout 2011-05-17 20:07:48 +01:00
meta Add pidofproc to ${sysconfdir}/init.d/functions 2011-05-18 14:32:45 +01:00
meta-demoapps recipes: Add Upstream-Status to multiple recipes 2011-05-13 10:29:01 +01:00
meta-rt Rename poky-image-* -> core-image-* and task-poky-* -> task-core-* 2011-04-21 00:29:30 +01:00
meta-skeleton Add a skeleton for init scripts 2011-05-18 14:32:45 +01:00
meta-yocto Qt4OpenGL: Enable libopengl for platform emenlow and mpc8315e-rdb 2011-05-13 10:04:55 -07:00
scripts scripts/oe-buildenv-internal: Improve message when bitbake is missing 2011-05-18 12:42:26 +01:00
.gitignore Rename the remaining poky-* scripts to oe-* or runqemu-* 2011-04-21 00:29:31 +01:00
LICENSE LICENSE: Clarify the license recipe source code is under 2010-06-10 10:13:18 +01:00
README README: Update to reflect what Poky is today 2011-04-21 13:03:52 +01:00
README.hardware Rename poky-image-* -> core-image-* and task-poky-* -> task-core-* 2011-04-21 00:29:30 +01:00
oe-init-build-env Further cleanup of various poky references 2011-04-21 12:56:16 +01:00

README

Poky
====

Poky is an integration of various components to form a complete prepackaged
build system and development environment. It features support for building
customised embedded device style images. There are reference demo images
featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
cross-architecture application development using QEMU emulation and a
standalone toolchain and SDK with 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 layers which extend the systems capabilities in a modular way.

As an integration layer Poky consists of several upstream projects such as 
BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information 
e.g. for the hardware support. Poky is in turn a component of the Yocto Project.

The Yocto Project has extensive documentation about the system including a 
reference manual which can be found at:
    http://yoctoproject.org/community/documentation

For information about OpenEmbedded see their website:
    http://www.openembedded.org/