From owner-freebsd-arch Tue Jun 27 8:29:19 2000 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C6F0637C22B; Tue, 27 Jun 2000 08:29:08 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id RAA26901; Tue, 27 Jun 2000 17:28:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: nate@yogotech.com (Nate Williams) Cc: Warner Losh , Wes Peters , papowell@astart.com, Doug@gorean.org, nik@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: Bringing LPRng into FreeBSD? In-reply-to: Your message of "Tue, 27 Jun 2000 08:09:08 MDT." <200006271409.IAA04044@nomad.yogotech.com> Date: Tue, 27 Jun 2000 17:28:44 +0200 Message-ID: <26899.962119724@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200006271409.IAA04044@nomad.yogotech.com>, Nate Williams writes: >> We're not Joe's Print Server Corp. That's Joe's problem, not ours. > >No, it's ours, in that the software we have currently (which is used by >Joe's Printer Server Corp.) works fine for Joe, and he has no licensing >issues at all. If Joe is in the print server business, I am absolutely damn certain that he has made modifications to the lp{rdc} stuff we have in our tree, so I *seriously* doubt he would want to switch to LPRng in the first place. ... Unless he already has sorted out the license and is using LPRng. Should anybody be wildly emotionally attached to the current lp{rdc} stuff, they can always dig it out of the reposistory and make it a port if they feel like it. Lets get LPRng in and be done with it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message