Since your admittedly new to slack I'm going to be a bit verbose and perhaps redundant but this like many other things caused me much difficulty until I sorted it out in my mind. Maybe I can save you a bit of grief, documentation was scarce or poor when I had to nut it out.
I use a slack-10 box as a printserver with cups. if you are networking other linux boxes, that's all you need. You can do without samba and I have even had clients running win-2k accesss the cups server without samba using IPP.
In slackware you have your choice of printer systems (lprng and cups) but you can not have both running at the same time. You may have noticed that you were given a choice when you installed slack. If you nominated , say, CUPS as your printserver then the installer would have made /etc/rc.d/rc.cups executable but not /etc/rc.d/lprng.
If the rc.cups script is executable, cups is started at boot. If for some reasons you change your cups configuration files or something like that you will have to stop/start cups. The commands are /etc/rc.d/rc.cups stop /etc/rc.d/rc.cups start or /etc/rc.d/rc.cups restart as root.
You should be able to access the CUPS interface in anybrowser on the server at port 631 (the same for standalone boxes) Use
http://localhost:631 or 127.0.0.1:631, its the same thing.
As noted above, you can interface with cups in kprinter but I've preferred accesssing cups with a browser for setting up printers and other such stuff and using kprinter for managing the print jobs. Just me, others do it other ways, that's linux, that's choice.
If you have your server configured correctly and printers setup on the cups server, when you open kprinter or go to the printing manager via settings on a client you will see your server's printers listed as available. Note that you will have to nominate CUPS at the bottom of the print manager or kprinter so KDE knows it's working with CUPS
CUPS in slack will work standalone out of the box. You will have to edit the /etc/cupsd.conf file on the server and the /etc/cups/client.conf on an/all clients for networking printshares Once the configuration files are changed you will have stop/start the cups server as explained above.
It took me awhile to sort out what I should have in my cupsd.conf and client.conf files. I'll give you a headstart. You can see what I've done here
http://members.optusnet.com.au/~rick...0configuration and work from that. That's how I started, by grabbing someone else's off the net and fiddling with it till it worked for me. Note that in the example cupsd.conf on the page listed above I am allowing access to one client with ip 192.168.1.2. Things like that will have to be changed to suit your situation in your configuration.
............and Google is your friend!it
