From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox: Add inetd related files
Date: Fri, 27 Jul 2012 15:59:57 -0500 [thread overview]
Message-ID: <5013014D.4040404@windriver.com> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C27A73D@DFLE30.ent.ti.com>
On 7/27/12 3:26 PM, Cooper Jr., Franklin wrote:
> The section you mentioned is within the file inetd which I am adding to the SRC_URI list in the busybox_1.19.4.bb file. The variable ${sbindir} won't be expanded.
>
> -----Original Message-----
> From: Phil Blundell [mailto:philb@gnu.org]
> Sent: Friday, July 27, 2012 3:02 PM
> To: Patches and discussions about the oe-core layer
> Cc: Cooper Jr., Franklin
> Subject: Re: [OE-core] [PATCH] busybox: Add inetd related files
>
> On Fri, 2012-07-27 at 14:52 -0500, Franklin S Cooper Jr wrote:
>> +if ! [ -x /usr/sbin/inetd ]; then
>> + exit 0
>> +fi
>
> That should be ${sbindir}.
Inline sed of the initscript may be the easiest way to do this.
You need to expand it, you can not rely on /usr/sbin/inetd, as OE-Core expressly
permits people to change the bindir and sbindir locations. (Generally if
someone does, they change from /usr/sbin to /sbin, and /usr/bin to /bin...)
--Mark
> p.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2012-07-27 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 19:52 [PATCH] busybox: Add inetd related files Franklin S Cooper Jr
2012-07-27 20:01 ` Phil Blundell
2012-07-27 20:26 ` Cooper Jr., Franklin
2012-07-27 20:43 ` Phil Blundell
2012-07-27 22:10 ` Cooper Jr., Franklin
2012-07-27 20:59 ` Mark Hatle [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=5013014D.4040404@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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