public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lee <ny6p01@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Getting printer working, the road of Pain.
Date: Thu, 8 Sep 2022 13:24:02 -0700	[thread overview]
Message-ID: <CABpw4G8BROn4ZGTQ3mjHt4y0Pny48D8OR9d=PRq0oYSgxJgWyQ@mail.gmail.com> (raw)
In-Reply-To: <20220908200442.013cd5d7@ventiloplattform.tastytea.de>

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

Who needs to go to the hassle maintaining a printer of their own, buying
cartridges, paper etc? I set up an online account at my neighborhood
Kinkos, and I just upload whatever docs I need and they print out in HD
whatever I need for pennies a page. Ymmv.

Lee 😎

On Thu, Sep 8, 2022, 11:05 AM tastytea <gentoo@tastytea.de> wrote:

> On 2022-09-08 12:52-0400 Alan Grimes <alonzotg@verizon.net> wrote:
>
> > […]
> >
> > Right now linux is so broken that the CUPS web interface will deny
> > all attempts to administer the printer and reject any password. The
> > config file is written in moonspeak, I just need the motherfucking
> > thing to say yes when I tell it to do a thing. I expect it to take
> > 2-3 days just to get over this hurdle.
>
> I solved this problem by replacing the contents of every <Location>
> block with:
>
>   Order allow,deny
>   Allow localhost
>   Allow from fd69:0:0:0:*
>   Allow from 192.168.69.*
>
> > How can people actually go around installing linux on people's
> > computers as if they were doing them a favor when it really is this
> > bad?
>
> It's not bad at all if you use a distribution with a better default
> configuration, pre-installed drivers and a pre-installed GUI for setting
> up the automatically detected printer in less than 5 clicks.
> Unless you have a printer from a shitty company, of course.
>
>

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

  parent reply	other threads:[~2022-09-08 20:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9b267743-3c9e-86dd-31f7-631b116dc251.ref@verizon.net>
2022-09-08 16:52 ` [gentoo-user] Getting printer working, the road of Pain Alan Grimes
2022-09-08 18:04   ` tastytea
2022-09-08 19:24     ` Michael
2022-09-08 20:24     ` Lee [this message]
2022-09-08 20:40       ` Wols Lists
2022-09-08 22:56         ` Peter Humphrey
2022-09-09 11:50           ` David M. Fellows
2022-09-08 22:10   ` Ramon Fischer
2022-09-10  0:18   ` Paul Colquhoun
2022-09-10  8:09     ` Wols Lists
2022-09-10  9:59       ` karl
2022-09-10 15:32       ` [gentoo-user] " Grant Edwards

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='CABpw4G8BROn4ZGTQ3mjHt4y0Pny48D8OR9d=PRq0oYSgxJgWyQ@mail.gmail.com' \
    --to=ny6p01@gmail.com \
    --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