Thread View: comp.bugs.sys5
4 messages
4 total messages
Started by Robert Withrow
Sun, 21 Apr 1991 02:43
SVR4.0 V2.0 -- lp(7) not configured as documented.
Author: Robert Withrow
Date: Sun, 21 Apr 1991 02:43
Date: Sun, 21 Apr 1991 02:43
16 lines
985 bytes
985 bytes
This is specifically for Intel SVR4.0 V2.0.
The documentation for lp(7) states that the /dev/lp(x) port operates
as documented in termio(7). This is a *fib*, however, since no one
got around to telling the autopush(1) utility to push the terminal
line discipline module onto this device. If you want the lp(7) driver
to operate as documented you want to add a line like this to your
/etc/ap/chan.ap file:
# major minor lastminor modules
7 -1 0 ldterm ttcompat
--
---
Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
Re: SVR4.0 V2.0 -- lp(7) not configured as documented.
Author: Guy Harris
Date: Mon, 22 Apr 1991 17:33
Date: Mon, 22 Apr 1991 17:33
5 lines
665 bytes
665 bytes
>If you want the lp(7) driver to operate as documented you want to add >a line like this to your /etc/ap/chan.ap file: You can probably leave "ttcompat" off, unless you want to be able to perform V7/BSD-style "ioctl()"s on "/dev/lp"....
Re: SVR4.0 V2.0 -- lp(7) not configured as documented.
Author: Robert Withrow
Date: Tue, 23 Apr 1991 13:42
Date: Tue, 23 Apr 1991 13:42
13 lines
937 bytes
937 bytes
In article <7318@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes: |You can probably leave "ttcompat" off, unless you want to be able to |perform V7/BSD-style "ioctl()"s on "/dev/lp".... I agree. The reason why I included it is because AT&T included it for the ASY(7) driver, the man page for which reads just like the one for LP(7). -- --- Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
SVR4.0 PostScript Printer Problem
Author: Paul Breslaw
Date: Thu, 25 Apr 1991 20:57
Date: Thu, 25 Apr 1991 20:57
38 lines
1477 bytes
1477 bytes
I'm running SysVR4 on Intel 486 workstations.
We have some remote SunOS/Ultrix PostScript printers which I need
to configure into the spooling system.
I followed the instructions in the Advanced System Management Guide
and configured one logical printer as
lpadmin -p ps1 -s remote!ps -T PS -I PS
and another as
lpadmin -p ps2 -s remote!ps -I PS,troff,simple
and another as
lpadmin -p ps3 -s remote!ps
Now I want to print a manual page, I guess by
troff -man mpage.1 | lp -d printer -T troff
If printer is ps1 or ps3 I'm told nothing but it doesn't print.
If printer is ps2 I'm told there is no filter.
If I rip out the troff->postscript filter dpost and run
troff -man mpage.1 | dpost | lp -d printer
with ps1 or ps3 everything works fine. I forget what happened if
printer is ps2.
Is a remote PostScript printer a PostScript printer type or an unknown
printer type, or something else.
Any suggestions?
Paul Breslaw (paul@hasler.ascom.ch)
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads