From: "Norman Rieß" <norman@smash-net.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Network printing
Date: Tue, 13 Jan 2009 15:19:27 +0100 [thread overview]
Message-ID: <496CA2EF.4080800@smash-net.org> (raw)
In-Reply-To: <200901131038.57687.peter@humphrey.ukfsn.org>
Peter Humphrey schrieb:
> On Monday 12 January 2009 20:12:16 Norman Rieß wrote:
>
>
>> So here is the screenshot.
>> http://www.smash-net.org/bilder/cups.png
>> Notice: loki is the client and asgard is the server connected to the
>> printer.
>>
>> The upper left shell shows the configuration cupsd.conf on the _server_.
>> You see the "Allow ...." statements in the "Location"-tags. These
>> statements configure which IP's shall be allowed to print and browse the
>> configuration-webpage.
>> In the browser you see the webpage on the server. I am sorry it is in
>> german, but i guess you will get the point. You see the printer
>> connected and configured there.
>> That is all on the serverside.
>>
>> Bottom left you see a cat of the client.conf with its only statement,
>> the cupsserver. You do _not_ configure printers here!
>> You see the lpstat sees the printer on the server. And you see the gedit
>> printingdialog sees the printer.
>>
>
> Thanks. That's exactly what I have. Do you have ldap in your print server's
> cups USE flags? Or gnutls?
>
>
These are my flags:
USE="-X -gtk -gtk2 -qt3 -qt4 -gnome -kde unicode nls samba mmx sse 3dnow
-mysql"
USE="3dnow acl apache2 berkdb bzip2 cli cracklib crypt cups dri fortran
gdbm gpm iconv ipv6 isdnlog ldap mailwrapper midi mmx mudflap ncurses
nls nptl nptlonly openmp pam pcre perl pppd python readline reflection
samba session snmp spl sse ssl sysfs tcpd truetype unicode x86 xml xorg
zlib"
package.use
net-print/cups jpeg nls pam png ppds ssl tiff X
next prev parent reply other threads:[~2009-01-13 14:19 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
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ß [this message]
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=496CA2EF.4080800@smash-net.org \
--to=norman@smash-net.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