From: Alejandro del Castillo <alejandro.delcastillo@ni.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Vladimir Zapolskiy <vz@mleia.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package_ipk: allow to specify OPKG_ARGS in local.conf
Date: Wed, 2 Dec 2015 17:16:30 -0600 [thread overview]
Message-ID: <565F7BCE.2070203@ni.com> (raw)
In-Reply-To: <CAJTo0Lbzvbwc34aXEMgfUJGnANMzaB+4ecM1=sa=8KONeTJukw@mail.gmail.com>
On 12/02/2015 03:48 AM, Burton, Ross wrote:
>
> On 2 December 2015 at 04:48, Vladimir Zapolskiy <vz@mleia.com
> <mailto:vz@mleia.com>> wrote:
>
> sh: /tmp/opkg-5jPLag/run-postinsts-UsUtaI/preinst: /bin/sh: bad
> interpreter: Permission denied
>
>
> Whilst the patch is fine, this is worrying as noexec /tmp shouldn't break opkg.
> Maybe opkg should be changed to use something in /var for the scripts?
Could you expand on why it's better to use /var instead of /tmp as the default
sandbox location for opkg? I believe dpkg uses /var/lib/ and would like to
understand why that's better (to change opkg, if it makes sense)
--
Cheers,
Alejandro
next prev parent reply other threads:[~2015-12-02 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 4:48 [PATCH] package_ipk: allow to specify OPKG_ARGS in local.conf Vladimir Zapolskiy
2015-12-02 9:48 ` Burton, Ross
2015-12-02 23:16 ` Alejandro del Castillo [this message]
2015-12-02 23:19 ` Burton, Ross
2015-12-03 1:03 ` Alejandro del Castillo
2015-12-03 5:57 ` Vladimir Zapolskiy
-- strict thread matches above, loose matches on Subject: below --
2015-12-02 4:41 Vladimir Zapolskiy
2015-12-02 4:50 ` Vladimir Zapolskiy
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=565F7BCE.2070203@ni.com \
--to=alejandro.delcastillo@ni.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=vz@mleia.com \
/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.