David wrote:
yes exactly :s -l /dev/lp0 gets
crw-rw---- 1 root lp 6, 0Apr15 1999 /dev/lp0
Is that a good thing? David
That's perfectly normal. What Graham suggested is the basic test on "unwilling" devices: cat a file to it. Since it's connected to the printer, something is bound to happen. i.e. try: cat /etc/printcap > /dev/lp0 you should expect a "staicased" output like -----8<---- # ### BEGIN apsfilter: ### PS_300dpi a4 mono 300 ### # Warning: Configured for At some point it runs of the page, showing that communication works and lp0 *is* the correct device. Then it's time to think about the rest. Well if all fails it's trial and error with /dev/lp1. Juergen PS: If stuff is listed in the queue but doesn't print try (as root) "lpc up all"
--- Graham Smith
wrote: doing what you suggest adds the file to the
On 13-Mar-2000 David wrote: list
in lpq but the printer remains silent.
That does not make sense. The command cat <file> > /dev/lp0 writes directly to the port and bypasses the lpr program altogether. What happens when you do an ls -l on /dev/lp0? You should see something like shown below.
ls -l /dev/lp0 crw-rw---- 1 root lp 6, 0 Dec 4 01:39 /dev/lp0
Regards,
Graham Smith
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/