Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!ucbvax!daedalus.UUCP!corwin
From: corwin@daedalus.UUCP (-David C. Kovar)
Newsgroups: comp.protocols.appletalk
Subject: Re: Papif on System V machine
Message-ID: <8903181605.AA24898@daedalus.gsd.harvard.edu>
Date: 18 Mar 89 16:05:30 GMT
References: <734@wucs1.wustl.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: daedalus!kovar%husc4@talcott.harvard.edu
Organization: The Internet
Lines: 19


  I'm at home at the moment and my copy of CAP for a Masscomp is on a
tape at work so I'm doing this from memory. If I recall correctly, the
hardest part, for me, was just figuring out the system V line printing
system. papif itself does not depend on any 4.3BSD lpr'isms. It needs
cap.printers or and environmental variable to resolve the full name of
the printer you want to use and that's it. After that it is just a filter
with stdin on one end and AppleTalk protocols on the other end.

  There may be other problems with compiling it on a sysV machine, such
as signal handling, but it will not have anything to do with lpr depedencies.

-David C. Kovar
	Technical Consultant			ARPA: kovar@husc4.harvard.edu
	Office of Information Technology	BITNET: corwin@harvarda.bitnet
	Harvard University			MacNET: DKovar
						Ma Bell: 617-495-5947

"The difficult we did yesterday, the impossible we're doing now."