Here's how I like to deal with questions like this:
Will knowing the answer ever help you troubleshoot a problem?
"Oh, geez, I know what I've been doing wrong - I've been calling it a *port*
when it's really an *interface*!! I'll have it up in a few seconds, sorry
about that...."
;-)
-----Original Message-----
From: Peter Van Oene [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 2:56 PM
To: [EMAIL PROTECTED]
Subject: Re: THEY ARE NOT PORTS THEY ARE INTERFACES! [7:16843]
What would you consider interface s0.100 to be? Seems pretty logical to me.
I think you'll find that both the terms interface and port have context
sensitive meanings. If you've ever configured a 3Com netbuilder you'll be
even more convinced of this. I missed the rest of the thread, but I don't
see how using a term one way or another makes one a dork even though I
believe strongly in technical accuracy. Nor do I see how inferring that
people are spineless dorks contributes positively to the learning process.
Pete
*********** REPLY SEPARATOR ***********
On 8/22/2001 at 1:08 PM Peter Slow wrote:
>an INTERFACE a thing, such as an ethernet or loopback interface.
>a port is a logical device, and NO a loopback does not count.
>i meant like tcp ports, usp ports, and the like.
>
>Stop being d0rks and copying everyone else who does it
>wrong, and dont be afraid to tell people to speak correctly!
>
>c3660#conf t
>Enter configuration commands, one per line. End with CNTL/Z.
>c3660(config)#port fastethernet 0/0
> ^
>% Invalid input detected at '^' marker.
>
>c3660(config)#interface fastethernet 0/0
>c3660(config-if)#^Z
>c3660#SEE!?
>% Unrecognized command
>c3660#SEE!
>-humboldt
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=16872&t=16843
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]