mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] ptxdist: BUSYBOX_NTPD blocks NTP
Date: Tue, 27 Jan 2015 19:23:39 +0100	[thread overview]
Message-ID: <CABDcavZzaiG5yEhqjVLj=aarFbiVp_spXpycXybVHP49r5Le2Q@mail.gmail.com> (raw)
In-Reply-To: <20150127075636.GD5565@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 2262 bytes --]

Hi Michael,

2015-01-27 8:56 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:

> On Mon, Jan 26, 2015 at 05:24:55PM +0100, Guillermo Rodriguez Garcia wrote:
> > Hello all,
> >
> > I am using the ntpd applet in busybox but also wanted to enable the
> ntpdate
> > program (yes I know use of ntpdate is not recommended in general but this
> > is for a very specific use case). However I see that ntpdate is part of
> the
> > "ntp" package and that the ntp package is blocked by BUSYBOX_NTPD. From
> > rules/ntp.in:
> >
> > menuconfig NTP
> >         tristate
> >         prompt "ntp                           "
> >         select OPENSSL          if NTP_CRYPTO
> >         select ROOTFS_VAR_CACHE if NTP_NTPD
> >         select LIBC_M
> >         select LIBC_RT
> >         select GCCLIBS_GCC_S
> >         select LIBMD
> >         depends on !BUSYBOX_NTPD || ALLYES
> >
> > [...]
> > config NTP_NTPDATE
> >         bool
> >         prompt "install ntpdate"
> >         depends on NTP
> >
> >
> > Obviously one would not want to run two ntp services at the same time,
> but
> > since busybox lacks an ntpdate command, there are cases where one would
> > want to use ntpdate from the NTP package while still using Busybox's ntpd
> > for everything else.
> >
> > My question is: Is there any reason why this wouldn't work? Was the
> > "depends on !BUSYBOX_NTPD" line added just to avoid the possibility of
> the
> > two ntp services running at the same time? Or is it there to guard from
> > other possible problems/issues?
>
> We usually add those lines only to prevent two packages from installing the
> same file. In this case we have the !BUSYBOX_NTPD check twice, once for the
> package and once for ntpd. This is clearly wrong. I don't see a reason why
> the check for the packages is needed and I don't remember why I added it. I
> suggest you remove the check (and the comment at the end of the file) and
> see what happens.
>

OK, tried just that: Removed the first (package-level) check, then selected
ntpdate from the ntp package and ntpd from busybox, rebuilt, tested on the
target, and I can confirm that everything works as expected. So I would say
that this check can be removed.

Thank you,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 3288 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2015-01-27 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 16:24 Guillermo Rodriguez Garcia
2015-01-27  7:56 ` Michael Olbrich
2015-01-27 18:23   ` Guillermo Rodriguez Garcia [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='CABDcavZzaiG5yEhqjVLj=aarFbiVp_spXpycXybVHP49r5Le2Q@mail.gmail.com' \
    --to=guille.rodriguez@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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