But regarding its alternatives... there are none. Those "modern"#
printers can usually only get to work using CUPS, because apsfilter

there are. don't use these "modern" printers. Of course not all of them.

It's natural that you buy hardware that will be supported by software you use. CUPS is like workaround for me.

Decent, network-capable, PostScript printers do not have to be
costly.

I didn't say they have. It's always a question of the printers

postscript printer is the simplest solution. anyway - they MAY NOT print every page because they have limited hardware capacity and may be not able to process overcomplex postscript files.

Possibly not a big deal today as their capacity is better than before, but in case of problems you may use ghostscript as ps-to-ps filter.

quality (how good it works, how long it works) and the amount
of toner they come with; for inkjet stuff, criteria are similar

Unless you need to print no more than 10 pages a month, i recommend against buying any inkjet printer. They are incredibly costly to use, even when being damn cheap to buy.

Done the same with HP Laserjet 4000 duplex - it even received
an IP automatically via DHCP, so I just had to "arp -a" and
edit /etc/hosts and /etc/printcap. The lpq / lprm tools seemed
to operate on the printer server inside the printer.

For non-ethernet printers like my laserjet 4 there are often available original print server modules for them for really nothing (i paid <10$)

if not, and you need ethernet connectivity, then this

http://www.edimax.com/en/produce_detail.php?pd_id=50&pl1_id=7&pl2_id=34

is a perfect choice. i recommend it for every unix user.

As they are advertised as mostly for windows, i actually found configuring it under unix very simple exactly as you said (/etc/printcap), while incredibly complex under windows ;)

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to