From: Constantine Gavrilov <const-g@xpert.com>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: willy tarreau <wtarreau@yahoo.fr>,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18pre21
Date: Fri, 10 Nov 2000 11:57:45 +0200 [thread overview]
Message-ID: <3A0BC699.791064BE@xpert.com> (raw)
In-Reply-To: <20001110092846.29847.qmail@web1102.mail.yahoo.com> <20001110114425.E13151@mea-ext.zmailer.org>
Matti Aarnio wrote:
>
> On Fri, Nov 10, 2000 at 10:28:46AM +0100, willy tarreau wrote:
>
> From the patch source:
>
> +CONFIG_BONDING
> + Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
> + Channels together. This is called 'Etherchannel' by Cisco,
> + 'Trunking' by Sun, and 'Bonding' in Linux.
>
> I think "bonding" is term used in one particular type
> of ISDN multilink calls.
>
> Cisco Trademark is EtherChannel -- there the capitalization
> is important. We could call it ETHERNETCHANNEL (and even
> "Etherchannel" or "ETHERCHANNEL") get away with it clean.
>
> ...
> > Regards,
> > Willy
>
> /Matti Aarnio
ISDN uses "channel bonding", not bonding. As for "Etherchannel", let us change
it to "EtherChannel" is this is how it is called.
--
----------------------------------------
Constantine Gavrilov
Unix System Administrator and Programmer
Xpert Integrated Systems
1 Shenkar St, Herzliya 46725, Israel
Phone: (972-8)-952-2361
Fax: (972-9)-952-2366
----------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-10 10:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 9:28 Linux 2.2.18pre21 willy tarreau
2000-11-10 9:44 ` Matti Aarnio
2000-11-10 9:57 ` Constantine Gavrilov [this message]
2000-11-10 10:14 ` Matti Aarnio
2000-11-10 10:22 ` Constantine Gavrilov
2000-11-10 10:51 ` Matti Aarnio
2000-11-10 19:11 ` Thomas Davis
2000-11-10 10:18 ` Constantine Gavrilov
2000-11-11 4:36 ` Intel's ANS Driver -vs- Bonding [was Re: Linux 2.2.18pre21] Dan Browning
2000-11-11 7:47 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2000-11-13 9:47 Linux 2.2.18pre21 willy tarreau
2000-11-13 7:00 willy tarreau
2000-11-10 11:21 willy tarreau
2000-11-10 10:49 willy tarreau
2000-11-10 10:40 willy tarreau
2000-11-10 3:07 Alan Cox
2000-11-10 3:44 ` David S. Miller
2000-11-10 11:35 ` Benjamin Herrenschmidt
2000-11-10 15:42 ` Tom Rini
2000-11-10 15:34 ` David S. Miller
2000-11-10 10:59 ` Arnaud S . Launay
2000-11-10 10:52 ` David S. Miller
2000-11-16 14:07 ` Matthias Andree
2000-11-16 16:16 ` Andrea Arcangeli
2000-11-16 19:52 ` jesse
2000-11-16 21:40 ` Alan Cox
2000-11-18 10:07 ` Rogier Wolff
2000-11-18 17:32 ` kuznet
2000-11-18 17:34 ` Rogier Wolff
2000-11-18 17:47 ` kuznet
2000-11-18 17:51 ` Rogier Wolff
2000-11-16 22:56 ` Matthias Andree
2000-11-17 6:30 ` Peter Samuelson
2000-11-17 6:40 ` H. Peter Anvin
2000-11-17 11:22 ` Peter Samuelson
2000-11-17 17:35 ` H. Peter Anvin
2000-11-17 11:34 ` Matthias Andree
2000-11-17 19:23 ` jesse
2000-11-18 20:44 ` Pavel Machek
2000-11-18 1:38 ` Nix
2000-11-21 4:19 ` Peter Samuelson
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=3A0BC699.791064BE@xpert.com \
--to=const-g@xpert.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=wtarreau@yahoo.fr \
/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