From: "Manuel A. McLure" <manuel@mclure.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] got lprng?
Date: Mon, 20 Feb 2006 10:59:03 -0800 [thread overview]
Message-ID: <200602201059.03727.manuel@mclure.org> (raw)
In-Reply-To: <20060220060902.73054.qmail@web31703.mail.mud.yahoo.com>
On Sunday 19 February 2006 10:09 pm, maxim wexler wrote:
> This looks like an elaborate form of
>
> echo -e "This text should appear on the printer\f" >
> /dev/lp0
>
> Which works fine. Also, from apsfilter I was able to
> print a test page. So the hardware seems to be OK.
OK, then. Now, if I remember correctly, you require pure text printing using
the printer's built-in bitmap fonts, correct?
Is this an absolute requirement, or is the requirement just to be able to
print text files? If the latter, then CUPS may still be an option. CUPS will
convert the text file to Postscript, then pipe it through Ghostscript and
print it out on the printer in graphical mode.
The disadvantages of this method are a) it will probably be slower than pure
text printing, b) the font used to print the text will be something like
Courier instead of the printer's built-in font, and c) if your print file
includes printer escape sequences (to change font size, etc.) it won't work
correctly.
These issues can be worked around by defining a raw CUPS queue and manually
filtering the input file through unix2dos or something similar,
Now, supposing that you do require pure text printing, you'll want
an /etc/printcap entry like the following:
lp:sd=/var/spool/lpd/%P
:force_localhost
:lp=/dev/lp0
:filter=/usr/lib/filters/lpf
Once you've created the entry, run "checkpc" to check for any configuration
errors, and "/etc/init.d/lprng start" - let's see if that does the trick. I
think the "force_localhost" may resolve your hostname issues.
--
Manuel A. McLure KE6TAW <manuel@mclure.org> <http://www.mclure.org>
...for in Ulthar, according to an ancient and significant law,
no man may kill a cat. -- H.P. Lovecraft
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-20 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 21:53 [gentoo-user] got lprng? maxim wexler
2006-02-19 22:29 ` Manuel A. McLure
2006-02-20 1:14 ` Glenn Enright
2006-02-20 0:54 ` Manuel A. McLure
2006-02-20 1:47 ` Glenn Enright
2006-02-20 1:36 ` Manuel A. McLure
2006-02-21 9:11 ` Glenn Enright
2006-02-20 6:09 ` maxim wexler
2006-02-20 18:59 ` Manuel A. McLure [this message]
2006-03-01 17:55 ` [gentoo-user] got lprng?[SOLVED] maxim wexler
2006-03-01 18:30 ` Manuel McLure
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=200602201059.03727.manuel@mclure.org \
--to=manuel@mclure.org \
--cc=gentoo-user@lists.gentoo.org \
/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