From owner-freebsd-hackers Tue Jun 13 03:25:34 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA05997 for hackers-outgoing; Tue, 13 Jun 1995 03:25:34 -0700 Received: from wcarchive.cdrom.com (wcarchive.cdrom.com [192.216.191.11]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA05983 for ; Tue, 13 Jun 1995 03:25:30 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by wcarchive.cdrom.com (8.6.11/8.6.9) with ESMTP id DAA16782 for ; Tue, 13 Jun 1995 03:26:19 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id SAA01741 for freebsd-hackers@freebsd.cdrom.com; Tue, 13 Jun 1995 18:25:07 +0800 Date: Tue, 13 Jun 1995 18:25:07 +0800 From: Brian Tao Message-Id: <199506131025.SAA01741@aries.ibms.sinica.edu.tw> Newsgroups: comp.sys.sgi.admin,comp.unix.bsd.freebsd.misc Subject: FreeBSD 2.0.5 <-> IRIX 5.2/6.0.1 print queue Organization: Institute of Biomedical Sciences, Academia Sinica Apparently-To: freebsd-hackers@wcarchive.cdrom.com Sender: hackers-owner@FreeBSD.org Precedence: bulk There is a departmental LaserJet 4P printer connected to an Indigo^2 with the Impressario 1.2 drivers. Getting other Irises on the network to talk to the printer is easy. I would like to configure our multitude of FreeBSD 2.0.5 workstations to use that network printer as well. /etc/printcap on the FreeBSD machines has one entry: hp4|iris4|Hewlett-Packard LaserJet 4P:\ :lp=:rm=iris4:rp=hp4:sd=/var/spool/output/hp4:lf=/var/log/lpd-errs: It doesn't complain when I print to "hp4", but lpq shows the job is never actually spooled to the server, and I see: IRIS4: /usr/etc/lpd: hp4: unknown printer According to lpstat -d on iris4, "hp4" is a valid printer and the IRIS Print Manager confirms this. The /etc/printcap on iris4 doesn't list the hp4 though, so I'm not sure how it knows the default printer is supposed to be the HP. Anyhow, the printed 4.3BSD Line Printer Spooler Manual doesn't talk about this and I don't have anything more recent on hand. IRIS Insight only mentions connecting the SGI to other SGI's. I'm aware of the traditional obstacle facing SysV-BSD printer sharing, but never really investigated why this is so. Are there any workable solutions now for connecting BSD boxes to a SysV print server? The best I can do right now is a kludgy shell script that replaces the /usr/bin/lp binary and basically pipes the file (or stdin) to the print server via an rsh. As far as I'm concerned, this is just a band-aid solution until I figure out a real one. Any advice would be appreciated. Thanks.