Return to BSD News archive
Xref: sserve comp.sys.hp:17360 comp.unix.bsd:6260 comp.unix.ultrix:14231 comp.unix.questions:26884 Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!spool.mu.edu!agate!doc.ic.ac.uk!uknet!mcsun!chsun!hslrswi!aut!nbladt From: nbladt@autelca.ascom.ch (Norbert Bladt) Newsgroups: comp.sys.hp,comp.unix.bsd,comp.unix.ultrix,comp.unix.questions Subject: Re: Remote Printing from HP to BSD systems Message-ID: <1992Oct7.073653.20235@autelca.ascom.ch> Date: 7 Oct 92 07:36:53 GMT References: <1992Oct1.101600.10026@hp9000.csc.cuhk.hk> <1992Oct06.201338.2138@news.mentorg.com> Organization: Ascom Autelca AG, Guemligen, Switzerland Lines: 31 stevej@hpc.mentorg.com (Steve Jumonville) writes: >System V printing is painful to use if you're not familiar with it. Yes. I completely agree with this statement. >I suggest you use the menu driven 'sam' utility (System Admin Manager) to >set up printing to BSD. When you're in sam, follow the menu tree down through >peripherals, printers and plotters, to "setting up a remote printer". If you >have questions, use the "Help" funciton key. We solved it in a very simple way: chown lp /usr/bin/lp chmod u+s /usr/bin/lp (now /usr/bin/lp is running as user "lp" !) This is necessary because on every *n*x system around there is an user "lp". (At least, on any *n*x system we have here, HP's, SUN's, Interactive UNIX, etc.) Now you can write a simple model/interface file which just does a remote shell on the other system and that's it. Something like cat file | 'rsh BSDhost lp -Pbsd-printer-name' >By the way, run 'sam' in an 'hpterm' window if you want access to function keys. I guess, that you could do it with 'sam' on HP's, we never used it on System V. Hope this helps, Norbert. -- Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland Phone: +41 31 999 65 52 FAX: +41 31 999 65 44 Mail: nbladt@autelca.ascom.ch UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt