Date: Fri, 20 Feb 2026 20:45:30 -0500 From: Brandon Allbery <allbery.b@gmail.com> To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= <des@freebsd.org> Cc: stable@freebsd.org Subject: Re: The future of lpr and lpd Message-ID: <CAKFCL4WcV2XYAukS-597RNNXH8VkAaH_KfTCOiGHQMd1S7qqqA@mail.gmail.com> In-Reply-To: <86qzqex4g3.fsf@ltc.des.dev> References: <86wm07xnre.fsf@ltc.des.dev> <86qzqex4g3.fsf@ltc.des.dev>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] "LPRng" is what the upstream has been calling it. Originally it was an open source project with commercial support. I should note that it's fallen out of support twice, most recently continuing since 2019. (I abandoned it for CUPS when the original author stopped supporting it in 2005. Since CUPS supports both BSD lpr and System V lp frontends, it's basically drop-in.) As for fixing the current one, I think someone will need to step forward and take over support; "a general lack of interest over the past several decades" in the original message doesn't suggest that's forthcoming. On Fri, Feb 20, 2026 at 8:37 PM Dag-Erling Smørgrav <des@freebsd.org> wrote: > Dag-Erling Smørgrav <des@FreeBSD.org> writes: > > It would be extremely helpful if those of you who are using base lpr / > > lpd today could take the time to try out the lprng package / the > > print/lprng port (which should be a drop-in replacement) and let me know > > if there is any loss of functionality. > > Sorry, it's actually LPRng (sysutils/LPRng), not lprng (print/lprng), > because that would have been too sensible. > > DES > -- > Dag-Erling Smørgrav - des@FreeBSD.org > > -- brandon s allbery kf8nh allbery.b@gmail.com [-- Attachment #2 --] <div dir="ltr">"LPRng" is what the upstream has been calling it. Originally it was an open source project with commercial support.<div><br></div><div>I should note that it's fallen out of support twice, most recently continuing since 2019. (I abandoned it for CUPS when the original author stopped supporting it in 2005. Since CUPS supports both BSD lpr and System V lp frontends, it's basically drop-in.)</div><div><br></div><div>As for fixing the current one, I think someone will need to step forward and take over support; "a general lack of interest over the past several decades" in the original message doesn't suggest that's forthcoming.</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Feb 20, 2026 at 8:37 PM Dag-Erling Smørgrav <<a href="mailto:des@freebsd.org">des@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dag-Erling Smørgrav <des@FreeBSD.org> writes:<br> > It would be extremely helpful if those of you who are using base lpr /<br> > lpd today could take the time to try out the lprng package / the<br> > print/lprng port (which should be a drop-in replacement) and let me know<br> > if there is any loss of functionality.<br> <br> Sorry, it's actually LPRng (sysutils/LPRng), not lprng (print/lprng),<br> because that would have been too sensible.<br> <br> DES<br> -- <br> Dag-Erling Smørgrav - des@FreeBSD.org<br> <br> </blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>brandon s allbery kf8nh</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a></div></div></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKFCL4WcV2XYAukS-597RNNXH8VkAaH_KfTCOiGHQMd1S7qqqA>