All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Meixner <jsmeix@suse.de>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Automatic printer setup with Printer Applications
Date: Fri, 26 Feb 2021 11:03:34 +0100	[thread overview]
Message-ID: <821b4df56f518b8d2cc38ce846e8cc48@suse.de> (raw)
In-Reply-To: <YDe6L+I0u65ncSXP@shaftnet.org>


Hello

On 2021-02-25 15:54, Solomon Peachy wrote (excerpts):
> 
> And much like we've seen multiple distinct models with
> identical USB VID/PIDs, I've also seen distinct models
> that share identical IEEE1284 IDs. [2]
> And then there's the iManufacturer/iModel/iSerial strings
> that may or may not match what's in the 1284 data
> or what's silkscreened onto the printer itself..
> ...Like everything else involving printing, it's a complete mess.
...
> [2] They are in the same family, but the PDL is barely incompatible..

for some (older) examples that "similar looking model names"
do not mean "same driver works" see the part about
"It is crucial to have exact model names!" in
https://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility

I do not agree that everything involving printing is a complete mess
but I do fully agree that model->driver matching is a complete mess
from which follows "automated printer setup is a complete mess"
so my personal conclusion is:

Stay away from automated printer setup
(unless you like complete mess ;-)

I am looking forward to the future where proper
IPP (Everywhere) printer devices provide all what is needed
(including spooling and handling many clients simultaneously)
so neither printer drivers (and their setup)
nor spooling services (and their setup)
are needed any longer.
Only clients that properly talk IPP directly to
IPP printer devices that properly provide IPP.


Kind Regards
Johannes Meixner
-- 
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5 - 90409 Nuernberg - Germany
(HRB 36809, AG Nuernberg) GF: Felix Imendoerffer

  reply	other threads:[~2021-02-26 10:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 19:27 [Printing-architecture] Automatic printer setup with Printer Applications Till Kamppeter
2021-02-24  7:37 ` Johannes Meixner
2021-02-24  8:03 ` Zdenek Dohnal
2021-02-24 11:25   ` Till Kamppeter
2021-02-24 12:01     ` Johannes Meixner
2021-02-24 13:51       ` Till Kamppeter
2021-02-25 10:30         ` Johannes Meixner
2021-02-25 13:37           ` Till Kamppeter
2021-02-25 14:00             ` Johannes Meixner
2021-02-25 13:53           ` Michael Sweet
2021-02-24 12:48     ` Solomon Peachy
2021-02-24 14:01       ` Johannes Meixner
2021-02-24 17:23         ` Till Kamppeter
2021-02-26  9:17           ` Johannes Meixner
2021-02-24 14:17       ` Till Kamppeter
2021-02-25 15:28         ` Solomon Peachy
2021-02-25 22:54           ` Till Kamppeter
2021-02-26 14:59             ` Solomon Peachy
2021-02-25  8:28       ` Zdenek Dohnal
2021-02-25 14:54         ` Solomon Peachy
2021-02-26 10:03           ` Johannes Meixner [this message]
2021-02-26 12:28             ` Solomon Peachy
2021-02-27 21:07               ` Michael Sweet
2021-02-24 14:17 ` Michael Sweet
2021-02-24 14:46   ` Johannes Meixner
2021-02-24 18:47     ` Till Kamppeter
2021-02-24 17:40   ` Till Kamppeter
2021-02-24 17:48     ` Michael Sweet
2021-02-24 19:21       ` Till Kamppeter
2021-02-24 20:01         ` Michael Sweet
2021-02-24 20:15           ` Till Kamppeter
2021-02-25  8:52   ` Zdenek Dohnal
2021-02-25  9:24     ` Till Kamppeter
2021-02-25  9:54       ` Zdenek Dohnal
2021-02-25 13:43       ` Michael Sweet
2021-02-25 19:39         ` Till Kamppeter
2021-02-25 13:33     ` Michael Sweet
2021-02-25 15:24       ` Till Kamppeter
2021-02-25 15:30         ` Michael Sweet
2021-02-25 21:51           ` Till Kamppeter
2021-03-02 10:58 ` [Printing-architecture] Future of Printer Setup Tools Till Kamppeter
2021-03-02 12:04   ` Johannes Meixner
2021-03-02 22:52     ` Till Kamppeter

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=821b4df56f518b8d2cc38ce846e8cc48@suse.de \
    --to=jsmeix@suse.de \
    --cc=printing-architecture@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.