All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: guidelines for upstart in oe?
Date: Wed, 14 Sep 2011 17:31:06 +0200	[thread overview]
Message-ID: <4E70C8BA.9030901@dresearch-fe.de> (raw)

If i remember right there are some first experiments with using upstart as an sysvinit replacement in some oe based distros.

Do some guidelines or suggestions exist to make an application recipes upstart ready?

Nowadays a recipe for a common service contains INITSCRIPT_NAME & Co and installs an init script for sysvinit.

How should such a recipe be modified to be able to install the application in a native upstart image (without sysvinit compatible runlevels)?

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058



             reply	other threads:[~2011-09-14 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14 15:31 Steffen Sledz [this message]
2011-09-16 15:29 ` guidelines for upstart in oe? Steffen Sledz
2011-09-16 15:32   ` Phil Blundell
2011-09-16 16:15     ` Steffen Sledz
2011-09-16 20:33       ` Steffen Sledz
2011-09-19  8:06       ` Anders Darander
2011-09-19  9:11         ` Steffen Sledz
2011-09-19  9:12         ` Systemd sysv compat mode, was: " Koen Kooi
2011-09-17  6:24     ` Steffen Sledz
2011-09-19  8:34       ` Phil Blundell
2011-09-16 15:35   ` Koen Kooi

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=4E70C8BA.9030901@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.