Re: brltty=huge distraction for folks that don't need it.

2022-01-04 Thread Pierre-Elliott Bécue
gene heskett wrote on 03/01/2022 at 02:24:53+0100: > On Sunday, January 2, 2022 5:58:44 PM EST Pierre-Elliott Bécue wrote: >> gene heskett wrote on 02/01/2022 at 23:53:19+0100: >> > Greetings All; >> > >> > Without any conscious prompting by me, te debian 11.1 netinstall for >> > x86-64 syste

Mystery Printer

2022-01-04 Thread A_Man_Without_Clue
Hi all, I have a printer, Brother DCPJ562N connected to the Debian Buster PC via USB. Brother printer driver is installed. This printer is shared on the wired network. Now, today I was trying to print the document from another PC (Debian Bullseye) and it did print it normally. But then I rea

[SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread local10
Jan 4, 2022, 05:58 by to...@tuxteam.de: > Seems to work for me (currently). Are you still getting the error? > Not anymore, it has been solved:  https://lists.debian.org/debian-user/2022/01/msg00096.html Thanks to everyone who responded.

Re: Mystery Printer

2022-01-04 Thread john doe
On 1/4/2022 12:18 PM, A_Man_Without_Clue wrote: Hi all, I have a printer, Brother DCPJ562N connected to the Debian Buster PC via USB. Brother printer driver is installed. This printer is shared on the wired network. Now, today I was trying to print the document from another PC (Debian Bullseye)

Re: Mystery Printer

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 08:18:21PM +0900, A_Man_Without_Clue wrote: > Hi all, > > I have a printer, Brother DCPJ562N connected to the Debian Buster PC via ^^^ > USB. Brother printer driver is installed. This printer is shared on the > wired network. > > Now, toda

Re: Mystery Printer

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 01:10:32PM +0100, john doe wrote: [...] > Looks like you have a network printer the 'N' in the model name. > So my guess is that your printer is connected to your network. [...] > I would say yes if you have a network printer (wireless/wired). Our answers crossed in the

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 12:50:39PM +0100, local10 wrote: > Jan 4, 2022, 05:58 by to...@tuxteam.de: > > > Seems to work for me (currently). Are you still getting the error? > > > > > Not anymore, it has been solved:  > https://lists.debian.org/debian-user/2022/01/msg00096.html > > Thanks to eve

Re: Mystery Printer

2022-01-04 Thread David
On Tue, 4 Jan 2022 at 22:18, A_Man_Without_Clue wrote: > I have a printer, Brother DCPJ562N connected to the Debian Buster PC via > USB. Brother printer driver is installed. This printer is shared on the > wired network. > Now, today I was trying to print the document from another PC (Debian > B

Re: Mystery Printer

2022-01-04 Thread A_Man_Without_Clue
On 1/4/22 21:15, to...@tuxteam.de wrote: On Tue, Jan 04, 2022 at 01:10:32PM +0100, john doe wrote: [...] Looks like you have a network printer the 'N' in the model name. So my guess is that your printer is connected to your network. [...] I would say yes if you have a network printer (wire

GUIs (was: Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com)

2022-01-04 Thread rhkramer
On Tuesday, January 04, 2022 12:58:45 AM to...@tuxteam.de wrote: > [1] Don't you hate GUIs? Describing how to do a simple thing ends up in >reams of difficult-to-understand text. +1 sometimes, but sometimes they offer a much easier way to do things with less learning required -- there is a tr

Re: brltty=huge distraction for folks that don't need it.

2022-01-04 Thread rhkramer
On Tuesday, January 04, 2022 05:20:34 AM Pierre-Elliott Bécue wrote: > gene heskett wrote on 03/01/2022 at 02:24:53+0100: > > The first time I tried to remove brltty, the removal cascaded all the > > way up thru all of gnome and xorg. Scary. > > I think you probably tried to kill something else w

Re: brltty=huge distraction for folks that don't need it.

2022-01-04 Thread Pierre-Elliott Bécue
rhkra...@gmail.com wrote on 04/01/2022 at 14:52:00+0100: > On Tuesday, January 04, 2022 05:20:34 AM Pierre-Elliott Bécue wrote: >> gene heskett wrote on 03/01/2022 at 02:24:53+0100: >> > The first time I tried to remove brltty, the removal cascaded all the >> > way up thru all of gnome and xorg

Re: GUIs (was: Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com)

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 08:50:23AM -0500, rhkra...@gmail.com wrote: > On Tuesday, January 04, 2022 12:58:45 AM to...@tuxteam.de wrote: > > [1] Don't you hate GUIs? Describing how to do a simple thing ends up in > >reams of difficult-to-understand text. > > +1 sometimes, but sometimes they offe

Re: Reasonably simple setup for 1TB HDD and 250GB M.2 NVMe SSD

2022-01-04 Thread Michael Stone
On Mon, Jan 03, 2022 at 08:51:59PM -0300, Jorge P. de Morais Neto wrote: But doesn't Btrfs compression work with small blocks? https://btrfs.wiki.kernel.org/index.php/Compression#Are_there_speed_penalties_when_doing_random_access_to_a_compressed_file.3F Relatively small, which makes it fairly

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread Michael Stone
On Tue, Jan 04, 2022 at 01:09:06AM +0100, local10 wrote: Jan 3, 2022, 23:08 by d...@randomstring.org: Alright. Put this into your /etc/hosts temporarily: [...] OK, I understand now what the problem was. Quite a while ago I added a line into the /etc/hosts to fix a temp DNS issue and completel

Re: brltty=huge distraction for folks that don't need it.

2022-01-04 Thread Michael Stone
On Tue, Jan 04, 2022 at 08:52:00AM -0500, rhkra...@gmail.com wrote: On Tuesday, January 04, 2022 05:20:34 AM Pierre-Elliott Bécue wrote: gene heskett wrote on 03/01/2022 at 02:24:53+0100: > The first time I tried to remove brltty, the removal cascaded all the > way up thru all of gnome and xorg

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread James H. H. Lampert
On 1/4/22 10:19 AM, Michael Stone wrote: And this is why putting stuff into /etc/hosts is basically never the right answer. :) Au contraire! Among other things, the host table is the best possible place to block access to certain unwanted domains. For example, if you add these entries: > 0.

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote: [...] > And this is why putting stuff into /etc/hosts is basically never the right > answer. :) Eye, beholder and things. I've got a couple of them like so: # Pest: 127.0.0.1 www.google-analytics.com 127.0.0.1 ajax.google.com

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 10:34:48AM -0800, James H. H. Lampert wrote: > On 1/4/22 10:19 AM, Michael Stone wrote: > > And this is why putting stuff into /etc/hosts is basically never the > > right answer. :) > > Au contraire! > > Among other things, the host table is the best possible place to bloc

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread local10
Jan 4, 2022, 18:19 by mst...@debian.org: > And this is why putting stuff into /etc/hosts is basically never the right > answer. :) > I think it's fine as long as one is aware of what one is doing. I should have caught it sooner but due to other circumstances I was under a false impression that

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread David Wright
On Tue 04 Jan 2022 at 19:37:34 (+0100), to...@tuxteam.de wrote: > On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote: > > [...] > > > And this is why putting stuff into /etc/hosts is basically never the right > > answer. :) > > Eye, beholder and things. I've got a couple of them like

