Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] rpi-userland: Fix vcfiled startup
Date: Wed, 6 Aug 2014 19:40:48 +0200 (CEST)	[thread overview]
Message-ID: <1234544963.1762589.1407346848783.JavaMail.zimbra@advansee.com> (raw)
In-Reply-To: <20140806173351.GF3891@free.fr>

Dear Yann E. MORIN,

On Wednesday, August 6, 2014 7:33:51 PM, Yann E. MORIN wrote:
> Benoit, All,
> 
> On 2014-08-06 15:39 +0200, Beno?t Th?baudeau spake thusly:
> > The VideoCore file server daemon startup script installed from this package
> > is
> > not compatible with BuildRoot (because of its naming and other Debian
> > dependencies), which prevented vcfiled from starting. Hence, prevent this
> > package from installing its vcfiled startup script, and install a vcfiled
> > SysV
> > init script suitable for BuildRoot.
> 
> I'm not sure I would be happy that the GPU is allowed uncontrolled
> access to the filesystem.
> 
> Please, make this an option, defaulting to 'n', so the user can
> willingly choose to install it or not.

Will do.

> Otherwise, see below...
> 
> > Signed-off-by: Beno?t Th?baudeau <benoit.thebaudeau@advansee.com>
> [--SNIP--]
> > diff --git a/package/rpi-userland/S94vcfiled
> > b/package/rpi-userland/S94vcfiled
> > new file mode 100755
> > index 0000000..25a0fcd
> > --- /dev/null
> > +++ b/package/rpi-userland/S94vcfiled
> > @@ -0,0 +1,47 @@
> > +#!/bin/sh
> > +
> > +NAME=vcfiled
> > +DESC="VideoCore file server daemon $NAME"
> > +DAEMON="/usr/sbin/$NAME"
> > +DAEMON_ARGS=""
> > +CFGFILE="/etc/default/$NAME"
> > +PIDFILE="/var/run/$NAME/$NAME"
> 
> Are you sure about the path to the PID file?
> What about:
>     PIDFILE="/var/run/$NAME.pid"

Yes, sure, this is the path used by vcfiled, which creates its PID file itself
rather than relying on start-stop-daemon -m for that.

> Othwerwise, looks good after a casual look. Ditto your previous patches,
> I'll try to find some time tonight to test it.

Thanks.

[...]

Regards,
Beno?t

  reply	other threads:[~2014-08-06 17:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 13:39 [Buildroot] [PATCH v2 1/3] rpi-userland: Bump version Benoît Thébaudeau
2014-08-06 13:39 ` [Buildroot] [PATCH v2 2/3] rpi-userland: .mk: Indent rules with tabs Benoît Thébaudeau
2014-08-06 17:25   ` Yann E. MORIN
2014-08-06 17:44   ` Thomas Petazzoni
2014-08-06 13:39 ` [Buildroot] [PATCH v2 3/3] rpi-userland: Fix vcfiled startup Benoît Thébaudeau
2014-08-06 17:33   ` Yann E. MORIN
2014-08-06 17:40     ` Benoît Thébaudeau [this message]
2014-08-06 19:56       ` Benoît Thébaudeau
2014-08-06 20:02         ` Yann E. MORIN
2014-08-06 17:25 ` [Buildroot] [PATCH v2 1/3] rpi-userland: Bump version Yann E. MORIN
2014-08-06 17:44 ` Thomas Petazzoni

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=1234544963.1762589.1407346848783.JavaMail.zimbra@advansee.com \
    --to=benoit.thebaudeau@advansee.com \
    --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