From owner-cvs-all Wed Nov 1 13:10:31 2000 Delivered-To: cvs-all@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 52A7037B479; Wed, 1 Nov 2000 13:10:27 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eA1LAJU18369; Wed, 1 Nov 2000 13:10:20 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Andreas Klemm Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc printcap In-Reply-To: Message from Andreas Klemm of "Wed, 01 Nov 2000 05:30:25 PST." <200011011330.FAA23892@freefall.freebsd.org> Date: Wed, 01 Nov 2000 13:10:19 -0800 Message-ID: <18365.973113019@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Therefore best decision: if people want printing, then configure both > 1. /etc/rc.conf > 2. /etc/printcap I'm not sure I agree with this reasoning - the /etc/rc.conf configuration of lpd can be considered as a reasonably front-ended by sysinstall at installation time whereas there's nothing to configure /etc/printcap. Since new users will likely have no idea that /etc/printcap has anything to do with turning on lpd (hitting the "Print" button in Netscape is about the most they can handle), there needs to be an automated way of dealing with this before just turning it off. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message