From owner-freebsd-arch  Mon Jul  3 20:30:34 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from astart2.astart.com (astart2.astart.com [206.71.174.194])
	by hub.freebsd.org (Postfix) with ESMTP id 598BB37B5E7
	for <arch@FreeBSD.ORG>; Mon,  3 Jul 2000 20:30:30 -0700 (PDT)
	(envelope-from papowell@astart.com)
Received: from h4.private (papowell@h4.private [10.0.0.4])
	by astart2.astart.com (8.9.3/8.9.3) with ESMTP id UAA28679;
	Mon, 3 Jul 2000 20:32:33 -0700 (PDT)
Received: (from papowell@localhost)
	by h4.private (8.9.3/8.9.3) id UAA07644;
	Mon, 3 Jul 2000 20:30:04 -0700 (PDT)
Date: Mon, 3 Jul 2000 20:30:04 -0700 (PDT)
From: papowell@astart.com
Message-Id: <200007040330.UAA07644@h4.private>
To: arch@FreeBSD.ORG, sheldonh@uunet.co.za
Subject: Re: was: Bringing LPRng into FreeBSD?
Cc: papowell@astart.com
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> From sheldonh@axl.ops.uunet.co.za Mon Jun 26 02:46:32 2000
> From: Sheldon Hearn <sheldonh@uunet.co.za>
> To: arch@FreeBSD.ORG
> cc: papowell@astart.com
> Subject: Re: was: Bringing LPRng into FreeBSD? 
> Date: Mon, 26 Jun 2000 11:46:23 +0200
>
>
> Could someone just enumerate the advantages of importing LPRng?  It
> seems to be a package which can me made to do everything FreeBSD's lpr
> can do, but it does not seem to be a superset of FreeBSD's lpr.  This
> means that there is a cost associated with bringing it in as a
> replacement.
>
> Are we sure that the cost is justified?  Is it so much better than the
> existing lpr that having it available as a port is "not enough"?
>
> I have no stsrong opinion one way or the other, but I do get the feeling
> that this thread has skipped an important issue, instead focusing on
> licensing.  This looks like a little cart before horse.
>
> Ciao,
> Sheldon.
>

1. Kerberos authentication,  as well as PGP, md5, etc. support.

2. Load balancing queues

3. Dynamic routing of jobs

4. Form support

5. Permissions support for printers at the user level

6. Printcap support that allows you to easily use LDAP,
   NIS++,  SQL, or your favorite network database.

7. Diagnostics.

8. More Diagnostics.

9. Did I mention dynamically configurable run time enabled
   diagnostics?

10. remote lpc administration

Patrick Powell


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message