Re: why bash completion sometimes doesn't work?

2022-01-04 Thread David Wright
On Mon 03 Jan 2022 at 21:22:44 (-0500), Greg Wooledge wrote: > On Mon, Jan 03, 2022 at 11:56:57PM +, Long Wind wrote: > > Thank Greg and David! > > > > i type "ifdown ", it add lo automatically, > > wireless device isn't shown, though wireless connection works well > > > > i think "ip a" can

Re: Replace line in file based on pattern

2022-01-04 Thread David Wright
On Mon 03 Jan 2022 at 08:38:32 (-0500), Paul M. Foster wrote: > On 1/2/22 11:03 PM, Greg Wooledge wrote: > > On Sun, Jan 02, 2022 at 09:59:08PM -0500, Paul M. Foster wrote: > > > Regarding "patch", let's consider a "stock" config file from a fresh > > > install > > > (call it NEW), and an existing

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread James H. H. Lampert
On 1/4/22 11:33 AM, David Wright wrote: In fact, I was quite shocked when I just tried DNS over HTTPS for a couple of minutes. The 10-day weather profile that I screenshoot every day was plastered in popups. Anyone know how to combine DoH with resolving 14,000 addresses to 127.0.0.1? Also, does

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 01:33:18PM -0600, David Wright wrote: > On Tue 04 Jan 2022 at 19:37:34 (+0100), to...@tuxteam.de wrote: > > On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote: > > > > [...] > > > > > And this is why putting stuff into /etc/hosts is basically never the right > >

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread Michael Stone
On Tue, Jan 04, 2022 at 10:34:48AM -0800, James H. H. Lampert wrote: On 1/4/22 10:19 AM, Michael Stone wrote: And this is why putting stuff into /etc/hosts is basically never the right answer. :) Au contraire! Among other things, the host table is the best possible place to block access to c

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread Celejar
On Tue, 4 Jan 2022 20:58:27 +0100 wrote: > On Tue, Jan 04, 2022 at 01:33:18PM -0600, David Wright wrote: > > On Tue 04 Jan 2022 at 19:37:34 (+0100), to...@tuxteam.de wrote: > > > On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote: > > > > > > [...] > > > > > > > And this is why putti

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread Dan Ritter
David Wright wrote: > On Tue 04 Jan 2022 at 19:37:34 (+0100), to...@tuxteam.de wrote: > > On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote: > > > > [...] > > > > > And this is why putting stuff into /etc/hosts is basically never the right > > > answer. :) > > > > Eye, beholder and

reduce size of debian-live-11.1.0-amd64-xfce+nonfree.iso installation

2022-01-04 Thread David Christensen
debian-user I installed debian-live-11.1.0-amd64-xfce+nonfree.iso and updated onto a amd64 computer for graphical desktop usage (e.g. "daily driver"): 2022-01-04 17:57:07 root@laalaa ~ # cat /etc/debian_version ; uname -a 11.2 Linux laalaa 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x

Cursor theme switched to Breeze without apparent notice

2022-01-04 Thread The Wanderer
Mostly-short version: How can I figure out what package change resulted in my system changing to use a different cursor theme, and how can I revert it as completely as possible? Full-length version (or something like it): I recently rebooted for the first time since November 19th (there was a p

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 04:05:11PM -0500, Celejar wrote: [...] > One way "to combine DoH with resolving 14,000 addresses to 127.0.0.1" > is by using Pi-hole. Some people have *millions* of domains blacklisted > in Pi-hole: Pi-hole won't help unles it also does HTTPS proxying (that means it would

Re: [SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

2022-01-04 Thread tomas
On Tue, Jan 04, 2022 at 04:09:42PM -0500, Dan Ritter wrote: [...] > Here's what I do: > > My local DNS resolver offers DNS, DNS over TLS, and DNS over > HTTPS. > > I supply a use-application-dns.net zone that returns NXDOMAIN. > That tells browsers to not use DoH. Oh, is it possible to tell th