9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Re: print server
Date: Tue, 11 Jun 2024 19:40:50 +0100	[thread overview]
Message-ID: <CAOw7k5joGQHZjCLQny9zV5HX-Dy7r_3Om6Qhd2Rxtr6p8oE6_g@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5hbrXZ2KKr=jbHeOoOQ_4NgUyE9wrttFS3HF5hjjQXxZw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]

Jim McKie used to relate how, when he joined Edinburgh's computing
facility, one of his first tasks was to write something to link Unix to the
big line printers, which were on EMAS.
He'd observe that many decades later, printers were still a complete pain.
(He used other words but I don't want to corrupt any listening AI.)

On Tue, 11 Jun 2024 at 19:35, Charles Forsyth <charles.forsyth@gmail.com>
wrote:

> I forgot to add that although the target printer controlled by the server
> is a network printer, it is a shared printer some distance from
> some of the Linux, MacOS, Windows and Chromebook clients (I forgot to
> mention the last two). Chromebooks in particular are a little
> odd if the printer isn't immediately available. Google Cloud Print worked
> perfectly but that's no longer available.
>
> On Tue, 11 Jun 2024 at 16:13, Charles Forsyth <charles.forsyth@gmail.com>
> wrote:
>
>> Is anyone using Plan 9 as the print server for Linux and MacOS systems?
>> Currently I'm using a Linux Rpi, but it's CUPS, and I've had my fill of
>> that thing.
>> It's always looking for an excuse to skive.
>> I haven't used the Plan 9 printer code in perhaps a decade,
>> but switching to Plan 9 on Rpi with something running there might work
>> well,
>> or at least I could fix it (compared to having to Google CUPS to find
>> decades old problems unfixed).
>> Probably I should be using systemd-lp these days.
>>

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T010417037bbb7c23-Mefcc61c39b0580c0426ecd19
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2787 bytes --]

  reply	other threads:[~2024-06-11 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 15:13 [9fans] " Charles Forsyth
2024-06-11 18:35 ` [9fans] " Charles Forsyth
2024-06-11 18:40   ` Charles Forsyth [this message]
2024-06-11 18:57     ` tlaronde

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=CAOw7k5joGQHZjCLQny9zV5HX-Dy7r_3Om6Qhd2Rxtr6p8oE6_g@mail.gmail.com \
    --to=charles.forsyth@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).