All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten ter Huurne <maarten@treewalker.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] vsftpd: Add build option to disable utmpx update code
Date: Mon, 06 Oct 2014 00:17:43 +0200	[thread overview]
Message-ID: <3812649.c7Zos5kZI3@hyperion> (raw)
In-Reply-To: <20141005234637.715fa4fb@free-electrons.com>

On Sunday 05 October 2014 23:46:37 Thomas Petazzoni wrote:
> Dear Maarten ter Huurne,
> 
> On Tue, 16 Sep 2014 15:17:30 +0200, Maarten ter Huurne wrote:
> > This was modeled after a similar option for Dropbear.
> > 
> > The utmpx code is automatically disabled when compiling with musl,
> > to avoid a build error due to WTMPX_FILE being undefined.
> 
> I find this explanation unclear: when you say "is", I assume it's
> *before* this patch is applied, but my understanding is that you mean
> *once* the patch is applied, correct?

Correct. It describes the behavior that this patch introduces in 
package/vsftpd/Config.in, for which there is no "before". But it is not 
clear that it applies only to that part of the changes: if you look at the 
vsftpd package as a whole, then it could indeed be misinterpreted as 
describing the previous situation. I will rephrase it if the other parts of 
the patch are accepted.

> > Note that
> > musl has an empty utmpx implementation, so no functionality is lost
> > by not calling it.
> > 
> > Signed-off-by: Maarten ter Huurne <maarten@treewalker.org>
> > ---
> > Note that previously the utmpx code was being built, so this patch
> > changes the default behavior. I think this is not a problem because
> > most systems would not have a valid utmpx file, but it might be worth
> > mentioning in the release notes.
> 
> Then instead of adding yet another new option, what about simply
> disabling the utmpx support in vsftpd.mk when the C library is musl,
> and keep it enabled otherwise?

That is possible, but systems running a libc with utmpx support might not 
actually be using it. This fragment exists in package/dropbear/Config.in:

config BR2_PACKAGE_DROPBEAR_WTMP
        bool "log dropbear access to wtmp"
        help
          Enable logging of dropbear access to wtmp. Notice that
          Buildroot does not generate wtmp by default.

Therefore I thought that having an option to disable the feature would be 
useful even if building it is possible.

> >  package/vsftpd/Config.in                        | 12 ++++++
> >  package/vsftpd/vsftpd-0001-utmpx-builddef.patch | 49
> >  +++++++++++++++++++++++++ package/vsftpd/vsftpd.mk                    
> >     |  8 ++++
> >  3 files changed, 69 insertions(+)
> >  create mode 100644 package/vsftpd/vsftpd-0001-utmpx-builddef.patch
> 
> Have you submitted vsftpd-0001-utmpx-builddef.patch upstream? It's kind
> of a feature patch, so something we _generally_ don't like to take in
> Buildroot.

Yes, I mailed it to the maintainer on 2014-09-16. I haven't had a reply yet.

Bye,
		Maarten

  reply	other threads:[~2014-10-05 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 13:17 [Buildroot] [PATCH] vsftpd: Add build option to disable utmpx update code Maarten ter Huurne
2014-10-05 21:46 ` Thomas Petazzoni
2014-10-05 22:17   ` Maarten ter Huurne [this message]
2014-10-11 17:25 ` Thomas Petazzoni
2014-10-12  7:32 ` Peter Korsgaard

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=3812649.c7Zos5kZI3@hyperion \
    --to=maarten@treewalker.org \
    --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.