mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <randy.dunlap@verizon.net>
To: davem@redhat.com, linux-kernel@vger.kernel.org
Cc: ahu@ds9a.nl
Subject: Re: Silly advise in bridge Configure help
Date: Wed, 06 Nov 2002 20:20:58 -0800	[thread overview]
Message-ID: <3DC9EA2A.142559AA@verizon.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]

Bert Hubert said a few days back:
| In the Configure HELP of Ethernet bridging:
|
| "Note that if your box acts as a bridge, it probably contains 
| several Ethernet devices, but the kernel is not able to recognize
| more than one at
| boot time without help; for details read the Ethernet-HOWTO, 
| available from in <http://www.linuxdoc.org/docs.html#howto>."
|
| This is extremely bogus these days and prone to confuse people. 
| I suggest this warning is removed.

Sounds good, so here's the patch to 2.5.46 Kconfig to do that
if you want it.

~Randy

[-- Attachment #2: bridge_help-2.5.46.patch --]
[-- Type: text/plain, Size: 692 bytes --]

--- ./net/Kconfig%fixhelp	Mon Nov  4 14:30:05 2002
+++ ./net/Kconfig	Wed Nov  6 20:07:13 2002
@@ -382,11 +382,6 @@
 	  for location. Please read the Bridge mini-HOWTO for more
 	  information.
 
-	  Note that if your box acts as a bridge, it probably contains several
-	  Ethernet devices, but the kernel is not able to recognize more than
-	  one at boot time without help; for details read the Ethernet-HOWTO,
-	  available from in <http://www.linuxdoc.org/docs.html#howto>.
-
 	  If you want to compile this code as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module

             reply	other threads:[~2002-11-07  5:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07  4:20 Randy.Dunlap [this message]
2002-11-07  9:15 ` David S. Miller
2002-11-07  9:18   ` bert hubert
2002-11-07  9:49     ` David S. Miller
2002-11-07 10:39       ` bert hubert
2002-11-07 10:41         ` bert hubert
2002-11-07 10:52         ` David S. Miller
2002-11-07 11:16           ` bert hubert
2002-11-07 13:02           ` IPSEC FIRST LIGHT! (by non-kernel developer :-)) bert hubert
2002-11-07 13:14             ` James Morris
2002-11-07 13:21             ` David S. Miller
2002-11-07 14:12               ` bert hubert
2002-11-07 15:18                 ` David S. Miller
2002-11-07 15:33                   ` bert hubert
2002-11-07 17:49                   ` kuznet
2002-11-07 18:41                     ` bert hubert
2002-11-07 19:05                       ` kuznet
2002-11-08  1:59             ` [LARTC] " Mike Diehl
2002-11-08  9:41               ` [documentation] " bert hubert
2002-11-08  9:52                 ` David S. Miller
2002-11-08 11:15                   ` bert hubert
2002-11-08 11:27                     ` bert hubert
2002-11-08 12:25                       ` bert hubert
2002-11-08 13:31                         ` kuznet
2002-11-08 13:44                           ` bert hubert
  -- strict thread matches above, loose matches on Subject: below --
2002-10-28 13:35 Silly advise in bridge Configure help bert hubert

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=3DC9EA2A.142559AA@verizon.net \
    --to=randy.dunlap@verizon.net \
    --cc=ahu@ds9a.nl \
    --cc=davem@redhat.com \
    --cc=linux-kernel@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

Powered by JetHome