From: Eric Paris <eparis@redhat.com>
To: Florin Malita <fmalita@gmail.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
nsxfreddy@gmail.com, akpm@osdl.org, davem@davemloft.net,
ctindel@users.sourceforge.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
Subject: Re: [Bonding-devel] Re: [PATCH] channel bonding: add support for device-indexed parameters
Date: Tue, 27 Sep 2005 09:54:29 -0400 [thread overview]
Message-ID: <1127829269.4560.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20050927094055.7953a832.fmalita@gmail.com>
It dos work with RHEL3. In modules.conf you just need
alias bond0 bonding
options bond0 -o bonding0
alias bond1 bonding
options bond1 -o bonding1
You can add your mode and mii_mon and such on the options lines. It
does work I've used it.
-Eric
On Tue, 2005-09-27 at 09:40 -0400, Florin Malita wrote:
> On Tue, 27 Sep 2005 00:11:56 -0700
> Jay Vosburgh <fubar@us.ibm.com> wrote:
> >
> > Florin Malita <fmalita@gmail.com> wrote:
> > [...]
> > >How can you load a module multiple times on _any_ distro?
> >
> > modprobe -obond0 bonding mode=your-favorite-mode
> > modprobe -obond1 bonding mode=some-other-mode
> >
> > and so on. This is in the modprobe man page, and is described
> > in the bonding documentation (found in the kernel documentation or at
> > http://sourceforge.net/projects/bonding). It is admittedly somewhat
> > grotty, but it works.
>
> OK, I see this capability has been in module-init-tools since the 0.8
> days. Doesn't apply to any 2.4/modutils based system tough.
>
> >
> > >Not being able to set a (different) preferred
> > >interface/primary for each bond device makes it unacceptable for
> > >deployment in our environment.
> >
> > How are you configuring bonding? The current SuSE distros, for
> > example, will do the multiple module load stuff automatically in the
> > sysconfig scripts. This is described in the current bonding
> > documentation.
>
> Our systems are RHEL3 based so unfortunately the naming trick above
> doesn't work.
>
> But it does work on RHEL4 so admittedly, having this workaround
> available for recent distros removes the urgency for a fix.
>
> Thanks
> Florin
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.
> Download it for free - -and be entered to win a 42" plasma tv or your very
> own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Bonding-devel mailing list
> Bonding-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bonding-devel
next prev parent reply other threads:[~2005-09-27 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 4:04 [PATCH] channel bonding: add support for device-indexed parameters Florin Malita
2005-09-22 6:03 ` Jason R. Martin
2005-09-22 13:16 ` Florin Malita
2005-09-26 23:58 ` Jay Vosburgh
2005-09-27 5:24 ` Florin Malita
2005-09-27 7:11 ` Jay Vosburgh
2005-09-27 13:40 ` Florin Malita
2005-09-27 13:54 ` Eric Paris [this message]
2005-09-27 14:10 ` [Bonding-devel] " Florin Malita
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=1127829269.4560.4.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=akpm@osdl.org \
--cc=bonding-devel@lists.sourceforge.net \
--cc=ctindel@users.sourceforge.net \
--cc=davem@davemloft.net \
--cc=fmalita@gmail.com \
--cc=fubar@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsxfreddy@gmail.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;
as well as URLs for NNTP newsgroup(s).