dave
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Umar Goldeli
> Sent: Sunday, 27 August 2000 10:40 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [SLUG] Redhat printtool.
>
>
> I ended up installing
I ended up installing lprng, apsfilter and all the other goodies
neccessary... it all generally works beautifully now, apart from remote
printing - but I'll figure that out eventually.
Danke all.. :)
//umar.
> There's another alternative: apsfilter. This is especially good when your
> sysadmin
> There's another alternative: apsfilter. This is especially good when your
> sysadmin has installed lprng, this making it difficult to use printtool.
> It comes with a console tool for defining queues in printcap that can
> automatically determine (in most cases) the type of file being printed an
> Firstly - the printers in question aren't postscript capable.. secondly, I
> would prefer not to have X on this machine.
Do you need to actually have X on the machine to run this ?
I thought you only needed the Tcl/Tk stuff i might be wrong.
But for what its worth, i have a headless box at ho
There's another alternative: apsfilter. This is especially good when your
sysadmin has installed lprng, this making it difficult to use printtool.
It comes with a console tool for defining queues in printcap that can
automatically determine (in most cases) the type of file being printed and
invoke
Umar Goldeli wrote:
...snip...
> It appears that the only simple('ish) way to setup non-PS printers is to
> use the silly printtool - but it's X only... or is it?
The simple way is to edit the /etc/printcap file by text editor. There
are basically two formats; local or remote; simple.
> "b
Greetings,
Being new to the world of squirting ink onto dead trees - I am currently
fiddling with the latest version of ghostscript/rhs-printfilters and other
miscellany..
Firstly - the printers in question aren't postscript capable.. secondly, I
would prefer not to have X on this machine.
It a
