From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] add insserv to use LSB compliant init scripts and dynamically configure init order
Date: Mon, 6 Dec 2010 21:09:24 +0100 [thread overview]
Message-ID: <20101206210924.75330f3d@surf> (raw)
In-Reply-To: <96b265c099c9a9d7673ed6061aa562878ac45be0.1291587953.git.smiley73@users.sourceforge.net>
Hello,
On Sun, 5 Dec 2010 16:26:19 -0600
heiko at zuerker.org wrote:
> +config BR2_PACKAGE_INSSERV
> + bool "insserv"
> + help
> + This small package provides a tool for process controlling
> + in System V boot scripts.
> + It works for LSB compliant init scripts.
> + http://wiki.debian.org/LSBInitScripts
Just curious, how do you use this in the context of Buildroot ?
By default, Buildroot uses Busybox init, which isn't SysV compliant (it
doesn't support runlevels). And how would this interact with the
Buildroot build process ?
> +#INSSERV_DEPENDENCIES=zlib
> +#HOST_INSSERV_DEPENDENCIES=host-zlib
Useful ? Comments ?
> +define INSSERV_CONFIGURE_CMDS
> + echo "#!/bin/sh" > $(@D)/tests/common
> + echo "exit 0" >> $(@D)/tests/common
> + chmod +x $(@D)/tests/common
> +endef
> +
> +define HOST_INSSERV_CONFIGURE_CMDS
> + echo "#!/bin/sh" > $(@D)/tests/common
> + echo "exit 0" >> $(@D)/tests/common
> + chmod +x $(@D)/tests/common
> +endef
Those sound strange. Maybe a short comment above would clarify a bit.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-06 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 22:26 [Buildroot] [PATCH] add insserv to use LSB compliant init scripts and dynamically configure init order heiko at zuerker.org
2010-12-06 20:09 ` Thomas Petazzoni [this message]
2010-12-06 20:29 ` Heiko Zuerker
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=20101206210924.75330f3d@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.