From: "Russ Cox" <rsc@swtch.com>
To: "Lucio De Re" <lucio@proxima.alt.za>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] JetDirect printing
Date: Thu, 7 Dec 2006 16:39:31 -0500 [thread overview]
Message-ID: <ee9e417a0612071339m5ccbb048j53bb070771ce7f90@mail.gmail.com> (raw)
In-Reply-To: <a66cfc287b07cf5fd7e3b08d728b66cf@proxima.alt.za>
> # 2c307 2C-307 alice tcp!mh2c307!9100 81920 post+600dpi generic generic generic generic tcppost FIFO
> # fn 2C-501 helix tcp!fn!9100 81920 post2+600dpi+duplex generic generic generic generic tcppost FIFO
>
> are intended for use with JetDirect connected printers. But how do
> "alice" and "helix" actually deal with this?
They deal with it by invoking the tcppost transport.
See /sys/lib/lp/daemon/tcppost.
Russ
prev parent reply other threads:[~2006-12-07 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 19:28 Lucio De Re
2006-12-07 21:39 ` Russ Cox [this message]
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=ee9e417a0612071339m5ccbb048j53bb070771ce7f90@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
--cc=lucio@proxima.alt.za \
/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;
as well as URLs for NNTP newsgroup(s).