public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Network printing
Date: Wed, 7 Jan 2009 12:08:12 +0000	[thread overview]
Message-ID: <200901071208.12105.peter@humphrey.ukfsn.org> (raw)
In-Reply-To: <5bdc1c8b0901060904x4ff714fcq4b0f36a08f5e4bc0@mail.gmail.com>

On Tuesday 06 January 2009 17:04:57 Mark Knecht wrote:

>    For the sake of conversation how about emerge flags?

> My server:
>
> [ebuild   R   ] net-print/cups-1.3.9-r1  USE="X acl dbus jpeg ldap pam
> perl png ppds python samba ssl tiff -avahi -gnutls -java -kerberos
> -php -slp -static -xinetd -zeroconf" LINGUAS="en -de -es -et -fr -he
> -id -it -ja -pl -sv -zh_TW" 0 kB
>
> [ebuild   R   ] net-print/hplip-2.8.6b  USE="dbus ppds qt3 qt4
> -cupsddk -doc -fax -minimal -parport -scanner -snmp" 0 kB

Mine:

[ebuild   R   ] net-print/cups-1.3.9-r1  USE="acl dbus jpeg pam perl png 
python ssl 
tiff -X -avahi -gnutls -java -kerberos -ldap -php -ppds -samba -slp -static -xinetd -zeroconf" 
LINGUAS="en -de -es -et -fr -he -id -it -ja -pl -sv -zh_TW"

[ebuild   R   ] net-print/hplip-2.8.6b  USE="cupsddk dbus 
doc -fax -minimal -parport -ppds -qt3 -qt4 -scanner -snmp"

I don't have X set because X is not installed on this server. I may install 
it later. I have cupsddk instead of ppds because hplip's ppds USE flag 
description says it is obsolete and I should use cupsddk instead.

> One of my clients:
>
> [ebuild   R   ] net-print/cups-1.3.9-r1  USE="X acl dbus jpeg ldap pam
> perl png ppds python ssl tiff -avahi -gnutls -java -kerberos -php
> -samba -slp -static -xinetd -zeroconf" LINGUAS="en -de -es -et -fr -he
> -id -it -ja -pl -sv -zh_TW" 0 kB
>
> [ebuild   R   ] net-print/hplip-2.8.6b  USE="dbus ppds qt3 qt4
> -cupsddk -doc -fax -minimal -parport -scanner -snmp" 0 kB

Mine:
[ebuild   R   ] net-print/cups-1.3.9-r1  USE="X acl dbus jpeg pam perl png 
python ssl 
tiff -avahi -gnutls -java -kerberos -ldap -php -ppds -samba -slp -static -xinetd -zeroconf" 
LINGUAS="en -de -es -et -fr -he -id -it -ja -pl -sv -zh_TW"

[ebuild   R   ] net-print/hplip-2.8.6b  USE="cupsddk dbus doc 
qt3 -fax -minimal -parport -ppds -qt4 -scanner -snmp"

The same comment re cupsddk applies on this machine.

----------------------------
On Tuesday 06 January 2009 18:44:46 BRM wrote:

> 1) Modify '/etc/cups/client.conf' and tell it where the server is.

If I do that, will I lose the ability to connect the printer to the client? 
Surely, cups ought to be able to operate with more than one server, no? 
Otherwise, what do all those offices do that have printers connected to 
several workstations and share them all around?

> 2) Configure LP:
>     - use lpstat to see the available printers

Do you have a reason for preferring these two programs to the cups Web 
interface?

On the client, lpstat lists all four: the laser and the deskjet, each 
defined both locally and on the server. I see no reports of any problems.

>     - use lpoptions to set the default printer

Is it necessary to declare a default printer to cups? I thought I'd let 
applications set their own defaults, so that for instance the Deskjet gets 
coloured work and the laser gets word-processor output etc.

> I believe you only need HPLIP on the server side, not the client side.
> But having it there shouldn't do any harm.

It's installed on the client so that I can print locally until I get network 
printing working. I assume that cups on the client will communicate via ipp 
with cups on the server, whatever printer driver is installed between cups 
and the printer. (I believe that the DJ4260 doesn't use the traditional HP 
printer control language, so I'm obliged to use hplip.)

-- 
Rgds
Peter



  reply	other threads:[~2009-01-07 12:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 15:39 [gentoo-user] Network printing Peter Humphrey
2009-01-06 17:04 ` Mark Knecht
2009-01-07 12:08   ` Peter Humphrey [this message]
2009-01-07 14:20     ` BRM
2009-01-10 12:15       ` Peter Humphrey
2009-01-10 12:56         ` Norman Rieß
2009-01-12 10:44           ` Peter Humphrey
2009-01-12 11:24             ` Norman Rieß
2009-01-12 20:12               ` Norman Rieß
2009-01-13 10:38                 ` Peter Humphrey
2009-01-13 14:19                   ` Norman Rieß
2009-01-13 17:46                     ` Peter Humphrey
2009-01-13 18:36                       ` Norman Rieß
2009-01-14  8:58                         ` Mick
2009-01-15 10:39                           ` Peter Humphrey
2009-01-15 14:50                             ` Mick
2009-01-12 14:25             ` BRM
2009-01-13 10:42               ` Peter Humphrey
2009-01-07 15:03     ` Mark Knecht
2009-01-06 18:44 ` BRM
2009-01-19 16:08 ` [gentoo-user] Network printing -- Solved Peter Humphrey
  -- strict thread matches above, loose matches on Subject: below --
2008-12-22 11:25 [gentoo-user] Network printing Peter Humphrey
2008-12-22 18:00 ` BRM
2008-12-23 11:53   ` Peter Humphrey
2008-12-24  0:03     ` Mick
2008-12-24  9:25       ` Peter Humphrey
2008-12-24 10:45         ` Mick
2008-12-24 11:45           ` Peter Humphrey
2008-12-24 19:31             ` Mark Knecht
2008-12-28 12:47               ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200901071208.12105.peter@humphrey.ukfsn.org \
    --to=peter@humphrey.ukfsn.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox