Oko said:
What does it make easier? Can you be more specific? Maybe you think that he is
running corporate network which has 500 printers distributed in five different office buildings and 2000 users who can send the documents to only selected printers in their office building.
CUPS works just fine on single-user desktops. And it makes a lot of things a lot simpler to do than plain-jane LPD, especially for newbies to Unix and those coming from a non-Unix background.
Plus, it's what MacOS X uses, so there's a *lot* of PPD files (driver files) available for pretty much any printer. If it works on a Mac, it'll work on a Unix system running CUPS.
CUPS is developed for enterprise printing. The only novel thing introduced by CUPS is support for IPP (Interent Printing Protocol). The only other thing that CUPS is really good at is being a good text filter (see above for what text filter does).
CUPS makes managing large numbers of printers easy, true. But it doesn't make managing small numbers of printers hard. In fact, it makes managing a single printer a lot easier than trying to get LPD up and running. Especially since the setup/config is the same across all the systems that support CUPS. For desktop systems, there's even nice, proper, working integration with KDE, GNOME, and XFCE tools.
Everything else is much, much more complicated than on LPD.
I beg to differ. Having administered CUPS printing for the past couple of years, it is soooooo much simple than LPD/LPR/LPRng. Especially when you want to get non-postscript, non-networked printers configured. It's pretty much plug-n-play now. Especially if you install the foomatic-ppds port, which includes "drivers" for several hundred printers.
Trouble shooting CUPS is a nightmare but you obviously have not done that.
Trouble-shooting CUPS is simple. You check the access.log, the error.log, and the audit log. How is that difficult?
To be honest with you you really do not need any spooling system if you are going to use printer on your desktop. Just get the printer which speaks Post Script and send directly file with (you of course need to have correct permission)
So, your advice is to throw away whatever printer you already have, even though it works perfectly, and to go out and find a printer that speaks Postscript natively? Why not just plug it in, grab a PPD file off
OpenPrinting, plug that into CUPS, and be on your merry way?
Is CUPS daemon going to start itself? You have to replace native LPD commands with CUPS commands which have the same name unless you are going to use the full path. Did you explain him that?
No you don't. Unless you are going to be mucking around at the command-line running "lp" commands manually, you don't have to replace or rename files or do anything crazy like that.
You didn't tell him anything about permissions, groups, and similar issues.
What permissions issues? By default, CUPS only listens on localhost. You have to explicitly configure it to listen on another IP, and to have it broadcast out to the network.
On another hand if he has winprinter which is probably the case the driver for his printer probably doesn't exits.
Most of those are working now, thanks to Apple's support for CUPS. There are PPD files (drivers) available for pretty much any printer out there. Just do a search on OpenPrinting. Granted, there are some really crappy printers that don't work so well without a full-blown Windows install, but they are becoming less common than you seem to think.
On the final note users which do not want to learn little bit about printing and Unix in general will not benefit from using FreeBSD at all. For those users I warmly recommend Windows XP or OS X or if you do not want to pay for OS something like Ubuntu.
And why must someone know anything at all about the LP protocol in order to get printing working?
Yes, people should be willing to learn, and be willing to dig into things, but figuring out a printcap file? That's like telling someone they need to understand how a sendmail.cf file is written by hand in order to use SMTP. Why bother? Just install Postfix and be happy. Same principle here.