public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Gerhard Mack <gmack@innerfire.net>
Cc: David Lloyd <lloy0076@adam.com.au>,
	Justin Cormack <justin@street-vision.com>,
	linux-kernel@vger.kernel.org
Subject: Re: OT: Which Gigabit ethernet card?
Date: Wed, 25 Dec 2002 23:23:25 +0800	[thread overview]
Message-ID: <3E09CD6D.5020509@metaparadigm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0212250847230.18327-100000@innerfire.net>

On 12/25/02 21:50, Gerhard Mack wrote:
> On Wed, 25 Dec 2002, David Lloyd wrote:
> 
> 
>>Thank Goodness -- I've worked in places where they INSIST on making
>>crossover cables the same length and colour as normal cables. Then you
>>go, "huh? samba/the network/the kernel" is not working until someone
>>with better eyesight finds the problem.
>>
>>*death to crossover cables*
> 
> 
> That's pretty lame of them but shouldn't the ethernet link light be a good
> indicator that it's a cable problem?
> 
> fix: Dud cable->trash bin "oops was that a crossover? it wasn't marked as
> one."

Or take a two second look holding both RJ45 connectors next to each other
connector side up. If the colours are in the same order on both - it's
straight through. First and third are swapped - it's a crossover cable.

Once you learn this simple trick, you'll never have a problem again -
just get used to spending the extra two seconds before using the cable.

~mc


  reply	other threads:[~2002-12-25 15:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 13:45 OT: Which Gigabit ethernet card? Jurgen Kramer
2002-12-20 18:29 ` Ben Greear
2002-12-20 18:48 ` Bill Davidsen
2002-12-20 20:15   ` Wes Felter
2002-12-20 21:06     ` Joel Jaeggli
2002-12-20 21:08 ` Dax Kelson
2002-12-20 21:13 ` Eric Weigle
2002-12-21 12:44 ` Jurgen Kramer
2002-12-21 17:28   ` Sampson Fung
2002-12-23 12:17     ` Roy Sigurd Karlsbakk
2002-12-23 14:50       ` nick
2002-12-23 17:23         ` Eric Weigle
2002-12-23 17:28         ` Justin Cormack
2002-12-23 17:35           ` Jeff Garzik
2002-12-24  1:43             ` nick
2002-12-23 18:57           ` Daniel Egger
2002-12-25  6:03           ` David Lloyd
2002-12-25 13:50             ` Gerhard Mack
2002-12-25 15:23               ` Michael Clark [this message]
2002-12-25 17:23                 ` Jeff Garzik
2002-12-25 17:33                   ` Sean Neakums
2002-12-27  9:45                     ` daveman
2002-12-27  9:59                       ` John Bradford
     [not found] <fa.io6mq9v.11gou0n@ifi.uio.no>
2002-12-31  2:22 ` Bill Davidsen
2002-12-31  8:47   ` Filip djMedrzec Zyzniewski
2003-01-09 16:15     ` Bill Davidsen
2003-01-09 16:39       ` John Bradford

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=3E09CD6D.5020509@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=gmack@innerfire.net \
    --cc=justin@street-vision.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lloy0076@adam.com.au \
    /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