mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: Alexander Dahl <post@lespocky.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] lldpd: bump version to 0.7.19
Date: Mon, 9 Nov 2015 10:58:12 +0100	[thread overview]
Message-ID: <20151109095812.GA809@pqgruber.com> (raw)
In-Reply-To: <84f6c683fb34bc362d65652f3389a228@localhost>

Hi Alexander,

On Mon, Nov 09, 2015 at 08:46:09AM +0100, Alexander Dahl wrote:
> Hei hei, 
> 
> Am 2015-11-07 18:26, schrieb Clemens Gruber:
> > -LLDPD_VERSION	:= 0.7.6
> > -LLDPD_MD5		:= dbd90a68b91448dcb94a4a77c5d8ef65
> > +LLDPD_VERSION	:= 0.7.19
> > +LLDPD_MD5		:= 4e924420e00ccd5dc289506f43221820
> 
> I'm afraid it's not that simple. Some configure options changed and some
> where added. This should be adressed in rules/lldpd.make and maybe in
> rules/lldpd.in as well. I attach a diff of the output of ./configure
> --help to this mail.
> 
> Another point is to check the new pid file handling. There's a new
> option --with-lldpd-pid-file in the configure output which should be
> checked against projectroot/etc/init.d/lldpd which is the startup script
> for bbinit.

This works out of the box. It uses /var/run/lldpd.pid by default.

> 
> The new possibility to link against json-c should be checked. There
> seems to be some new support for systemd. The with-privsep options
> should also be checked, there were some upstream changes in lldpd 0.7.8.

In v2, I added an option to enable the JSON output format (but only with json-c
as we do not have Jansson in ptxdist)

> 
> Maybe the https://github.com/vincentbernat/lldpd/blob/branch-0.7/NEWS
> could also be helpful.

Yes, I updated the minimum kernel version in the oldies option and added an
option for custom TLVs.

> 
> I would be happy if you could have a look into this, I'm also interested
> in an updated package, but didn't have time to investigate this further
> yet. ;-)

Privilege separation options are OK.
I did not enable seccomp because they do not use the syscall directly but
through libseccomp which is not in ptxdist. Also, it is not yet enabled by
default by the developer, so I think this can wait a little bit.

lldpd works on my system with busybox init.
I do not have a systemd box with ptxdist however. (It should detect the correct
location via pkg-config, right?)
Would be great if you could give the v2 patch a try, especially wrt systemd.

> 
> Greets
> Alex
> 
> -- 
> »With the first link, the chain is forged. The first speech censured,
> the first thought forbidden, the first freedom denied, chains us all
> irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
> *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-11-09  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 17:26 Clemens Gruber
2015-11-09  7:46 ` Alexander Dahl
2015-11-09  9:58   ` Clemens Gruber [this message]
2015-11-16 13:11     ` Clemens Gruber
2015-11-16 13:26       ` Alexander Dahl
2015-11-22 17:46         ` Clemens Gruber

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=20151109095812.GA809@pqgruber.com \
    --to=clemens.gruber@pqgruber.com \
    --cc=post@lespocky.de \
    --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