9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Aki Nyrhinen" <anyrhine@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Ideas for an printer filesystem
Date: Fri, 30 Nov 2007 09:19:42 +0200	[thread overview]
Message-ID: <218917ef0711292319j237007b2kcec16153d38017fd@mail.gmail.com> (raw)
In-Reply-To: <ae3d7b2869423235ae56410a7609bbcc@quanstro.net>

On Sep 7, 2007 12:54 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> > The fs does not issue the print command until the descriptor being
> > used to update file contents is closed.
>
> ah.  the print directory is not any old directory, but a special fs.
>
> > And yes, on Plan 9, lp is used. On macosx, lpr.
> unfortunate.

i think so too. gs(1) is the guy who does all the work for home
class printers, so i've never set up lp (it's too damn hard and it's
functionality would be mostly useless anyway!). instead, i've
been happy to type a gs command into a script. it's something
like (can't really check now)

gs -dNOPAUSE -sDEVICE=hl7x0 -sOutputFile=/dev/lpt1data -q -dBATCH $1

this seems to work with a higher success rate than cups on the
linux distribution of the day. configuration consists of changing
the strings hl7x0 and lpt1data to something that works for you.
if the printer is old and bad and has too little memory, add -r300
or similar to print in bigger dots.

could be you need to recompile plan9 gs, it has reduced support
for printers per default.

i can imagine it'd be easy to make nemos print spooler to exec
a script instead of lp. the script could exec that gs command or
dial tcp for networked or do spam filtering.


  reply	other threads:[~2007-11-30  7:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 23:56 Enrico Weigelt
2007-09-07  8:44 ` Francisco J Ballesteros
2007-09-07 10:08   ` erik quanstrom
2007-09-07 10:17     ` Francisco J Ballesteros
2007-09-07 10:54       ` erik quanstrom
2007-11-30  7:19         ` Aki Nyrhinen [this message]
2007-11-30  3:37       ` Enrico Weigelt
2007-11-30  9:42         ` Francisco J Ballesteros
2007-11-30 12:32           ` Enrico Weigelt
2007-11-30 13:06             ` Rodolfo =?unknown-8bit?Q?Garc=EDa?=
2007-11-30 13:38               ` Enrico Weigelt
2007-11-30 16:56                 ` Rodolfo =?unknown-8bit?Q?Garc=EDa?=
2007-11-30 16:46             ` Anant Narayanan
2007-11-30 22:40               ` Lucas James
2007-12-01  4:42 ` ron minnich
2007-12-01  4:54   ` Bruce Ellis
2007-12-11 13:30     ` roger peppe
2007-12-11 20:36       ` Bruce Ellis

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=218917ef0711292319j237007b2kcec16153d38017fd@mail.gmail.com \
    --to=anyrhine@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).