From owner-freebsd-questions@FreeBSD.ORG Sun Aug 24 22:29:37 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 412D516A4BF for ; Sun, 24 Aug 2003 22:29:37 -0700 (PDT) Received: from adsl-63-198-56-213.dsl.snfc21.pacbell.net (adsl-63-198-56-213.dsl.snfc21.pacbell.net [63.198.56.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A00543FDF for ; Sun, 24 Aug 2003 22:29:36 -0700 (PDT) (envelope-from jd108@pacbell.net) Received: from pacbell.net (localhost [127.0.0.1]) ESMTP id h7P5TZqr008232; Sun, 24 Aug 2003 22:29:35 -0700 (PDT) (envelope-from jd108@pacbell.net) Message-ID: <3F499EBF.7020007@pacbell.net> Date: Sun, 24 Aug 2003 22:29:35 -0700 From: "Joseph I. Davida" User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Stevens References: <3E2C2ADF-D6AF-11D7-A2E0-000A959CEE6A@pursued-with.net> In-Reply-To: <3E2C2ADF-D6AF-11D7-A2E0-000A959CEE6A@pursued-with.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: questions@freebsd.org Subject: Re: usb to ethernet converter X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2003 05:29:37 -0000 Hmm... so exactly what are "the wings" you are talking about with respect to printing via a USB port that are absent when the communication is over ethernet? As I said in my message: >> This area needs a little clarification. So, if you are unable to explain these wings, (and you did not explain them at all), how can you assume they exist? I think your analogy is insuffient to explain the reason why the printer's protocol works over USB and not over an ethernet link to - ethernet-2-usb-converter - to usb printer. So, let us all benefit from your brilliant and exuisite mind (sic :) and explain to all of us how and why the upper level printer-specific print protocol depends on the physical communication layer, which has it's own protocol that has absolutely nothing to do specifically with printing? The USB bus can have many different devices connected to it, so it can not be dedicated to handling only the printer protocol. I repeat, I am seeking knowledgeable explanation of how and why it would work or not work. Thanks to any and all who care to explain this clearly. Cheers, Joe Kevin Stevens wrote: > > On Sunday, Aug 24, 2003, at 20:26 US/Pacific, Joseph I. Davida wrote: > >> If that is the case, how is it that the >> protocol can work over direct connection >> to USB port and not over ethernet? >> This area needs a little clarification. >> All we are changing is the physical interface, >> but keeping the rest of the filters, which do >> the printer specific conversion to bitmaps >> (or whatever that format is) the same. So the >> only change would be in the physical connection. > > > Exquisite reasoning. By the same token, an airplane shouldn't need > wings, since it's just like a car except for the physical transport medium. > >> I just need to know more details why it cannot work. > > > Yes, that's clear. Seems you have some studying to do. Good luck! > > KeS >