From owner-freebsd-hackers Fri Aug 7 12:49:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06763 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 12:49:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06758 for ; Fri, 7 Aug 1998 12:49:49 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id PAA99766 for ; Fri, 7 Aug 1998 15:49:41 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: Date: Fri, 7 Aug 1998 15:53:39 -0400 To: hackers@FreeBSD.ORG From: Garance A Drosihn Subject: CAP vs netatalk for Appletalk/printing support Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I notice the ports collection includes both CAP and netatalk, and that kernel changes have been made for netatalk to take advantage of. I was wondering if most FreeBSD'ers prefer netatalk over CAP. Right now RPI drives many printer queues thru CAP running on Solaris, and we'll soon switch many of those queues over to CAP under AIX. I have a number of improvements to CAP as a result of this, and was wondering if it'd be worthwhile to see about making those changes for CAP under FreeBSD. If a lot of people use CAP then this might be worthwhile, but if most people prefer netatalk then I probably shouldn't spend any time on it. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message