From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
Date: Mon,  3 May 2010 05:00:56 -0700
Message-ID: <z2zfe41879c1005030500yacb6bb31h3f5ff405455a088d@mail.gmail.com>
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [9fans] An Important Node
Topicbox-Message-UUID: 17bbf08a-ead6-11e9-9d60-3106f5b1d025

With one network- and PS- incapable printer* in
the household, and several computers with at least
a few users, there was a need to have some sort of
network capable printing device.

The printer is hooked up via (just for added complexity)
USB to the Plan 9 CPU server. Printing amongst Plan 9
computers is easy enough - run usb/print, export /dev,
etc. (maybe a cleaner way? the problem is with /dev/lp7,
which only shows up once usb/print is run), ending with
an lp(1) command. However, other computers are running
Windows or Linux.

So, in order to have Windows see the CPU server as a
network printer, I simply "[Added] a New Printer" on TCP,
port PORT, and IP that of the CPU server, with the device
being Adobe's Generic PostScript Printer, which produces
basic PS pages (something lp(1) on Plan 9 can deal with).

On the Plan 9 side, then, the CPU server listens:

aux/listen1 -tv tcp!*!PORT $home/bin/rc/print &

where the script `print' contains:

#!/bin/rc

lp -H -d officejet5610 >>[2] /sys/lib/lp/log/officejet5610

... and that's all she wrote.


Best,
ak

* OfficeJet 5610 - I highly discourage this product.
  (welcome, HP)