From: "Benoît Thébaudeau" <benoit@wsystem.com>
To: buildroot@busybox.net
Subject: [Buildroot] package/dhcp/S80dhcp-*: possible bug
Date: Thu, 20 Aug 2015 00:31:21 +0200 [thread overview]
Message-ID: <55D503B9.6030005@wsystem.com> (raw)
Hi all,
The S80dhcp-* scripts use string variables like INTERFACES that are left empty.
Because of that, the corresponding services are not started.
Previously, there were configuration files to initialize these variables, but
they have been removed by the commit 07064c0978b78356bf74408c216f524881df3362.
Is it a bug, or are these scripts supposed to just be templates (requiring a
root FS overlay to fix them) and not the actual scripts?
If it is a bug, what is the preferred way of fixing it? With a configuration
file that would be sourced by these scripts like before, or with Config.in
string options that would fill these scripts, or with something else?
Best regards,
Beno?t
next reply other threads:[~2015-08-19 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 22:31 Benoît Thébaudeau [this message]
2015-08-20 20:55 ` [Buildroot] [PATCH 1/3] package/dhcp: fix SysV init scripts option passing Benoît Thébaudeau
2015-08-20 20:55 ` [Buildroot] [PATCH 2/3] package/dhcp/S80dhcp-server: support extra options Benoît Thébaudeau
2015-08-20 20:55 ` [Buildroot] [PATCH 3/3] package/dhcp/S80dhcp-server: allow empty INTERFACES Benoît Thébaudeau
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=55D503B9.6030005@wsystem.com \
--to=benoit@wsystem.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