From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] An Important Node
Date: Mon, 3 May 2010 05:00:56 -0700 [thread overview]
Message-ID: <z2zfe41879c1005030500yacb6bb31h3f5ff405455a088d@mail.gmail.com> (raw)
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)
next reply other threads:[~2010-05-03 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 12:00 Akshat Kumar [this message]
2010-05-03 14:05 ` erik quanstrom
2010-05-03 19:01 ` Akshat Kumar
2010-05-03 19:07 ` erik quanstrom
2010-05-03 19:24 ` Akshat Kumar
2010-05-05 6:48 ` lucio
2010-05-05 7:47 ` Akshat Kumar
2010-05-05 8:20 ` lucio
2010-05-05 12:08 ` lucio
2010-05-05 13:44 ` [9fans] plan9 lpt1 Steve Simon
2010-05-05 22:22 ` [9fans] An Important Node Akshat Kumar
2010-05-06 4:14 ` lucio
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=z2zfe41879c1005030500yacb6bb31h3f5ff405455a088d@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/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).