From: Willy Tarreau <willy@w.ods.org>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org,
bonding-devel@lists.sourceforge.net,
ctindel@users.sourceforge.net, fubar@us.ibm.com, akpm@osdl.org
Subject: Re: [PATCH] fix ifenslave to not fail on lack of IP information
Date: Mon, 7 Nov 2005 07:23:25 +0100 [thread overview]
Message-ID: <20051107062325.GE11266@alpha.home.local> (raw)
In-Reply-To: <20051104165434.GB17181@hmsreliant.homelinux.net>
Hi,
On Fri, Nov 04, 2005 at 11:54:34AM -0500, Neil Horman wrote:
> The current version of ifenslave fails to attach slave interfaces to a bond if
> the masters doesn't have appropriate IP information. While its common for
> bonded interface to have IP information its not required (bond as part of a
> bridge for instance). This patch modifies ifenslave to not fail if IP
> information is not available in the master at the time of enslaving.
>
> Regards
> Neil
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
>
>
> ifenslave.c | 10 ++++------
> 1 files changed, 4 insertions(+), 6 deletions(-)
>
>
> diff --git a/Documentation/networking/ifenslave.c b/Documentation/networking/ifenslave.c
> --- a/Documentation/networking/ifenslave.c
> +++ b/Documentation/networking/ifenslave.c
(...)
I find it annoying that ifenslave is still hosted by the kernel. I made
this mistake years ago because it was not hosted anywhere and I needed
to make changes available somewhere, but it should move to somewhere
else, either as a standalone package on sf.net, or added to an existing
package such as ifconfig, or better merged with it. I even think that
if ifconfig included all ifenslave, vconfig, ethtool and brctl functions,
it wouldn't be abandonned as it is now, but this is another problem.
Regards,
Willy
next prev parent reply other threads:[~2005-11-07 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 16:54 Neil Horman
2005-11-07 6:23 ` Willy Tarreau [this message]
2005-11-11 4:20 ` Rob Landley
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=20051107062325.GE11266@alpha.home.local \
--to=willy@w.ods.org \
--cc=akpm@osdl.org \
--cc=bonding-devel@lists.sourceforge.net \
--cc=ctindel@users.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®