9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] printing from Plan 9
Date: Sun, 15 Sep 2019 12:52:54 -0700	[thread overview]
Message-ID: <293bbc77c2af2d77@orthanc.ca> (raw)
In-Reply-To: <248a959f6e8ea9cb7ebfe1534d30a40a@hamnavoe.com>

Richard Miller writes:

> Before replacing my expiring inkjet printer I thought I'd ask
> the list: does anyone still use lp(1) nowadays, and are there
> printers currently on the market which work well with Plan 9?

As others have mentioned, life is far too short for CUPS.

For Plan9 printing I have always just used a laser printer that
natively supports Postscript.  You pay a bit more for Postscript,
but that pays for itself immediately in not having to dick around
with CUPS, gs, or gawd knows what else to get the hardware talking
to whatever system you've plugged it into.

I currently have an HP Laserjet M402dn.  It speaks Postscript 3,
prints up to 40 PPM, supports duplex printing, and talks lpd or
"virtual serial port" on port 9100.  CAD$350 from Staples.

I've never had any trouble making these consumer HP Postscript
printers interface with lp(1).  I configure them as an lpd printer,
and then point all the other hosts on the network at the Plan9 CPU
server as their default 'printer'.  This lets me use the lp(1)
content conversion filters on all the other hosts -- I find lp's
behaviour to be far superior to anything that MacOS and the others
provide.

If you really need an inkjet (e.g. for colour), I would still
recommend finding something that natively supports Postscript.
Failing that, you're likely going to have to connect the inkjet to
something like a Mac or a Linux host.  But as long as you can
configure the print host to listen on the lpd port and handle
incoming Postscript jobs correctly, you should just be able to
configure it as a networked Postscript printer.

--lyndon



  parent reply	other threads:[~2019-09-15 19:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-14  9:04 Richard Miller
2019-09-14  9:14 ` Covert Username
2019-09-14 10:43 ` Graham Gallagher
2019-09-14 11:41   ` Richard Miller
2019-09-14 12:27     ` Charles Forsyth
2019-09-16 11:42       ` arnold
2019-09-15 19:52 ` Lyndon Nerenberg [this message]
2019-09-16  4:14   ` Lucio De Re
2019-09-16 13:45 ` Ethan Gardener
2019-09-16 17:41   ` hiro
2019-09-14  9:12 umbraticus

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=293bbc77c2af2d77@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --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).