[Tfug] Yet another poser

[Bexley Hall]

--- Rich <r-lists at studiosprocket.com> wrote:

> On Sep 14, 2007, at 12:23 pm, Bexley Hall wrote:
> 
> > So, in as much as is possible, I have tried to
> > rid myself of this problem by "picking" what I
> > think is an appropriate "standard" cable and
> > then building "widgets" to append to said
> > cable to modify it's *overall* character.
> I found a site a while ago where a sysadmin listed 
> the contents of  
> his (custom-built) cable kit. It was something like
> this:
> 
>   - standard T568B to T568B cable
>   - 1" crossover adapter m-f
>   - 1" loopback adapter m-f
>   - RJ45-db9 (Cisco)
>   - RJ45-db9 (RS232)  2 off
>   - db9-db25  2 off
>   - db9 and db25 gender benders, each 2 off
> and the clever bit:
>   - an *RJ45* null modem adapter - 1" long again

This would be good for a guy "administering systems".
In my case, I am usually talking to a specialized
device that isn't "run of the mill".

> I forget what the rest was. I'd've thrown in a
> USB-db9 adapter for fun and learning.

[snip]
 
> > Lastly, how are crossover cables typically
> > identified?  I had assumed I would just slap a
> > label on this (I label all of my widgets since
> > you "can't tell the players without a program"!)
> > saying "CROSSOVER"...?
> Yellow band at one or both ends.
> 
> Not a problem for me, because I label every cable at
> both ends with a  
> labelling machine. If it's not a crossover, it's
> labelled:
> 
> 1. hostname
> 2. (IP, unless dhcp)
> 3. MAC address
> 4. wall socket

Doesn't help me when said cables (widgets, in this
case  :> ) are being stored in a box!  :>
 
> > (Yeah, I think WAY too much about these little
> > details... :>  )
> Taha! You're not the only one!

Do nothing simply if a way can be found to make
it wonderful and complex!


      ____________________________________________________________________________________
Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, and more!
http://tv.yahoo.com/collections/3658