public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Norman Rieß" <norman@smash-net.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Network printing
Date: Sat, 10 Jan 2009 13:56:29 +0100	[thread overview]
Message-ID: <49689AFD.70300@smash-net.org> (raw)
In-Reply-To: <200901101215.19510.peter@humphrey.ukfsn.org>

Peter Humphrey schrieb:
>
> Of course it should. It does not. I simply cannot find the necessary 
> invocations and USE flags etc. No matter what I try I cannot get printing 
> to work over the network. I always get a succession of success messages 
> from cups, followed by "printer does not exist" when I try to print a test 
> page. That's a pretty strange definition of success in anybody's book. Even 
> a straightforward postscript laser cannot be made to work now.
>
> I'm going to give it up altogether as a lost cause. Every machine on the 
> network will have to have the printers set up locally, and be carried to 
> where the printers are whenever a print job is needed.
>
> This is one giant black mark for Linux, the ultimate networking OS. I've 
> been using Linux on-and-off for about 15 years, but I'm seriously 
> considering the future of it in this house.
>
> Thanks for trying to help.
>
>   
I read your posts and it sound to me, you try to connect to the printers
instead of your spoolserver.
You say you configured both printers on one server with CUPS-Webpage. I
assume this works and you can print a testpage with the Webpage.
Then you wrote "ServerName yourserver" in /etc/cups/client.conf . You
can now choose both printers in the applicationspecific printmenus, right?

If this is the case and it still does not work, please provide some
logentries.

As one who uses linux for 15 years you should know that cups != linux.

Regards Norman



  reply	other threads:[~2009-01-10 12:56 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ß [this message]
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=49689AFD.70300@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