From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gpsd: make init script optional
Date: Tue, 18 Jun 2013 09:07:03 +0200 [thread overview]
Message-ID: <20130618090703.05d44c80@skate> (raw)
In-Reply-To: <51BFFD16.7030009@mind.be>
Dear Arnout Vandecappelle,
On Tue, 18 Jun 2013 08:24:22 +0200, Arnout Vandecappelle wrote:
> There are just a few daemons that you'd want to run from hotplug, most
> of them would still run from init.d.
>
> But I really would like a better way to manage the services you want to
> run in init.d, and especially their order. I can't come up with a good
> solution, though, so I'm not actively complaining :-)
I believe it's typically the kind of customization that is left to the
user, through a post-build script. Buildroot provides a relatively sane
default installation, and the user has to further tweak it if needed. I
don't think we should make Buildroot more complex to allow directly in
the Buildroot configuration this kind of very specific customization.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-06-18 7:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 11:34 [Buildroot] [PATCH] gpsd: make init script optional spdawson at gmail.com
2013-06-16 12:34 ` Maxime Ripard
2013-06-16 13:09 ` Yann E. MORIN
2013-06-16 15:59 ` Simon Dawson
2013-06-16 17:37 ` Peter Korsgaard
2013-06-16 18:16 ` Simon Dawson
2013-06-16 18:30 ` Maxime Ripard
2013-06-18 6:24 ` Arnout Vandecappelle
2013-06-18 7:07 ` Thomas Petazzoni [this message]
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=20130618090703.05d44c80@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox