From: Jay Vosburgh <fubar@us.ibm.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] bonding: update some distro-specific documentation
Date: Wed, 12 Sep 2007 11:47:36 -0700 [thread overview]
Message-ID: <1085.1189622856@death> (raw)
In-Reply-To: <20070912181839.GD3754@gospo.rdu.redhat.com>
Andy Gospodarek <andy@greyhouse.net> wrote:
>I could do that, or we could just take this as-is and get initscripts
>fixed up to account for this. Does that seem reasonable?
Changing initscripts is fine, too, but is there then going to be
some (perhaps small) installed base for which the documentation will be
incorrect?
>I'd rather go that route, and I've even got a patch that *seems* to work
>already:
>
>--- initscripts-8.45.17.EL/sysconfig/network-scripts/ifup-eth.orig
>+++ initscripts-8.45.17.EL/sysconfig/network-scripts/ifup-eth
>@@ -125,7 +125,16 @@ if [ "$ISALIAS" = no ] && is_bonding_dev
> for arg in $BONDING_OPTS ; do
> key=${arg%%=*};
> value=${arg##*=};
>- echo $value > /sys/class/net/${DEVICE}/bonding/$key
>+ OLDIFS=$IFS;
>+ IFS=',';
>+ if [ "${key}" = "arp_ip_target" ]; then
>+ for arp_ip in $value; do
>+ echo +$arp_ip > /sys/class/net/${DEVICE}/bonding/$key
>+ done
>+ else
>+ echo $value > /sys/class/net/${DEVICE}/bonding/$key
>+ fi
>+ IFS=$OLDIFS;
> done
>
> /sbin/ip link set dev ${DEVICE} up
That looks like it should do the right thing, although I didn't
actually try it. The other bonding sysfs thingies that use the "+" type
of syntax don't appear in BONDING_OPTS.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2007-09-12 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 21:24 [PATCH] bonding: update some distro-specific documentation Andy Gospodarek
2007-09-07 18:27 ` Jay Vosburgh
2007-09-12 18:18 ` Andy Gospodarek
2007-09-12 18:47 ` Jay Vosburgh [this message]
2007-09-12 19:40 ` Andy Gospodarek
2007-09-17 21:46 ` Andy Gospodarek
2007-09-17 21:53 ` Andy Gospodarek
2007-09-17 23:00 ` Andy Gospodarek
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=1085.1189622856@death \
--to=fubar@us.ibm.com \
--cc=andy@greyhouse.net \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).