From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting printer working, the road of Pain.
Date: Thu, 08 Sep 2022 20:24:07 +0100 [thread overview]
Message-ID: <13096506.uLZWGnKmhe@lenovo.localdomain> (raw)
In-Reply-To: <20220908200442.013cd5d7@ventiloplattform.tastytea.de>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
On Thursday, 8 September 2022 19:04:42 BST tastytea 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.
You'll need the right drivers for the printer you have. This page is a good
start for CUPS and usually it doesn't take long to connect to the printer and
start printing.
https://wiki.gentoo.org/wiki/Printing
Modern printers invariably offer their own http(s) web GUI for administration,
which may also need configuring, but just printing alone should be achievable
by using the guidance in the wiki above.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-08 19:24 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 [this message]
2022-09-08 20:24 ` Lee
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=13096506.uLZWGnKmhe@lenovo.localdomain \
--to=confabulate@kintzios.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