From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: add option to install ntp startup script
Date: Tue, 19 May 2015 10:24:10 +0200 [thread overview]
Message-ID: <555AF32A.60403@je-eigen-domein.nl> (raw)
In-Reply-To: <CAJ3iQcrTBMLEU8zeQYFXmP9ugvrLyD4J1aKfcUmUyJhKtOwB5A@mail.gmail.com>
Hi,
On 05/19/2015 05:08 AM, Gergely Imreh wrote:
> On 19 May 2015 at 03:58, Floris Bos <bos@je-eigen-domein.nl> wrote:
>> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
>> ---
>> package/busybox/Config.in | 6 ++++++
>> package/busybox/S49ntp | 34 ++++++++++++++++++++++++++++++++++
>> package/busybox/busybox.mk | 15 +++++++++++++++
>> package/busybox/ntp.conf | 2 ++
>> 4 files changed, 57 insertions(+)
>> create mode 100644 package/busybox/S49ntp
>> create mode 100644 package/busybox/ntp.conf
>>
>> diff --git a/package/busybox/Config.in b/package/busybox/Config.in
>> index b4f949f..0b74536 100644
>> --- a/package/busybox/Config.in
>> +++ b/package/busybox/Config.in
>> @@ -26,6 +26,12 @@ config BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
>> Show packages in menuconfig that are potentially also provided
>> by busybox.
>>
>> +config BR2_PACKAGE_BUSYBOX_NTP
>> + bool "Install the ntp startup script"
>> + help
>> + Install the ntp daemon startup script, that by default operates in
>> + client-only mode and synchronizes the system time with pool.ntp.org.
>> +
> Should this section be wrapped in an "if BR2_PACKAGE_NTP" / "endif"
> block? I guess there's no point showing the option if the NTP package
> is not selected.
>
> On a higher level, wouldn't it make sense to add this option to the
> NTP package itself, instead of busybox?
Note that this patch is about enabling the ntpd applet included in
Busybox, as a light-weight alternative to the full blown standalone NTP
package.
So no, it does not depend on BR2_PACKAGE_NTP.
BR2_PACKAGE_NTP and BR2_PACKAGE_OPENNTPD already have startup scripts of
their own.
But if you just want your device to retrieve the time because it lacks a
RTC (as opposed to playing server and providing the time to others),
installing those is overkill in my opinion.
> Especially because NTP is not the only ntp client supported by busybox, there's also chrony.
>Ideally that should also have an option for default setup and startup
script, just like the this patch aims to do for ntp.
Chrony is a standalone buildroot package, and not an applet provided by
busybox.
Doesn't it install a startup script implicity, if you select it in
buildroot?
>> +++ b/package/busybox/ntp.conf
>> @@ -0,0 +1,2 @@
>> +server 0.pool.ntp.org
>> +server 1.pool.ntp.org
> Isn't 2 servers too few in general? If there's a default conf, maybe
> use the same setup as the NTP Pool project page's simple setup at
> http://www.pool.ntp.org/en/use.html
It is the same we currently have for the standalone ntp package in
package/ntp/ntpd.etc.conf
Am open to change that, but I do think the standalone ntp config should
be changed too then.
--
Yours sincerely,
Floris Bos
next prev parent reply other threads:[~2015-05-19 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 19:58 [Buildroot] [PATCH] busybox: add option to install ntp startup script Floris Bos
2015-05-19 3:08 ` Gergely Imreh
2015-05-19 4:23 ` Gergely Imreh
2015-05-19 5:00 ` Baruch Siach
2015-05-19 8:24 ` Floris Bos [this message]
2015-05-20 2:48 ` Gergely Imreh
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=555AF32A.60403@je-eigen-domein.nl \
--to=bos@je-eigen-domein.nl \
--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