All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: init-ifupdown: is this missing a RDEPEND to procps?
Date: Thu, 21 Nov 2013 09:09:25 -0700	[thread overview]
Message-ID: <528E3035.9040100@mlbassoc.com> (raw)
In-Reply-To: <528E2DDE.1080602@gmail.com>

On 2013-11-21 08:59, Hans Beckerus wrote:
> On 2013-11-20 4:15, Hans Beckérus wrote:
>> The /etc/init.d/networking script is using sysctl to grab some
>> parameters from /etc/sysctl.conf. This file does not exists unless
>> procps is also installed.
>> I can not see that init-ifupdown RDEPENDS procps. Should it not? Or is
>> there a reason for not having it like that?
> No one? Should I route this question to OE-core instead?

Probably since this recipe is in OE-core.

IMO, there should not be a dependency on procps since that's pretty
heavy and not really needed for smaller systems.  The single use
of /etc/sysctl.conf in the ifupdown script seems to be trying to make
sure local settings are applied before bringing up the network devices.
The script simply ignores the failure if the file is missing which is
OK, plus it does allow for local customization providing /etc/sysctl.conf
without the overhead of procps.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2013-11-21 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 15:15 init-ifupdown: is this missing a RDEPEND to procps? Hans Beckérus
2013-11-21 15:59 ` Hans Beckerus
2013-11-21 16:09   ` Gary Thomas [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=528E3035.9040100@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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 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.