> Yes, I had to do a fair bit of work to get my OfficeJet 5610 working
> with Plan 9. That topic was taken care of in a separate series of
> posts a while back. I documented the procedure in my contrib:
I recall now: my poor memory should not be taken as a reflection of
the value of your efforts a
On Wed, May 5, 2010 at 5:08 AM, wrote:
>> ... and that's all she wrote.
>
> Hm, you also added an entry for officejet5610 in /sys/lib/lp/devices,
> I presume, as I have nonesuch. But that's to be expected.
Yes, I had to do a fair bit of work to get my OfficeJet 5610 working
with Plan 9. That to
> ... and that's all she wrote.
Hm, you also added an entry for officejet5610 in /sys/lib/lp/devices,
I presume, as I have nonesuch. But that's to be expected. What I
find ultimately disappoining is that I can't get the parallel port on
my server to behave in any reasonable way.
The man pages s
> Add Local Printer -> Create New Port (or some such)
> with Type of Port: Standard TCP/IP
I'm way out of touch. I never even thought of looking for such a
feature!
++L
I've setup Windows 7 and Windows XP to do this.
For XP:
Control Panel -> Printers and Faxes -> Add Printer
Add Local Printer -> Create New Port (or some such)
with Type of Port: Standard TCP/IP
fill in IP and port information, using RAW type of data.
Upon choosing a printer from the provided list,
> 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).
What
OK, placing this in /rc/bin/service works well now.
Thank you for that suggestion.
Best,
ak
On Mon, May 3, 2010 at 12:07 PM, erik quanstrom wrote:
> if you put your script in the listen -t directory,
> you won't be none.
>
> - erik
> however, the program runs as user none, and
> requires access to /dev/lp7 (which I believe is
> not in its namespace, in the first place).
> Perhaps this approach would work better if I
> ran usb/print on boot up - although still, the
> file /dev/lp7 is chmod 660 for user and group
> bootes. Idea
I tried this initially, with the following in the file:
exec /rc/bin/lp -H -d officejet5610 >>[2] /sys/lib/lp/log/officejet5610
however, the program runs as user none, and
requires access to /dev/lp7 (which I believe is
not in its namespace, in the first place).
Perhaps this approach would work b
> On the Plan 9 side, then, the CPU server listens:
>
> aux/listen1 -tv tcp!*!PORT $home/bin/rc/print &
makes more sense to put this script in /rc/bin/service/tcpPORT
- erik
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
comp
11 matches
Mail list logo
