From: "Thomas West" <west9@worldnet.att.net>
To: <9fans@cse.psu.edu>
Subject: [9fans] lp doesn't work after upgrade from downloaded cd image
Date: Tue, 8 Oct 2002 11:52:42 -0700 [thread overview]
Message-ID: <000e01c26efc$03ca51c0$b9b0590c@default> (raw)
After upgrade from a recent cd image lp fails; printing is normal on win95
My system is a standalone pc.
after
cat foo| lp
the print light blinks , as if to start printing ,but quits after about a
second and goes back to standby.
I can print this way:
cat foo| lp -dstdout > /dev/lpt1data
but the result is the intended file along with a spurious page.
Nothing was written to log , prob, tmp, or queue in /sys/lib/lp
lp -d'?' lists the printer.
Guidance valued-
-Tom
next reply other threads:[~2002-10-08 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 18:52 Thomas West [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 16:45 rob pike, esq.
2002-10-08 16:06 Russ Cox
2002-10-08 16:01 rob pike, esq.
2002-10-09 16:39 ` Dan Cross
[not found] <rsc@plan9.bell-labs.com>
2002-10-08 15:58 ` Russ Cox
2002-10-08 16:08 ` Scott Schwartz
2002-10-08 13:36 Skip Tavakkolian
2002-10-08 12:57 Skip Tavakkolian
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='000e01c26efc$03ca51c0$b9b0590c@default' \
--to=west9@worldnet.att.net \
--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).