All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/leafnode2: fix news user check
Date: Sat, 27 Dec 2014 21:52:14 +0100	[thread overview]
Message-ID: <549F1BFE.3050106@openwide.fr> (raw)
In-Reply-To: <20141227171318.42ba61a4@free-electrons.com>

Le 27/12/2014 17:13, Thomas Petazzoni a ?crit :
> Dear Romain Naour,
>
> On Fri, 26 Dec 2014 18:38:11 +0100, Romain Naour wrote:
>> --enable-runas-user use 'news' as default but the configure stop
>> if news doesn't exist on the build host.
>> Use 'root' while cross-compiling
>>
>> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
>> ---
>>  package/leafnode2/leafnode2.mk | 6 +++++-
>>  1 file changed, 5 insertions(+), 1 deletion(-)
> Applied, thanks. Here, leafnode2 does not start properly at boot time,
> it asks for a fully qualified host name in /etc/hosts. It would be good
> to add a default config file + init script to make leafnode2 work at
> least somewhat out of the box.
>
> Thanks!
>
> Thomas
Honestly, I haven't runtime tested leadnode2.
I just checked why the build has stopped during a random build.

The configure script run the command: id -u news:
a=`$ID -u $RUNAS_USER`
if test -z "$a" ; then
    as_fn_error $? "user $RUNAS_USER does not exist. Please add this user before building leafnode.
                  Most systems have man adduser or man useradd to tell you how to do this." "$LINENO" 5
else
...

This test is used to print a warning because it expect a native
build:
WARNING: user $RUNAS_USER cannot be used to run leafnode for security reasons.
Be sure to configure run_as_user to an unprivileged user, else leafnode will not run."

I'm adding Bernd to cc since it use leadnode2.

Best regards,
Romain

      reply	other threads:[~2014-12-27 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 17:38 [Buildroot] [PATCH] package/leafnode2: fix news user check Romain Naour
2014-12-27 16:13 ` Thomas Petazzoni
2014-12-27 20:52   ` Romain Naour [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=549F1BFE.3050106@openwide.fr \
    --to=romain.naour@openwide.fr \
    --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.