Date: Mon, 20 Apr 2009 12:39:39 -0300 From: Ramiro Caso <misha_78@hotmail.com> To: <weif@weif.net>, <freebsd-questions@freebsd.org> Subject: RE: Can you ACTUALLY print from FreeBSD? Message-ID: <BAY102-W3863095A02EA60C72761F5E1760@phx.gbl> In-Reply-To: <20090420145839.5D396A3DC7@maxine.cjones.org> References: <20090420145839.5D396A3DC7@maxine.cjones.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm trying to print from my FreeBSD machine. I've been through a > number of online tutorials and instructions on printing from Unix or > FreeBSD in particular=2C but they all seem to start with the assumption > that printing from the machine is possible. I'm trying to get to that > starting point. >=20 > I have installed: >=20 > cups-base-1.3.9_3 Common UNIX Printing System > cups-pdf-2.5.0 A virtual printer for CUPS to produce PDF files > cups-pstoraster-8.15.4_2 Postscript interpreter for CUPS printing to non-= PS printers > gutenprint-cups-5.1.7_3 GutenPrint Printer Driver > libgnomecups-0.2.3_1=2C1 Support library for gnome cups admistration > hplip-2.8.2_4 Drivers and utilities for HP Printers and All-in-One = device >=20 > The printer I'm working with is a HP Officejet 4110. >=20 >=20 > There seem to be several issues with printing. First=2C since this is a > USB printer=2C the pinter is always owned by root:operator with read > permissions for user=2C group=2C and world. >=20 > Adding these lines to /etc/devfs.conf > link ulpt0 printer > own ulpt0 cups:cups > perm ulpt0 0666 >=20 > will set the ownership to cups:cups and the permissions to read and > write for user=2C group=2C and world on startup if the printer is already > turned on and plugged in. However=2C if the printer is not turned on at > startup=2C or if it is disconnected or turned off after system startup=2C > ownership and permissions revert. >=20 > Trying chown or chmod to the device at /dev/ulpt0 gives an invalid > path error=2C and trying to do so following the instructions in the man > page for devfs give 'operation not supported by device' errors. > > When th device is owned by root=2C attempting to print the test page > generates a 'permission denied' error in CUPS. When the device is > owned by cups=2C attempting to print the test page generates a "failed" > error in CUPS. >=20 > When the device is owned by cups=2C this error is reported in the error > log in CUPS=2C if debug logging is enabled: >=20 > [CGI] /usr/local/share/cups/drivers/pscript5.dll: No such file or directo= ry >=20 > There isn't a drivers directory in /usr/local/share/cups. I can make > one=2C but where do I get the pscript5.dll=2C and what else is it going t= o > rely on? >=20 > CUPS et al were installed using portinstall=2C and CUPS is working well > to produce .pdf files. I tried portupgrade last night on all the (I > think) relevant ports=2C but the system thinks they are all up to date. >=20 > So=2C questions: >=20 > 1. how can I get permissions on the device to stick=2C so that I do not > have to reboot the machine every time we want to print or have to > power cycle the printer? You should use /etc/devfs.rules instead=2C adding something like: add path 'ulpt*' mode 0660 group cups This will set the right permissions when the node is created. > 2. Am I correct that the missing .dll (that seems awfully Windows to > me) is the problem in getting a filter to print? If so=2C what do I > need to do to install it? >=20 >=20 > And=2C actually=2C a third printing-related issue: How do I get cupsd to > start on startup? I have these two lines in /etc/rc.conf:\ >=20 > cupsd_enable=3D"YES" # enable cups printing management > devfs_system_ruleset=3D"system" # something else they say cups needs >=20 > but CUPS has to be manually started by root after each reboot. what > else needs to be done to get cupsd to start at startup? >=20 > Keith > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe=2C send any mail to "freebsd-questions-unsubscribe@freebsd= .org" _________________________________________________________________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY102-W3863095A02EA60C72761F5E1760>