From: Ishwar Rattan rattan@cps201.cps.cmich.edu
Subject: man and printing files..
Date: Wed, 3 Jul 1996 10:54:44 -0400 [thread overview]
Message-ID: <19960703145444.IiOEb-AtA-kA9J2c5S1BuGRi6gk2P5tX17H7w6ZEwyg@z> (raw)
Hello
I have a standalone PC/AT (8Mb RAM, 640x480x1 vga) running Plan9.
I can't make `man' command work properly (the result is shown below).
term% man 8c
troff: cannot do .ev 49; line 5, file stdin
stack: }F }E TH
stdin 1 0
I tried to use the printer (postscript Apple LaserWriter 360) connected
to the parallel port (0x378).
term% bind -a '#L2' /dev
term% cat one.c > /dev/lpt2data
term%
sends the file to printer but there is a problem with correct
translation of CRLFs. I can't find a command like `lp' to send
files to this printer.
Also is there a way to set up the printer daemon on a stand alone
so that files can be printed using `lp' command.
term% lp -d'?'
srv: dial net!bootes!9fs: net!bootes!9fs: cs: can't translate address
mount: can't open /srv/bootes: file doesn't exist
could not set properly setup LSPOOL
I checked /srv/bootes does not exist.
Can somebody shed light on these things? Thanks.
Ishwar Rattan
reply other threads:[~1996-07-03 14:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19960703145444.IiOEb-AtA-kA9J2c5S1BuGRi6gk2P5tX17H7w6ZEwyg@z \
--to=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).