No. If it is postscript or PCL, you do not need hplip.If you use HP, then that's the driver to use.
No. If it is postscript or PCL, you do not need hplip.If you use HP, then that's the driver to use.
Very meta. Me like (bozo me is clicking like above).(stops to add a like to hruodr's post)
I just changed printers because my old HP one was out of order.This is good, because it will force a compliant implementation to come along.
3 major changes so far in 2026 in response to that mailing list thread, hardly any before this most recently.
sysutils/lprng is GPL. It didn't work for me on FreeBSD when I tried it: in this case, for an HP printer.
It seems to be a Linux Foundation sponsored implementation. CUPS required GCC to build, when the main printing application should use base compilers and tools.
Good, but heavy, that it requires a browser, network settings, and uses lots of non BSD components.
When I used HPLIP, it required CUPS as a dependency. If you use HP, then that's the driver to use.
CUPS and LPRng have LPR implementations in their own relevant directories.
CUPS needs a lightweight fork which uses BSD components as dependencies. Otherwise, there's a need for a command line BSD replacement for LPR, which is jointly maintained by NetBSD and OpenBSD. LPR uses the description of RFC1179, so this RFC is more important than the old implementation itself.
What is lacking is a Scanner version of CUPS with a browser interface. There was an online mention of one, such as a college hobbyist attempt, but nothing solid.
The mailing list discussions are good.
https://lists.freebsd.org/archives/freebsd-arch/2026-February/001231.html
CUPS uses both IPP and an implementation of LPR. In the mailing lists as well as in this thread, using the -s option with LPR was also mentioned. The purpose of firewalls and keeping daemons local to protect such applications was also mentioned in the mailing list.
#>avahi-browse -rt _ipp._tcp
lp -d name_printer /etc/hosts
$>curl http://IP_printer/eSCL/ScannerStatus
Weren't Postscript printers more expensive? As they were identical to another printer, but had an added letter to some they were Postscript, for using licensing rights. Postscript printers are required for older Apple though. But PCL is a more used standard.If it is postscript or PCL, you do not need hplip.
Postscript is a wonderful high level programming language, PCL low level, I doubt it is usable to write programs by hand. Postscript printers process it inside the printer.Weren't Postscript printers more expensive? As they were identical to another printer, but had an added letter to some they were Postscript, for using licensing rights. Postscript printers are required for older Apple though. But PCL is a more used standard.
Strange. I always used HP, with postscript or PCL, and was thinking on buying a brother.My brother printer is PCL. But i cant send a pcl file directly to it. It does not understand.
#!/bin/sh
/usr/local/bin/gs -dSAFER -dNOPAUSE -dBATCH -q -sDEVICE=pxlmono -r600\
-sPAPERSIZE=a4 -sOutputFile=- -
#!/bin/sh
/usr/local/bin/gs -dSAFER -dNOPAUSE -dBATCH -q -sDEVICE=ljet4 -r300\
-sPAPERSIZE=a4 -sOutputFile=- -
If it has a parallel port, cat'ing the PCL to the port should work. Sometimes you have to send an EOF character afterwards. If may be network only.My brother printer is PCL. But i cant send a pcl file directly to it. It does not understand.
gs -q -dNOPAUSE -dBATCH -sDEVICE=pxlmono \
-dDuplex=true -dTumble=false \
-sOutputFile=output.prn \
-c "<</Duplex true /Tumble false>> setpagedevice" \
-f $1
nc <IP-ADRES-PRINTER> 9100 < output.prn
Interesting. Then maybe that's ok.we replaced LPRng in that role with CUPS as a college sysadmin in the early 2000s. CUPS can absolutely do this. We even added in page accounting that queried the printer for its pagecount register between jobs.![]()