You will find that HTML email is not taken kindly here, please do not use it on this list. On Thu, 2006-03-23 at 14:20 -0500, L. Mark Stone wrote:
Just set up a new SuSE 10 Pro Box to perform as a file and print server. We noticed what we think is a defect in the YaST-created configs, and so I am asking here for advice as to whether I should open a bug for this on opensuse.org, please. I have no idea if this is set up the same way in 10.1, which we have not tested. After we set up Samba, cups and configured a printer attached to the box, we attempted to add this printer as a network printer to a WinXP Pro box. Without getting in to a religious war about raw vs. other forms of printing, our preferred printer setup method for most printers in small networks is to copy the SuSE ppd file to a network share, and then use the free Adobe Postscript printer driver installer and the ppd file to create network printers on each Windows workstation. OK, the printer installed fine on the Windows workstation but when we went to print, we got raw text spewing out of the printer. We noticed that in /etc/smb.conf in the global section there is a line "cups optons = raw". We commented out that line, restarted Samba and all was well. But, we also noticed that the lines in /etc/cups/mime.convs and /etc/cups/mime.types necessary for cups to support raw printing were commented out. In other words, the default SuSE Samba/cups printing setup is broken as Samba is configured for raw printing but cups is not. Both sides need to be configured to support the same type of printing for Samba printing to work without having to manually edit one or more files. This is more of a "fit 'n finish" issue and not a broken code problem, but is this the sort of thing that in your experience deserves a bug report to be filed?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998