On Fri, Jan 9, 2015 at 1:15 AM, [email protected]
<[email protected]> wrote:
> Maybe we can check the AS_FASTPATH option enablement in
> ${STAGING_KERNEL_DIR}/.config.
> if [ "`grep "CONFIG_AS_FAST=y" ${STAGING_KERNEL_DIR}/.config`" ]; then
> for keyword in
> net.ipv4.conf.default.rp_filter \
> net.ipv4.conf.all.rp_filter \
> do
> sed -i 's,'"$keyword"'=.*,'"$keyword"'=0,'
> ${D}${sysconfdir}/sysctl.conf
> done
> fi
This should be done in a init script. This is a runtime configuration
and there is no reason to diverge procps package for it.
I see some possible ways to address it:
* make a qoriq-asfastpath-init recipe
This would check the kernel, at runtime, and see if it is enabled. In
case it does, it uses sysctl to set the values accordingly.
* add a do_install_append *in kernel* which makes a
${sysconfdir}/sysctl.conf.d/99-as-fast.conf
This makes this fine and install it when the kernel has it enabled.
So in no means changing procps seems the best alternative. It is
related *to the kernel* and may - and likely will - vary from one
machine to another.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
