From: "Chris DiTrani" <cditrani@livedata.com>
To: linux-admin@vger.kernel.org
Subject: Re: Samba advice
Date: Tue, 25 May 2004 17:27:05 -0400 [thread overview]
Message-ID: <0baf01c4429f$06adc020$8401a8c0@monsta> (raw)
In-Reply-To: Pine.SOL.4.56.0405251649540.15289@hadar.cse.Buffalo.EDU
----- Original Message -----
From: "Tony Gogoi" <tgogoi@cse.Buffalo.EDU>
>
> > that's not how printing works.
> >
> > The desktop, no matter what OS, uses drivers to transform print into
> > language that the printer understands. Print servers merely offer the
> > printers as a share for spooling and pass the data off to the printer.
> >
> So, if the printer driver is installed on a Linux print server and a
> windows client wants to print a colorful word document, there shouldn't be
> any problems as the windows client sends the data to be printed in a
> format the linux printer driver understands ??????
The the linux print server in this mode is just a pass-thru to the printer,
providing queueing and not much more. You can almost think of the linux
print server as part of the cable between the windows boxes and the printer.
The linux print server doesn't really care what printer it's connected to -
it's just passing data through from a windows box that used the correct
printer-specific driver to format the data.
You can install the windows driver for you printer on the linux server and
samba will allow users on windows boxes to load it when they connect to the
shared printer, but linux isn't using that driver to talk to the printer.
CD
next prev parent reply other threads:[~2004-05-25 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 18:28 Samba advice Tony Gogoi
2004-05-24 18:35 ` Adam Lang
2004-05-25 0:33 ` Mauricio Silveira
2004-05-25 15:56 ` Tony Gogoi
2004-05-25 16:02 ` Adam Lang
2004-05-25 17:33 ` Dmitry Ivanov
2004-05-25 17:52 ` Adam Lang
2004-05-25 20:55 ` Tony Gogoi
2004-05-25 21:07 ` Adam Lang
2004-05-25 21:27 ` Chris DiTrani [this message]
2004-05-26 5:04 ` Mauricio Silveira
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='0baf01c4429f$06adc020$8401a8c0@monsta' \
--to=cditrani@livedata.com \
--cc=linux-admin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.