Simon L. Nielsen
simon at FreeBSD.org
Sat May 15 13:01:51 UTC 2004
On 2004.05.15 20:33:47 +0800, Robert Storey wrote:
> I've written up a little HOW-TO for getting CUPS and up and running, and I'd
> happy if it got appended to the current CUPS introduction in the Manual. So
> without further ado, below is what I've written. I'd appreciate any feedback.
I haven't used CUPS, so my comments might reflect that.
> STEP 1: For those who rebuild world every now and then, it might be best to add
> this to /etc/make.conf before building world and installing CUPS:
> However, the above is not mandatory.
You should note what each option actually does, and why it's a good idea
to have use them.
> STEP 2: Installing CUPS from PORTS
> You've got to install four packages from ports. You can find them here:
> The first port - /usr/ports/print/cups - is a meta-port, so installing it should
> install the others.
If it's enough to install the first port I don't think the others should
be mentioned, or at least it should be explained why one might want to
install the non-metaports and not the metaport.
> STEP 4: FreeBSD-specific Issue
> On FreeBSD, CUPS stores its executable files in /usr/local/bin/ whereas the
> traditional lp executables are in /usr/bin/. Because /usr/bin/ is in the command
Won't CUPS_OVERWRITE_BASE replace the standard lp* utitilies i /usr/bin
? (Just a guess since the what other make variabels with similar names
> path before /usr/local/bin/, your CUPS files will not be able to execute. For
> # which lpr
> This problem is handily solved by making file /usr/bin/lp* non-executable, like
> chmod -x /usr/bin/lp*
> Now, try the previous command again:
> # which lpr
> Success! This is what we want.
It should be noted that a new installworld will set the execuateable bit
again if people don't have NO_LPR in make.conf.
> STEP 6: Configuring the Printer
> This part is just like Linux. Open up a browser (Mozilla or Konqueror will do)
> and type this url:
> This will bring you to the CUPS configuration menu. You'll be asked to login
> (login as root and use the root password), then it's simple point-and-click
> operation that you should be able to figure out yourself.
> STEP 7: Configuring a CUPS Server and Client
> If you want to enable network printing on your LAN, you've got a little more
> work to do. Assuming that the FreeBSD box is the print server, edit file
> /usr/local/etc/cups/cupsd.conf and make two changes. The two changes vary
> according to how your network is configured, but for a typical Class C network,
> this should work:
> # broadcast address
> BrowseAddress @LOCAL
> <Location />
> Allow From 192.168.0.0/24
> Instead of @LOCAL, we could have specified a broadcast address, such as
> 192.168.0.255 (again, that's for a Class C network). And rather than
Since Class networks are depricated I would just say a "/24" or
something like that. If people know of Class A/B/C they probably also
> 192.168.0.0/24 (the whole network), we could have specified just a single client
> machine (such as 192.168.0.3).
> Once you have made the above changes, restart the CUPS daemon:
> /usr/local/etc/rc.d/cups.sh restart
> Now go to the client machine, open your browser, type http://localhost:631, and
> click the button "Print test page" - it should work.
Hmm, don't the cliean need to install something? E.g. entire CUPS or
some part of CUPS? And 'm certain the client need to set up something to
point at the print server.
It will be much faster to get your submission added if you write it in
DocBook SGML and send a diff as noted in the FreeBSD Documentation
Since CUPS is getting more popular I think it's good to have something
like this in the Handbook.
Simon L. Nielsen
FreeBSD Documentation Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
More information about the freebsd-doc