[RESOLU] Re: Comment ajouter à Firefox le moteur de recherche Debian Package Search ?

2022-01-26 Thread Olivier
En effet, le module Debian Queries reprend et développe les fonctions
assurées par le mdoule Debian Package Search.

Merci infiniment !

Le mer. 26 janv. 2022 à 19:43, Lamourec Alain  a écrit :
>
> Il faut ajouter l'extension (add-on) Debian queries par
> outils/Modules complémentaires
>
> Cordialement
>
> Olivier writes:
>
> > Bonjour,
> >
> > Je viens d'installer une nouvelle machine Bullseye.
> > Je note que Firefox n'y intègre pas le moteur de recherche
> > Debian
> > Package Search qui permet de retrouver des paquets dans les
> > dépôts
> > Debian.
> >
> > Comment ajouter ce moteur ?
> > J'ai trouvé [1] puis [2] mais je n'arrive pas à suivre les
> > instructions.
> >
> > [1] https://forums.debian.net/viewtopic.php?p=723242
> > [2]
> > https://mycroftproject.com/install.html?id=19956=all-debian-packages=ico=Debian+Packages+-+Names+%28All%29
> >
> > Slts
>
>
> --
> Lamourec Alain
>



Miracast, Chromcast ?

2022-01-26 Thread ptilou
slt,

heureusement que le système d’écran par réseau est supporté, sur le stick de 
Jeff, l’image est de mauvaise qualité ….

Par contre j’ai vu un Debiantiste installer sur Kindle, debian, je crois que 
c’est de l’arm, et donc sur le type miracast chromcast, quelqu’un a réussi à 
installer debian ?
Je pense que tu m’es un disque dur su le port usb de la box du FAI, et ça fait 
le home, ou mieux un cloud comme online, mais y a un seul usb sous forme de 
mini comme les smartphone, donc faut soit un d’ongle bluetooth qui supporte les 
périphériques d’entrée!

quelqu’un a vue quelque chose ?

merci

— 
ptilou



Re: how to test and compare performance of bullseye for i386 and amd64

2022-01-26 Thread a

Thank David!

my mail provider blocks your reply without informing me, so i can't 
receive it on time, i get your reply by some other way


it's amazing that you get my history of getting help here,

actually i've just bought 2nd-hand pc, it's core2 Q8200, 2.33G, it's my 
fastest pc though others might think it's slow. and i'm interested in 
its performance.  my motive behind this purchase is to solve slow 
reading PDF


as to firmware complaint, i think problem is with debian, not with me, 
because other major distro (opensuse and fedora) include non-free 
firmware in their official release. but i won't switch to other distro 
for such small incontinence





Re: system freeze older iMac Debian 11

2022-01-26 Thread Charles Curley
On Wed, 26 Jan 2022 16:52:55 -0800
"Robert F. Crochelt"  wrote:

> Can't even
> shift to a different console with ctrl-F_.

Try ctl-alt-F_.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread David Wright
On Wed 26 Jan 2022 at 18:56:17 (+0100), Andrei POPESCU wrote:
> On Mi, 26 ian 22, 11:55:36, Greg Wooledge wrote:
> > On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote:
> > > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
> > > should tell you that I don't have that file either, but I downloaded
> > > dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this.
> > > And if I type "man" into google, I get a list of previously sought
> > > man pages as the response, rather than "camera tv".
> > 
> > Why not just use
> > ?

For pasting the manpage extracts? That's simple. In
https://lists.debian.org/debian-user/2022/01/msg01055.html
Gene quoted "the bottom of /etc/dhcpcd.conf" so I needed to
see that file.

  $ apt-file find /etc/dhcpcd.conf
  dhcpcd5: /etc/dhcpcd.conf 
  $ 

Have I got, or ever even seen, package dhcpcd5? Leaving off the
5 in case it's a version number:

  $ grep -r dhcpcd /home/debian/packages/ ~/pc/configure/out-of-date/dpkg-l-*
  $ 

No—never installed it, going back as far as hamm. So, off to
  https://packages.debian.org/index
to get the link, and wget downloads the package into
/home/debian/bullseye/dhcpcd5_7.1.0-2+b1_amd64.deb
as there's no point in apt-get -d putting it into my cache.
(Besides, I'm here sitting at a buster machine.)

Then mc opens the .deb file as if it were a local directory.
Everything's there: the configuration file itself, and all
the docs, including the manpage(s).

So why use ?

Cheers,
David.



Re: Screen goes blank for 1-2 seconds

2022-01-26 Thread Bijan Soleymani
On 2022-01-26 11:35 p.m., Pankaj Jangid wrote> I don’t want to file any 
bug report till I have some concrete data. So

my question is - how do I diagnose such an issue and produce some data
for debugging. So that I can hand it over to maintainers.


This one line script will sleep for 0.01 seconds at a time and then 
print the current time in milliseconds to a file.


while `true`; do sleep 0.01; date +"%T.%3N" ; done > time.txt

Run that and look at the output in time.txt afterwards to make sure the 
system didn't actually stop. (even if it stopped it might still be a 
graphics issue, but at least it's another data point).


Output will look like:
23:41:20.670
23:41:20.686
23:41:20.701
23:41:20.715
23:41:20.732
23:41:20.749
23:41:20.766
23:41:20.785
23:41:20.803
23:41:20.821

(due to the overhead of running sleep and date there's more than 0.01 
seconds per iteration)


This script will give you the biggest time differences:
perl -e 'while(<>){chomp; $old_time = $time; $time = $_; $old_ms = 
$cur_ms ; $_ =~ s/.*[.]//; $cur_ms = $_; $delta = $cur_ms - $old_ms; 
$delta = $delta % 1000; if (defined($old_ms)){print "$delta: $old_time 
$time\n";}}' < time.txt  | sort -n | tail


The output is:
20: 23:50:50.384 23:50:50.404
20: 23:50:51.036 23:50:51.056
20: 23:51:06.262 23:51:06.282
20: 23:51:46.577 23:51:46.597
21: 23:50:42.553 23:50:42.574
21: 23:50:43.999 23:50:44.020
24: 23:50:59.126 23:50:59.150
25: 23:50:41.680 23:50:41.705
25: 23:50:50.192 23:50:50.217
25: 23:50:53.255 23:50:53.280

So in my case the biggest delay was 25ms (at time 23:50:53). If you see 
anything longer than 100ms you'll know the system has gotten stuck 
during the blank interval.


Bijan



PS1 and $-, a footnote; was Re: .profile not being src'd at login on uptodate buster

2022-01-26 Thread David Wright
On Mon 12 Apr 2021 at 11:26:49 (-0400), Greg Wooledge wrote:
> On Mon, Apr 12, 2021 at 10:18:19AM -0500, David Wright wrote:
> > I'm not using PS1 to test whether stdout is a terminal, but whether
> > the file is running interactively. From man bash:
> > 
> >   "PS1 is set and $- includes i if bash is interactive, allowing a
> >   shell script or a startup file to test this state.
> 
> The second half of that sentence is referring to the $- part.  That's
> what you're supposed to test to see whether the shell is interactive.
> 
> # bash
> if [[ $- = *i* ]]; then
>   echo "I am an interactive shell"
> echo 
> 
> # sh
> case $- in
>   *i*) echo "I am an interactive shell" ;;
> esac

I happened to come across one place where I might have originally
found the construction I no longer use, and that's in   man lesspipe,
very near the end, where it says:

  if [ -z "$PS1" ]; then

Cheers,
David.



Re: Screen goes blank for 1-2 seconds

2022-01-26 Thread David Wright
On Thu 27 Jan 2022 at 10:05:16 (+0530), Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
> 
> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.
> 
> I don’t want to file any bug report till I have some concrete data. So
> my question is - how do I diagnose such an issue and produce some data
> for debugging. So that I can hand it over to maintainers.

Can you provoke the same symptom by wiggling the HDMI plug in the
socket (at either end, but more likely at the computer end)?
These connectors can be unreliable.

Cheers,
David.



Screen goes blank for 1-2 seconds

2022-01-26 Thread Pankaj Jangid
Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
facing a very strange problem. The monitor goes blank for a brief time,
like 1-2s and then comes back. It is connected with the GPU using HDMI
cable.

During that 1-2s, the machine response is fine. Whatever I type during
that time goes there as input, and visible when the monitor comes back.

I don’t want to file any bug report till I have some concrete data. So
my question is - how do I diagnose such an issue and produce some data
for debugging. So that I can hand it over to maintainers.

Regards
Pankaj



Re: system freeze older iMac Debian 11

2022-01-26 Thread Felix Miata
Bob Crochelt composed on 2022-01-26 17:25 (UTC-0800):

> inxi output attached.  

Your iMac's BIOS date is about a month earlier than mine. Likely the only
difference between ours is you have G92M [GeForce 8800M GTS] while I have
RV630/M76 [Mobility Radeon HD 2600 XT/2700]. If yours is anything like mine, it
generates a lot of heat. Has yours ever had an internal cleaning? It may need 
its
heat sink compound on CPU and/or GPU replaced. System freezes are a common 
symptom
of overheating. Also, RAM is subject to failure with age and overheating. Have 
you
tried running memtest86?
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata



btfs disk compatibility between i386 and amd64

2022-01-26 Thread Joseph Brenner
I was wondering if the on-disk data format for btrfs is
compatible between the i386 and amd64 code bases--
e.g. would you expect to be able to swap data drives
between machines running either?

I've got an old i386 installation with /home in it's
own partition, and I'm wondering if I can expect to just
unlink /home and install a new amd64 version, and then link
in the home parition again.



Re: system freeze older iMac Debian 11

2022-01-26 Thread Bob Crochelt


On Wed, Jan 26, 2022, at 17:09, Felix Miata wrote:
> Robert F. Crochelt composed on 2022-01-26 16:52 (UTC-0800):
> 
> > Older iMac, recently installed Debian 11.  Having system freezes even
> > when running light weight environment like fvwm.  Starts with slow
> > video, progresses over a few minutes to complete freeze.  Can't even
> > shift to a different console with ctrl-F_.  Nothing in top (when it
> > starts) to suggest excessive memory or cpu usage.  Tried to install
> > nvidia drivers, but apparently not available for my GPU in Debian 11.
> > Output from lscpu and nvdia-detect in attached file.
> > I would be grateful for any suggestions.
> 
> As your attachment reports, the proprietary NVidia driver for your G92M 
> [GeForce
> 8800M GTS] (rev a2) had its support terminated before Bullseye.
> 
> Is the behavior the same if you use Wayland instead of Xorg?
> 
> What does inxi -SMGayz report (run from any terminal emulator in X)?
> -- 
> Evolution as taught in public schools is, like religion,
> based on faith, not based on science.
> 
> Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> 
> Felix Miata
> 
Thanks for the prompt reply.  I've not tried Wayland, have been happy with X 
till now.  
inxi output attached.  
BobSystem:
  Kernel: 5.10.0-11-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-11-amd64 
  root=UUID=c7496441-0106-499d-b623-032f6c08fe85 ro quiet 
  Desktop: FVWM 2.6.8 dm: startx Distro: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Desktop System: Apple product: iMac8,1 v: 1.0 serial:  
  Chassis: type: 13 v: Mac-F227BEC8 serial:  
  Mobo: Apple model: Mac-F227BEC8 v: PVT serial:  UEFI: Apple 
  v: IM81.88Z.00C1.B00.0802091538 date: 02/09/08 
Graphics:
  Device-1: NVIDIA G92M [GeForce 8800M GTS] vendor: Apple driver: N/A 
  alternate: nvidia bus ID: 01:00.0 chip ID: 10de:0609 class ID: 0300 
  Device-2: Apple Built-in iSight type: USB driver: uvcvideo bus ID: 7-4:2 
  chip ID: 05ac:8502 class ID: 0e02 serial:  
  Display: server: X.Org 1.20.11 driver: loaded: nouveau,vesa 
  unloaded: fbdev,modesetting alternate: nv display ID: :1 screens: 1 
  Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x318mm (20.0x12.5") 
  s-diag: 599mm (23.6") 
  Monitor-1: default res: 1920x1200 hz: 77 
  OpenGL: renderer: N/A v: N/A direct render: N/A 


Re: system freeze older iMac Debian 11

2022-01-26 Thread Felix Miata
Robert F. Crochelt composed on 2022-01-26 16:52 (UTC-0800):

> Older iMac, recently installed Debian 11.  Having system freezes even
> when running light weight environment like fvwm.  Starts with slow
> video, progresses over a few minutes to complete freeze.  Can't even
> shift to a different console with ctrl-F_.  Nothing in top (when it
> starts) to suggest excessive memory or cpu usage.  Tried to install
> nvidia drivers, but apparently not available for my GPU in Debian 11.
> Output from lscpu and nvdia-detect in attached file.
> I would be grateful for any suggestions.

As your attachment reports, the proprietary NVidia driver for your G92M [GeForce
8800M GTS] (rev a2) had its support terminated before Bullseye.

Is the behavior the same if you use Wayland instead of Xorg?

What does inxi -SMGayz report (run from any terminal emulator in X)?
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata



system freeze older iMac Debian 11

2022-01-26 Thread Robert F. Crochelt
Hi
Older iMac, recently installed Debian 11.  Having system freezes even
when running light weight environment like fvwm.  Starts with slow
video, progresses over a few minutes to complete freeze.  Can't even
shift to a different console with ctrl-F_.  Nothing in top (when it
starts) to suggest excessive memory or cpu usage.  Tried to install
nvidia drivers, but apparently not available for my GPU in Debian 11.
Output from lscpu and nvdia-detect in attached file.
I would be grateful for any suggestions.
Thanks
Bob Crochelt
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92M [GeForce 
8800M GTS] [10de:0609] (rev a2)

Checking card:  NVIDIA Corporation G92M [GeForce 8800M GTS] (rev a2)
Your card is only supported by the 340 legacy drivers series, which is only 
available up to buster.


Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   36 bits physical, 48 bits virtual
CPU(s):  2
On-line CPU(s) list: 0,1
Thread(s) per core:  1
Core(s) per socket:  2
Socket(s):   1
NUMA node(s):1
Vendor ID:   GenuineIntel
CPU family:  6
Model:   23
Model name:  Intel(R) Core(TM)2 Duo CPU E8435  @ 3.06GHz
Stepping:6
CPU MHz: 797.956
CPU max MHz: 3066.
CPU min MHz: 800.
BogoMIPS:6117.66
Virtualization:  VT-x
L1d cache:   64 KiB
L1i cache:   64 KiB
L2 cache:6 MiB
NUMA node0 CPU(s):   0,1
Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
Vulnerability L1tf:  Mitigation; PTE Inversion; VMX EPT disabled
Vulnerability Mds:   Vulnerable: Clear CPU buffers attempted, no 
microcode; SMT disabled
Vulnerability Meltdown:  Mitigation; PTI
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
Vulnerability Spectre v2:Mitigation; Full generic retpoline, STIBP 
disabled, RSB filling
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort:   Not affected
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe 
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf 
pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm pti 
tpr_shadow vnmi flexpriority vpid dtherm


Re: gnu screen and resizing terminal window

2022-01-26 Thread Bijan Soleymani

On 2022-01-26 5:55 p.m., Bijan Soleymani wrote:
Actually apparently putty does support remote resizing. It just seems 
that our systems lack the right termcap entries.


I managed to resize the putty window by running the command:
resize -s height width

so:
resize -s 24 80

Also adding this:
termcapinfo xterm WS=\E[8;%d;%dt

to:
/etc/screenrc

Allows screen to resize the putty session (with the :width and :height 
commands).


But when quitting/restarting screen it puts the putty and the screen 
session back to the original size.


Bijan



Re: gnu screen and resizing terminal window

2022-01-26 Thread Bijan Soleymani

On 2022-01-26 5:42 p.m., Bijan Soleymani wrote:
As far as I know this is not a screen feature. Putty controls the window 
size, it is determined by the default or whatever is saved for that 
session. You can change what happens when you resize the putty window on 
the machine running putty. There is no way for you to change the putty 
screen from the debian side.


Actually apparently putty does support remote resizing. It just seems 
that our systems lack the right termcap entries.


Bijan



Re: gnu screen and resizing terminal window

2022-01-26 Thread Bijan Soleymani




On 2022-01-26 1:45 p.m., Tim Woodall wrote:

I have to use PuTTY to connect to a debian server. For reasons that are
outwith my control the ssh session disconnects every 24 hrs.

Therefore I run screen so after reconnecting I can recover to whereever
I was at.

However, the PuTTY window does not resize to whatever it was previously.
I can find lots of questions asking how to turn this feature off but
nothing on why it doesn't work for me.


As far as I know this is not a screen feature. Putty controls the window 
size, it is determined by the default or whatever is saved for that 
session. You can change what happens when you resize the putty window on 
the machine running putty. There is no way for you to change the putty 
screen from the debian side.


Screen does provide commands to resize the virtual terminal, however 
neither putty nor xterm seem to support the termcap commands (apparently 
it is Z0 and Z1).


What happens when you try to resize the screen using screen's windowing 
commands:


^a : width 50
^a : height 15

(control-a, then colon, then width 50, then enter)

In my case I get a message that
Your termcap does not specify how to change the terminal's width to 50
and
Your termcap does not specify how to change the terminal's height to 15

That is with TERM set to xterm.

Bijan



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread gene heskett
On Wednesday, January 26, 2022 10:49:35 AM EST Brian wrote:
> On Wed 26 Jan 2022 at 10:39:42 -0500, gene heskett wrote:
> > On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote:
> > > On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> > > > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > > > > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > > > > > Resolving hostnames on the local network is simple and
> > > > > > reliable
> > > > > > when
> > > > > > avahi-daemon and linnss-mdns are available.
> > > > > > 
> > > > > >   brian@desktop:~$ getent hosts envy4500.local
> > > > > >   192.168.7.235   envy4500.local
> > > > > > 
> > > > > > Continually and nanually maintain /etc/hosts? Not in 2022!
> > > > 
> > > > More like biannually :-)
> > > > 
> > > > It's just pointless here, on such a static network. If I'm going
> > > > to
> > > > login to the router to add a MAC, then editing and distributing
> > > > my
> > > > master list is trivial. Last change: 2021-02-04, when I got hold
> > > > of
> > > > a redundant computer.
> > > 
> > > I am sure sue the use of the dawn of time /etc/hosts is a workabble
> > > solution. However many (most?) users will have libnns-mdns
> > > installed
> > > and immediately up to the job of resolving hostnames on a
> > > statically
> > > or dynamically configured network and is maintenance-free. Why not
> > > use
> > > it?
> > > 
> > > > > Ok, I'll bite :)
> > > > > 
> > > > > Could you point to any (reasonably up-to-date) documentation or
> > > > > is
> > > > > it
> > > > > sufficient to just install avahi-daemon and libnss-mdns?
> > > > 
> > > > I looked at the Debian wiki: ouch. It seems to have been spammed
> > > > a while back, and hasn't been touched in 4½ years. Although the
> > > > Arch wiki is far better, I'm not able to judge how much one might
> > > > be led astray by the differences between Arch and Debian.
> > > 
> > > Ouch indeed! The baisc structure and content of the wiki page was
> > > established in 2006. Its stated purpose is for "...tracking how
> > > Debian
> > > supports mdns and zeroconf stuff,...". The Discussion section is
> > > (IMO)
> > > inappropriate for a wiki page.
> > > 
> > > The Arch wiki page is technically more informed and, with care,
> > > would
> > > guide a Debian user in the right direcion.
> > > 
> > > Having said that, 'ssh desktop.local' does not require much
> > > guidance.
> > 
> > If a machine is "there" to reply, which one is it?
> 
> Sorry, I don't follow.

IDK for sure, but the descriptions I've speed read, seem to indicate a 
rather wild card approach, and that spooks me a bit, so I was trying to 
be a little facetious. Obviously I failed.

Thanks Brian 

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 





Re: hostname is being reset, killing net on reboot

2022-01-26 Thread gene heskett
On Wednesday, January 26, 2022 11:55:36 AM EST Greg Wooledge wrote:
> On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote:
> > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
> > should tell you that I don't have that file either, but I downloaded
> > dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this.
> > And if I type "man" into google, I get a list of previously sought
> > man pages as the response, rather than "camera tv".
> 
> Why not just use
> ?
> Is it too new?  You can replace "bullseye" with "buster" in the URL.
> Or "stretch", etc.
> 
I wasn't aware of that resource, thank you.
> .


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 





Re: gnu screen and resizing terminal window

2022-01-26 Thread Andrei POPESCU
On Mi, 26 ian 22, 18:45:41, Tim Woodall wrote:
> I have to use PuTTY to connect to a debian server. For reasons that are
> outwith my control the ssh session disconnects every 24 hrs.
> 
> Therefore I run screen so after reconnecting I can recover to whereever
> I was at.
> 
> However, the PuTTY window does not resize to whatever it was previously.
> I can find lots of questions asking how to turn this feature off but
> nothing on why it doesn't work for me.
> 
> I'm not wedded to screen - about the only feature I'm using is the
> scrollback buffer - so a change change to tmux is possible if that will
> help but I'd really like the resizing to work. Does this work for
> anyone?

As far as I recall the screen window size is limited to the smallest 
terminal that is connected to the particular session.

Maybe screen thinks there are other connections still present?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Re: how to test and compare performance of bullseye for i386 and amd64

2022-01-26 Thread a

Thank Polyna-Maude Racicot-Summerside!

it's only for curiosity.

for most users, their performance have little difference



Re: cmst empêche la clôture d'une session

2022-01-26 Thread didier gaumet



Le mercredi 26 janvier 2022 à 18:26 +0100, MERLIN Philippe a écrit :
> Bonjour,
> Je viens d'installer  à la place de wicd les paquets connman, iwd à
> la place de wpa_supplicant et cmst pour piloter le tout. Tout marche
> bien au point de vue connexion Wifi, j'ai un seul problème c'est à la
> fermeture d'une session Kde j'ai le message suivant /usr/bin/cmst a
> annuler la fermeture de cette session seul le lancement dans une
> console la commande shutdown now arrête effectivement le système .
> Savez vous comment une application en l'occurrence peut empêcher la
> fermeture d'une session  ? Et comment l'empêcher d'agir de cette
> façon.
> Philippe Merlin

Bonjour,

KDE/Plasma utilisant plasma-nm (la version KDE de l'applet Network-
Manager): si tu tiens à utiliser Cmst, tu as bien neutralisé le service
Network-Manager pour qu'il n'y ait pas de conflit d'utilisation avec
Connman?




Re: Btrfs best practices: defrag?

2022-01-26 Thread piorunz

I'd like to add question to this topic.

Is it safe & recommended to run autodefrag mount option in fstab?
I am considering two machines here, normal desktop which has Btrfs as
/home, and server with VM and other databases also btrfs /home. Both
Btrfs RAID10 types. Both are heavily fragmented. I never defragmented
them, in fact.

Running manual defrag on server machine, like:
sudo btrfs filesystem defrag -v -t4G -r /home
takes ages and can cause 120 second timeout kernel error in dmesg due to
service timeouts. I prefer to autodefrag gradually, overtime, mount
option seems to be good for that.

My current fstab mounting:

noatime,space_cache=v2,compress-force=zstd:3 0 2

Will autodefrag break COW files? Like I copy paste a file and I save
space, but defrag with destroy this space saving?
Also, will autodefrag compress files automatically, as mount option
enforces (compress-force=zstd:3)?

Any suggestions welcome.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Greg Wooledge
On Wed, Jan 26, 2022 at 07:26:49PM +, Brian wrote:
> On Wed 26 Jan 2022 at 10:42:38 -0600, David Wright wrote:
> > I've worked this way for 15 years and, unlike Gene, I'm not having
> > to fight any battles over it. I'm sure mDNS is perfect for people
> > with different demands from mine.
> 
> My question was really directed at all users, particularly those who
> do not appreciate the existance or basic function of Avahi. I am not
> dead set aginst /etc/hosts and the explantion of your successful mode
> of working should give pause for thought.

I don't know how many people know *anything* about it at all.  I certainly
don't, other than what's been mentioned in this thread.



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Brian
On Wed 26 Jan 2022 at 10:42:38 -0600, David Wright wrote:

[Snipping]

> I've worked this way for 15 years and, unlike Gene, I'm not having
> to fight any battles over it. I'm sure mDNS is perfect for people
> with different demands from mine.

My question was really directed at all users, particularly those who
do not appreciate the existance or basic function of Avahi. I am not
dead set aginst /etc/hosts and the explantion of your successful mode
of working should give pause for thought.

-- 
Brian.



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Reco
On Wed, Jan 26, 2022 at 07:11:36PM +0100, Andrei POPESCU wrote:
> > # fallback to static profile on eth0
> > interface eth0
> > fallback static_eth0
> > 
> > So if dhcpd fails, it uses the above, and it Just Works.
> > And I've not found any reference to it in the man page. So I've no clue 
> > why it seems to be such a huge, no one knows about it secret.
> 
> This must be the most complicated, round-about, inefficient method I've 
> ever seen to configure a static IP :)

I disagree. One can install NetworkManager, and then it will get even
more complicated.


> Is it so difficult to find out what is the canonical method to configure 
> a static IP on a Raspberry Pi OS? This is such a basic task it should be 
> somewhere in their documentation, wiki, whatever.

Curiously enough, this time Gene used "official" way to configure static
IP on RPi - [1]. Official documentation does not even mention e/n/i.


> Then it should be possible to configure a static IP with any of Debian's 
> network management tools you like.

And *that* would be fighting the distribution-approved method, and not
working with it. It's totally possible (I did it), but then again, it's
totally possible to install a real Debian on RPi.


All this once again proves us, folks - RaspberryPi OS is not Debian. It's
Debian-based. Certain list members do not see the difference, let's
refrain from pointing fingers :)

Reco

[1] 
https://www.raspberrypi.com/documentation/computers/configuration.html#static-ip-addresses



gnu screen and resizing terminal window

2022-01-26 Thread Tim Woodall

I have to use PuTTY to connect to a debian server. For reasons that are
outwith my control the ssh session disconnects every 24 hrs.

Therefore I run screen so after reconnecting I can recover to whereever
I was at.

However, the PuTTY window does not resize to whatever it was previously.
I can find lots of questions asking how to turn this feature off but
nothing on why it doesn't work for me.

I'm not wedded to screen - about the only feature I'm using is the
scrollback buffer - so a change change to tmux is possible if that will
help but I'd really like the resizing to work. Does this work for
anyone?

(long term I'm hoping to get permission to install cygwin and then use a
X server and xterms and ssh from inside them or, even better, a debian
laptop, but for now I'm stuck with putty)

Tim.



Re: Comment ajouter à Firefox le moteur de recherche Debian Package Search ?

2022-01-26 Thread Lamourec Alain
Il faut ajouter l'extension (add-on) Debian queries par 
outils/Modules complémentaires


Cordialement

Olivier writes:


Bonjour,

Je viens d'installer une nouvelle machine Bullseye.
Je note que Firefox n'y intègre pas le moteur de recherche 
Debian
Package Search qui permet de retrouver des paquets dans les 
dépôts

Debian.

Comment ajouter ce moteur ?
J'ai trouvé [1] puis [2] mais je n'arrive pas à suivre les 
instructions.


[1] https://forums.debian.net/viewtopic.php?p=723242
[2] 
https://mycroftproject.com/install.html?id=19956=all-debian-packages=ico=Debian+Packages+-+Names+%28All%29


Slts



--
Lamourec Alain



Re: Security

2022-01-26 Thread Andrei POPESCU
On Ma, 25 ian 22, 16:13:23, Nate Bargmann wrote:
> I am subscribed to that list and get them too.
> 
> I just see that three more messages popped in since this morning from
> the security list.
> 
> The complaints seem to be only about browsers.  The inference seems to
> be that the latest release always fixes security bugs.  While this is
> true to an extent, what is seldom acknowledged is that new releases also
> bring new and as yet undisclosed bugs that will be fixed next time or
> the time after or the time after that or...  I figure it's a gamble
> either way and stick with the Debian packages.

I'll use the opportunity to draw attention to DSA-5059-1, see e.g. this 
article for details:

https://arstechnica.com/information-technology/2022/01/a-bug-lurking-for-12-years-gives-attackers-root-on-every-major-linux-distro/

And please don't bother to reply with "there are no other users on this 
system I should worry about", the bad guys could still find ways to get 
in, e.g. via a compromised browser, regardless if you are behind a 
firewall or not[1].

Any system connecting to the internet should be kept up-to-date.

Even if you don't care about your data, privacy, etc., your system will 
probably become part of some botnet and be used to spread malware and 
spam to others.


[1] Of course, the risk level is significantly lower for the typical 
home user, but still not negligible in my opinion - we just can't know 
what unknown browser vulnerabilities there might be lurking, which the 
bad guys could actively exploit via malicious websites (vs. targeted 
attacks for high value targets).

In today's world once your browser is compromised https://xkcd.com/1200/ 
applies.


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Andrei POPESCU
On Ma, 25 ian 22, 21:27:17, gene heskett wrote:
> 
> It works fine with no complaints.
> 
> Here is the bottom of /etc/dhcpcd.conf:
> 
> # Example static IP configuration:
> #interface eth0
> #static ip_address=192.168.0.10/24
> #static ip6_address=fd51:42f8:caae:d92e::ff/64
> #static routers=192.168.0.1
> #static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1
> 
> # It is possible to fall back to a static IP if DHCP fails:
> # define static profile
> profile static_eth0
> static ip_address=192.168.71.13/24
> static routers=192.168.71.1
> static domain_name_servers=192.168.71.1
> 
> # fallback to static profile on eth0
> interface eth0
> fallback static_eth0
> 
> So if dhcpd fails, it uses the above, and it Just Works.
> And I've not found any reference to it in the man page. So I've no clue 
> why it seems to be such a huge, no one knows about it secret.

This must be the most complicated, round-about, inefficient method I've 
ever seen to configure a static IP :)

Is it so difficult to find out what is the canonical method to configure 
a static IP on a Raspberry Pi OS? This is such a basic task it should be 
somewhere in their documentation, wiki, whatever.

Even if they don't officially support static IPs (which I seriously 
doubt), you could still find out what is starting dhcpcd and disable it.

Then it should be possible to configure a static IP with any of Debian's 
network management tools you like. You might need to install it first 
though, preferably while the network connection is still up ;).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Andrei POPESCU
On Mi, 26 ian 22, 11:55:36, Greg Wooledge wrote:
> On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote:
> > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
> > should tell you that I don't have that file either, but I downloaded
> > dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this.
> > And if I type "man" into google, I get a list of previously sought
> > man pages as the response, rather than "camera tv".
> 
> Why not just use
> ?

+1 for manpages.debian.org, it's even possible to have it as an 
additional search engine in browsers that support it.

> Is it too new?  You can replace "bullseye" with "buster" in the URL.
> Or "stretch", etc.
 
I should close #931992 then ;)


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Re: The Raspberry Pi that Took a Day Off.

2022-01-26 Thread Gareth Evans



> On 25 Jan 2022, at 14:17, Martin McCormick  wrote:
> 
> This Pi is running Debian Stretch.  I believe that's what version
> 9 is called.  I have it capturing audio from a radio receiver and
> it's been doing that for several years now and it was doing that
> yesterday morning.  Later in the day, I downloaded more audio
> and, after a long pause, I got the message from ssh that the
> Raspberry Pi wasn't there any longer so I retrieved the Pi from
> the room where it was and brought it to my Debian desktop system
> to work on it.
> 
>I could login to the Pi which seemed to be up and running
> but the short story is that it couldn't talk to any address but
> our router.I couldn't even ping it's interface from the Pi,
> itself.
> 
>If I was on the Raspberry Pi's console, everything looked
> normal as long as one wasn't using the TCP/IP interface.  You
> could even do a ip addr or an ipconfig -a command and it would
> show that it had gotten the correct address from our dhcp server
> which is in the router.  It would successfully ping the router
> but no other addresses, not even the address it uses on our
> network.
> 
>I finally quit messing with it and went to bed but fired
> it up again today, January 25 and low and behold, it just came
> right up and is now back doing what it has been doing.
> 
>Is it possible that it got a corrupted lease for dhcp
> from the router?  Dhcp leases on our Netgear router are issued
> for not quite 24 hours so it may have gotten a bad lease, kept
> renewing it for the time it was powered up and then it got a new
> version of that lease today and all is well.
> 
>It's the same IP address because I have put it in the
> router as a static IP address.
> 
>The other thing that is weird is that the Raspberry Pi in
> question has both a wired Ethernet and a WiFi interface and both
> were misbehaving identically.
> 
>Normally, the wired port is not used and the dhcp lease
> renewal process happens over WiFi.
> 
>The results of ip addr always showed a correct subnet
> mask and the only rules in iptables are the 2 default rules.  In
> other words, all looked normal except that it didn't work.
> 
>While I had it on the work bench, so to speak, I ran fsck
> -fy on the SSD card since it has been a couple of years since I
> last did that and there was not a single squawk about anything.
> 
>Thanks for any ideas about how things got wrong and then
> magically fixed themselves.
> 
>When I turned it off last night, I gave it the halt -p
> command.  The power supply has no switch so I unplugged it from
> power so it started fresh about 8 hours later.
> 
> Martin WB5AGZ
> 

Hi Martin,

Are your router logs accessible?

Is there anything of potential relevance in those or the pi logs around the 
time it stopped/restarted 'connecting' (or even in the interim)?

Perhaps

cat /var/log/syslog{.n} | grep -i dhcp

might be a start, where {.n} indicates an optional eg. .1, .2 etc if syslog 
itself no longer contains logs from the relevant time.

The router may have a web interface that includes a section for errors if you 
can't get into it with ssh.  Not sure how helpful that might be even if one 
exists, but  maybe worth a look.

Gareth


Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Greg Wooledge
On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote:
> And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
> should tell you that I don't have that file either, but I downloaded
> dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this.
> And if I type "man" into google, I get a list of previously sought
> man pages as the response, rather than "camera tv".

Why not just use
?
Is it too new?  You can replace "bullseye" with "buster" in the URL.
Or "stretch", etc.



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread David Wright
On Wed 26 Jan 2022 at 15:31:46 (+), Brian wrote:
> On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > > > 
> > > > Resolving hostnames on the local network is simple and reliable when
> > > > avahi-daemon and linnss-mdns are available.
> > > > 
> > > >   brian@desktop:~$ getent hosts envy4500.local
> > > >   192.168.7.235   envy4500.local
> > > > 
> > > > Continually and nanually maintain /etc/hosts? Not in 2022!
> > 
> > More like biannually :-)
> > 
> > It's just pointless here, on such a static network. If I'm going to
> > login to the router to add a MAC, then editing and distributing my
> > master list is trivial. Last change: 2021-02-04, when I got hold of
> > a redundant computer.
> 
> I am sure sue the use of the dawn of time /etc/hosts is a workabble
> solution. However many (most?) users will have libnns-mdns installed
> and immediately up to the job of resolving hostnames on a statically
> or dynamically configured network and is maintenance-free. Why not use
> it?

Me personally? Because I want to avoid any complications with
configuring two cooperating routers; because I want to be able to spot
"foreign" interfaces by IP# (my brain doesn't work with either UUIDs
or MACs); because I want to be able to poke a hole into my network,
which raises security concerns; because I want to recognise that
two IP#s point to the same machine (MACs again); because knowing
how it all works is more valuable to me than the effort of lifting
a finger to maintain it once in a while.

Bear in mind that I'm likely installing Debian on something at
the time I'm making said tweak, and perhaps having to relocate
some functionailty to another machine if there's one heading for
recycling at the same time. With running the d-i and configuring
the router, what's to get worked up about with adding a line to
/etc/hosts?

I've worked this way for 15 years and, unlike Gene, I'm not having
to fight any battles over it. I'm sure mDNS is perfect for people
with different demands from mine.

Cheers,
David.



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread David Wright
On Wed 26 Jan 2022 at 05:14:32 (-0500), gene heskett wrote:
> On Tuesday, January 25, 2022 11:36:05 PM EST David Wright wrote:
> > On Tue 25 Jan 2022 at 21:27:17 (-0500), gene heskett wrote:
> > > On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote:
> > > > I can't speak to Gene's wanting a static network configured by his
> > > > method, but I'm happy to defend my choice.
> > > 
> > > It works fine with no complaints.
> > 
> > OK. I've already forgotten what you complained [about] in this thread's OP.
> > 
> > > Here is the bottom of /etc/dhcpcd.conf:
> > > 
> > > # Example static IP configuration:
> > > #interface eth0
> > > #static ip_address=192.168.0.10/24
> > > #static ip6_address=fd51:42f8:caae:d92e::ff/64
> > > #static routers=192.168.0.1
> > > #static domain_name_servers=192.168.0.1 8.8.8.8
> > > fd51:42f8:caae:d92e::1
> > > 
> > > # It is possible to fall back to a static IP if DHCP fails:
> > > # define static profile
> > > profile static_eth0
> > > static ip_address=192.168.71.13/24
> > > static routers=192.168.71.1
> > > static domain_name_servers=192.168.71.1
> > > 
> > > # fallback to static profile on eth0
> > > interface eth0
> > > fallback static_eth0
> > > 
> > > So if dhcpd fails, it uses the above, and it Just Works.
> > > And I've not found any reference to it in the man page. So I've no
> > > clue why it seems to be such a huge, no one knows about it secret.
> > Drum roll … …
> > 
> > CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz
> > 
> > DHCPCD.CONF(5)  BSD File Formats Manual
> > DHCPCD.CONF(5)
> > 
> > NAME
> >  dhcpcd.conf — dhcpcd configuration file
> > 
> > [ … ]
> > 
> >  profile name
> >  Subsequent options are only parsed for this profile name.
> > 
> > [ … ]
> > 
> >  static value
> >  Configures a static value.  If you set ip_address then
> > dhcpcd will not attempt to obtain a lease and will just use the value
> > for the address with an infinite lease time.  If you set ip6_address,
> > dhcpcd will continue auto-configuation as normal.
> > 
> > [ … ]
> > 
> >interface eth0
> >[ … ]
> >static ip_address=192.168.0.10/24
> >[ … ]
> >static routers=192.168.0.1
> >static domain_name_servers=192.168.0.1
> > 
> > [ … ]
> > 
> >  fallback profile
> >  Fall back to using this profile if DHCP fails.  This
> > allows you to configure a static profile instead of using ZeroConf.
> > 
> > /That/ seems clear enough to me.
> > 
> `twould indeed be clear David, but man keeps telling me no such file.

And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
should tell you that I don't have that file either, but I downloaded
dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this.
And if I type "man" into google, I get a list of previously sought
man pages as the response, rather than "camera tv".

> > But excuse me if I was labouring under the impression that you wanted
> > to nuke DHCP lest "some coder dinking around in dhcp code thinks the
> > whole world is volatile".
> 
> The responses I get from this list or any list positively reeks of NIH 
> syndrome if you want to do something different for a home net that 
> doesn't depend on dhcp. hosts files existed and ran the internet before 
> dhcp.

And when you install Debian, it helpfully writes one for you. I don't
know what is NIH about that. But your response here doesn't state
unambiguously whether you want to run DHCP or not, nor whether you do
or don't. Others have suggested that the OS you're actually dealing
with is one that sets up certain things in a non-Debian manner. If so,
then you need to investigate what those things are, and fit your
changes round them, rather than just fighting it, trying to return to
some "Golden Age" of networking from the 1990s.

Cheers,
David.



Re: how to test and compare performance of bullseye for i386 and amd64

2022-01-26 Thread David Wright
On Wed 26 Jan 2022 at 05:44:50 (-0500), Polyna-Maude Racicot-Summerside wrote:
> On 2022-01-25 19:35, David Wright wrote:
> > On Tue 25 Jan 2022 at 01:37:29 (-0500), a wrote:
> >> Thank David and Polyna-Maude!
> >>
> >> it's surprising that "The x64 binary are also somewhat larger than the
> >> i386 binaries"
> >>
> >> i compare some packages of bullseye for both arch, they happen to be
> >> contrary
> >>
> >> though difference is small and IMO has little impact on performance
> >>
> >> firefox-esr for i386: size= 58465416
> >>
> >> firefox-esr for amd64: size= 55451188
> >>
> >> gcc-10 for i386: size= 18097884
> >>
> >> gcc-10 for amd64: size=  16990272
> > 
> > Well, we've gone from ISOs containing different inventories to sizes
> > of packages. I still don't see how that affects performance.
> > 
> > All I did was to type ls -l /usr/bin for the two architectures into
> > two xterms in two viewports, and blink-compare them. Some binaries
> > were larger and some were smaller.
> > 
> > But let's try running them. I happen to have two freshly installed
> > bullseyes, and neither has run the installed FF before. Their dotfiles
> > in my home directories are close to identical, and their starting
> > pages are blank.
> > 
> > i386:
> > 
> >VSZ   RSZ %MEM  PID STAT   CMD
> > 1200184 176396 34.9   1603 Sl+firefox-esr
> > 477488 50140  9.9 1880 Sl+/usr/lib/firefox-esr/firefox-esr 
> > -contentproc -ch>
> > 467760 34188  6.7 1821 Sl+/usr/lib/firefox-esr/firefox-esr 
> > -contentproc -ch>
> > 455296 27436  5.4 1958 Sl+/usr/lib/firefox-esr/firefox-esr 
> > -contentproc -ch>
> > 
> > amd64:
> > 
> >VSZ   RSZ %MEMPID STAT   CMD
> > 3082424 408156  2.5 2538 Sl+firefox-esr
> > 2446004 146664  0.9 2662 Sl+/usr/lib/firefox-esr/firefox-esr 
> > -contentproc ->
> > 2417628 117508  0.7 2694 Sl+/usr/lib/firefox-esr/firefox-esr 
> > -contentproc ->
> > 2403264 108072  0.6 2603 Sl+/usr/lib/firefox-esr/firefox-esr 
> > -contentproc ->
> > 
> > The difference is larger than I thought it would be. Others would
> > have to interpret the actual numbers. The main difference that
> > /I/ notice is the speed, but it would be an unfair comparison,
> > pitching 1.5GHz/512MB with 1GB encrypted swap on 2004-era rust
> > against a multi-core 2.7GHz/16GB with a 2017-era SSD (but no swap).
> > Starting times come out at 3 minutes vs perhaps one second.
> > 
> Did you ask your question in a real-world intention ? I mean based on
> something you want to implement and may have resources limitation so
> want to have the most for what you got ?
> 
> Or was it only a question for "academic" purposes ? That you wanted some
> answer and explanation without any context that you can give.

The charitable interpretation I placed on "a", aka "lou", is that
they¹ have found a 32-bit-only wireless adapter, run a 32-bit
system, and are generally unimpressed by its speed.

If you remember, reading PDFs was slow, firmware-free adapters
were hard to find, and firmware-inclusive installers were elusive,
in the eyes of the OP. So, a less charitable interpretation might
be in order.

> If it's only for curiosity then there's plenty of books to read and
> you'll find answers.

Ah, PDFs. Catch 22 here.

¹ Forgive my grammar, RMS.

Cheers,
David.



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Brian
On Wed 26 Jan 2022 at 15:54:38 +, mick crane wrote:

> On 2022-01-26 15:31, Brian wrote:
> 
> > Having said that, 'ssh desktop.local' does not require much guidance.
> 
> Is .local mDNS specific ?

Yes.

> I thought we are supposed to not use .local for a home network.

That caveat is for allocating a domain name.

-- 
Brian.



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread mick crane

On 2022-01-26 15:31, Brian wrote:


Having said that, 'ssh desktop.local' does not require much guidance.


Is .local mDNS specific ?
I thought we are supposed to not use .local for a home network.
What is this ipv4only.arpa , are we supposed to use that.

mick
--
Key ID4BFEBB31



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Brian
On Wed 26 Jan 2022 at 10:39:42 -0500, gene heskett wrote:

> On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote:
> > On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> > > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > > > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > > > > Resolving hostnames on the local network is simple and reliable
> > > > > when
> > > > > avahi-daemon and linnss-mdns are available.
> > > > > 
> > > > >   brian@desktop:~$ getent hosts envy4500.local
> > > > >   192.168.7.235   envy4500.local
> > > > > 
> > > > > Continually and nanually maintain /etc/hosts? Not in 2022!
> > > 
> > > More like biannually :-)
> > > 
> > > It's just pointless here, on such a static network. If I'm going to
> > > login to the router to add a MAC, then editing and distributing my
> > > master list is trivial. Last change: 2021-02-04, when I got hold of
> > > a redundant computer.
> > 
> > I am sure sue the use of the dawn of time /etc/hosts is a workabble
> > solution. However many (most?) users will have libnns-mdns installed
> > and immediately up to the job of resolving hostnames on a statically
> > or dynamically configured network and is maintenance-free. Why not use
> > it?
> > 
> > > > Ok, I'll bite :)
> > > > 
> > > > Could you point to any (reasonably up-to-date) documentation or is
> > > > it
> > > > sufficient to just install avahi-daemon and libnss-mdns?
> > > 
> > > I looked at the Debian wiki: ouch. It seems to have been spammed
> > > a while back, and hasn't been touched in 4½ years. Although the
> > > Arch wiki is far better, I'm not able to judge how much one might
> > > be led astray by the differences between Arch and Debian.
> > 
> > Ouch indeed! The baisc structure and content of the wiki page was
> > established in 2006. Its stated purpose is for "...tracking how Debian
> > supports mdns and zeroconf stuff,...". The Discussion section is (IMO)
> > inappropriate for a wiki page.
> > 
> > The Arch wiki page is technically more informed and, with care, would
> > guide a Debian user in the right direcion.
> > 
> > Having said that, 'ssh desktop.local' does not require much guidance.
> 
> If a machine is "there" to reply, which one is it?

Sorry, I don't follow.

-- 
Brian.



Re: hostname is being reset, killing net on reboot

2022-01-26 Thread gene heskett
On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote:
> On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > > > Resolving hostnames on the local network is simple and reliable
> > > > when
> > > > avahi-daemon and linnss-mdns are available.
> > > > 
> > > >   brian@desktop:~$ getent hosts envy4500.local
> > > >   192.168.7.235   envy4500.local
> > > > 
> > > > Continually and nanually maintain /etc/hosts? Not in 2022!
> > 
> > More like biannually :-)
> > 
> > It's just pointless here, on such a static network. If I'm going to
> > login to the router to add a MAC, then editing and distributing my
> > master list is trivial. Last change: 2021-02-04, when I got hold of
> > a redundant computer.
> 
> I am sure sue the use of the dawn of time /etc/hosts is a workabble
> solution. However many (most?) users will have libnns-mdns installed
> and immediately up to the job of resolving hostnames on a statically
> or dynamically configured network and is maintenance-free. Why not use
> it?
> 
> > > Ok, I'll bite :)
> > > 
> > > Could you point to any (reasonably up-to-date) documentation or is
> > > it
> > > sufficient to just install avahi-daemon and libnss-mdns?
> > 
> > I looked at the Debian wiki: ouch. It seems to have been spammed
> > a while back, and hasn't been touched in 4½ years. Although the
> > Arch wiki is far better, I'm not able to judge how much one might
> > be led astray by the differences between Arch and Debian.
> 
> Ouch indeed! The baisc structure and content of the wiki page was
> established in 2006. Its stated purpose is for "...tracking how Debian
> supports mdns and zeroconf stuff,...". The Discussion section is (IMO)
> inappropriate for a wiki page.
> 
> The Arch wiki page is technically more informed and, with care, would
> guide a Debian user in the right direcion.
> 
> Having said that, 'ssh desktop.local' does not require much guidance.

If a machine is "there" to reply, which one is it?

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 





Re: Security

2022-01-26 Thread Nicholas Geovanis
The proper way IMO is to subscribe to the CERT for your nation. Be the
interface to it for your organization within your local responsibilities.
You will then receive the high-risk advisories before they are publically
released. That paid off, for example, during the ghost/meltdown Intel
vulnerabilities.

On Tue, Jan 25, 2022, 2:52 PM Polyna-Maude Racicot-Summerside <
deb...@polynamaude.com> wrote:

>
>
> On 2022-01-25 15:47, Andy Smith wrote:
> > Hello,
> >
> > On Tue, Jan 25, 2022 at 03:05:51PM -0500, Polyna-Maude
> Racicot-Summerside wrote:
> >> Kind of strange that some people complains we lag behind when I get
> >> information everyday that fixes are available for packages in the stable
> >> / old stable release.
> >
> > I think you are getting worked up over the actions of a troll.
> >
> > You will never get them to change their mind no matter how much
> > factual evidence you come up with, because they aren't posting in
> > good faith. If they were then they would have either accepted the
> > answers they got five times over the first time they brought it up
> > here, or else not accepted them and given up. Instead they went on
> > to write a "press release" and threaten more to come regarding
> > "excommunicated" developers. Their goal is to cause drama, not find
> > a solution for any real world problem.
> >
> > I recommend just moving on with your life and accepting that this
> > person is going to keep posting the same claims over and over
> > without feeling the need to refute them every time.
> >
> This message was more regarding some new users or ones who could have
> doubt on the safety / security of the Debian ecosystem.
>
> Sadly some of these people may cause some harm.
>
> > Cheers,
> > Andy
> >
>
> --
> Polyna-Maude R.-Summerside
> -Be smart, Be wise, Support opensource development
>


Re: hostname is being reset, killing net on reboot

2022-01-26 Thread Brian
On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:

> On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > > 
> > > Resolving hostnames on the local network is simple and reliable when
> > > avahi-daemon and linnss-mdns are available.
> > > 
> > >   brian@desktop:~$ getent hosts envy4500.local
> > >   192.168.7.235   envy4500.local
> > > 
> > > Continually and nanually maintain /etc/hosts? Not in 2022!
> 
> More like biannually :-)
> 
> It's just pointless here, on such a static network. If I'm going to
> login to the router to add a MAC, then editing and distributing my
> master list is trivial. Last change: 2021-02-04, when I got hold of
> a redundant computer.

I am sure sue the use of the dawn of time /etc/hosts is a workabble
solution. However many (most?) users will have libnns-mdns installed
and immediately up to the job of resolving hostnames on a statically
or dynamically configured network and is maintenance-free. Why not use
it?
 
> > Ok, I'll bite :)
> > 
> > Could you point to any (reasonably up-to-date) documentation or is it 
> > sufficient to just install avahi-daemon and libnss-mdns?
> 
> I looked at the Debian wiki: ouch. It seems to have been spammed
> a while back, and hasn't been touched in 4½ years. Although the
> Arch wiki is far better, I'm not able to judge how much one might
> be led astray by the differences between Arch and Debian.

Ouch indeed! The baisc structure and content of the wiki page was
established in 2006. Its stated purpose is for "...tracking how Debian
supports mdns and zeroconf stuff,...". The Discussion section is (IMO)
inappropriate for a wiki page.

The Arch wiki page is technically more informed and, with care, would
guide a Debian user in the right direcion.

Having said that, 'ssh desktop.local' does not require much guidance.

-- 
Brian.



Re: Hyper-typematic and Firefox responsiveness in Weston.

2022-01-26 Thread peter
From: Stefan Monnier 
Date: Sat, 01 Jan 2022 16:23:10 -0500
> I suggest you file a bug report.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004358

Regards, ... P.


-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W



Re: mailutils-pop3d not able to get it working

2022-01-26 Thread paulf
On Wed, 26 Jan 2022 13:55:46 +0100
Franco Martelli  wrote:

> On 26/01/22 at 03:39, pa...@quillandmouse.com wrote:
> > 
> > I use popa3d. It assumes email addresses of myuser@mydomain, with
> > the same email password as the user's password on the system. No
> > setup required. User billw on clifford.mydomain has an email of
> > billw@clifford.mydomain and he uses the same password as his user on
> > clifford.mydomain.
> > 
> > Paul
> > 
> Does popa3d require to setup TLS? I didn't need to encrypt the email
> a mail server that it listens to 110 port it is fine for me.
> 

As far as I know, there's no encryption.

Paul

-- 
Paul M. Foster
http://noferblatz.com
http://quillandmouse.com



Re: mailutils-pop3d not able to get it working

2022-01-26 Thread Franco Martelli

On 26/01/22 at 03:39, pa...@quillandmouse.com wrote:


I use popa3d. It assumes email addresses of myuser@mydomain, with the
same email password as the user's password on the system. No setup
required. User billw on clifford.mydomain has an email of
billw@clifford.mydomain and he uses the same password as his user on
clifford.mydomain.

Paul

Does popa3d require to setup TLS? I didn't need to encrypt the email a 
mail server that it listens to 110 port it is fine for me.


--
Franco Martelli



Re: mailutils-pop3d not able to get it working

2022-01-26 Thread Dieter Rohlfing
Am Tue, 25 Jan 2022 21:39:36 -0500
schrieb :

>I use popa3d.

Me too. popa3d is simple, small and effective.

Dieter



Re: how to test and compare performance of bullseye for i386 and amd64

2022-01-26 Thread Polyna-Maude Racicot-Summerside


On 2022-01-25 19:35, David Wright wrote:
> On Tue 25 Jan 2022 at 01:37:29 (-0500), a wrote:
>> Thank David and Polyna-Maude!
>>
>> it's surprising that "The x64 binary are also somewhat larger than the
>> i386 binaries"
>>
>> i compare some packages of bullseye for both arch, they happen to be
>> contrary
>>
>> though difference is small and IMO has little impact on performance
>>
>> firefox-esr for i386: size= 58465416
>>
>> firefox-esr for amd64: size= 55451188
>>
>> gcc-10 for i386: size= 18097884
>>
>> gcc-10 for amd64: size=  16990272
> 
> Well, we've gone from ISOs containing different inventories to sizes
> of packages. I still don't see how that affects performance.
> 
> All I did was to type ls -l /usr/bin for the two architectures into
> two xterms in two viewports, and blink-compare them. Some binaries
> were larger and some were smaller.
> 
> But let's try running them. I happen to have two freshly installed
> bullseyes, and neither has run the installed FF before. Their dotfiles
> in my home directories are close to identical, and their starting
> pages are blank.
> 
> i386:
> 
>VSZ   RSZ %MEM  PID STAT   CMD
> 1200184 176396 34.9   1603 Sl+firefox-esr
> 477488 50140  9.9 1880 Sl+/usr/lib/firefox-esr/firefox-esr 
> -contentproc -ch>
> 467760 34188  6.7 1821 Sl+/usr/lib/firefox-esr/firefox-esr 
> -contentproc -ch>
> 455296 27436  5.4 1958 Sl+/usr/lib/firefox-esr/firefox-esr 
> -contentproc -ch>
> 
> amd64:
> 
>VSZ   RSZ %MEMPID STAT   CMD
> 3082424 408156  2.5 2538 Sl+firefox-esr
> 2446004 146664  0.9 2662 Sl+/usr/lib/firefox-esr/firefox-esr 
> -contentproc ->
> 2417628 117508  0.7 2694 Sl+/usr/lib/firefox-esr/firefox-esr 
> -contentproc ->
> 2403264 108072  0.6 2603 Sl+/usr/lib/firefox-esr/firefox-esr 
> -contentproc ->
> 
> The difference is larger than I thought it would be. Others would
> have to interpret the actual numbers. The main difference that
> /I/ notice is the speed, but it would be an unfair comparison,
> pitching 1.5GHz/512MB with 1GB encrypted swap on 2004-era rust
> against a multi-core 2.7GHz/16GB with a 2017-era SSD (but no swap).
> Starting times come out at 3 minutes vs perhaps one second.
> 
Did you ask your question in a real-world intention ? I mean based on
something you want to implement and may have resources limitation so
want to have the most for what you got ?

Or was it only a question for "academic" purposes ? That you wanted some
answer and explanation without any context that you can give.

Without regards to code size or whatever, there may or may not be a
performance advantage and this depend on both the type of workload and
the system you are running under.

Regarding code size, it's also mostly dependent on some choice made
during calculation such as level of optimization and how the compiler
build the output.

So your simple question needs more real world data if you want a useful
answer.

If it's only for curiosity then there's plenty of books to read and
you'll find answers.
> Cheers,
> David.
> 

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development


OpenPGP_signature
Description: OpenPGP digital signature


Re: hostname is being reset, killing net on reboot

2022-01-26 Thread gene heskett
On Tuesday, January 25, 2022 11:36:05 PM EST David Wright wrote:
> On Tue 25 Jan 2022 at 21:27:17 (-0500), gene heskett wrote:
> > On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote:
> > > I can't speak to Gene's wanting a static network configured by his
> > > method, but I'm happy to defend my choice.
> > 
> > It works fine with no complaints.
> 
> OK. I've already forgotten what you complained in this thread's OP.
> 
> > Here is the bottom of /etc/dhcpcd.conf:
> > 
> > # Example static IP configuration:
> > #interface eth0
> > #static ip_address=192.168.0.10/24
> > #static ip6_address=fd51:42f8:caae:d92e::ff/64
> > #static routers=192.168.0.1
> > #static domain_name_servers=192.168.0.1 8.8.8.8
> > fd51:42f8:caae:d92e::1
> > 
> > # It is possible to fall back to a static IP if DHCP fails:
> > # define static profile
> > profile static_eth0
> > static ip_address=192.168.71.13/24
> > static routers=192.168.71.1
> > static domain_name_servers=192.168.71.1
> > 
> > # fallback to static profile on eth0
> > interface eth0
> > fallback static_eth0
> > 
> > So if dhcpd fails, it uses the above, and it Just Works.
> > And I've not found any reference to it in the man page. So I've no
> > clue why it seems to be such a huge, no one knows about it secret.
> Drum roll … …
> 
> CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz
> 
> DHCPCD.CONF(5)  BSD File Formats Manual
> DHCPCD.CONF(5)
> 
> NAME
>  dhcpcd.conf — dhcpcd configuration file
> 
> [ … ]
> 
>  profile name
>  Subsequent options are only parsed for this profile name.
> 
> [ … ]
> 
>  static value
>  Configures a static value.  If you set ip_address then
> dhcpcd will not attempt to obtain a lease and will just use the value
> for the address with an infinite lease time.  If you set ip6_address,
> dhcpcd will continue auto-configuation as normal.
> 
> [ … ]
> 
>interface eth0
>[ … ]
>static ip_address=192.168.0.10/24
>[ … ]
>static routers=192.168.0.1
>static domain_name_servers=192.168.0.1
> 
> [ … ]
> 
>  fallback profile
>  Fall back to using this profile if DHCP fails.  This
> allows you to configure a static profile instead of using ZeroConf.
> 
> /That/ seems clear enough to me.
> 
`twould indeed be clear David, but man keeps telling me no such file.

> But excuse me if I was labouring under the impression that you wanted
> to nuke DHCP lest "some coder dinking around in dhcp code thinks the
> whole world is volatile".

The responses I get from this list or any list positively reeks of NIH 
syndrome if you want to do something different for a home net that 
doesn't depend on dhcp. hosts files existed and ran the internet before 
dhcp. I remember using them on both pc's and amiga's 30 years ago. Its 
the short term memory that is plaguing me now. Can you remember using 
trumpet on a pc? I can. The amiga's had miami for a net driver but I 
can't recall if I used it when I wrote our first web page server in ARexx 
we used when we went live on the net for news, pulling the text from the 
teleprompter. WDTV was in the first 5 tv stations in the country that had 
a web page that went live as the live tv news show closed. It also demo'd 
the atrocious spelling of our journalists which got rather hilarious at 
times. :o)

At 87, I spend a lot of time contemplating the hereafter, I get up to go 
get a tool, and when I get to where the tool might be, I have to stop 
until I can remember what I'm hereafter. ;-)
 
> Cheers,
> David.
> 
> .
Take care and stay well David.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 





Comment ajouter à Firefox le moteur de recherche Debian Package Search ?

2022-01-26 Thread Olivier
Bonjour,

Je viens d'installer une nouvelle machine Bullseye.
Je note que Firefox n'y intègre pas le moteur de recherche Debian
Package Search qui permet de retrouver des paquets dans les dépôts
Debian.

Comment ajouter ce moteur ?
J'ai trouvé [1] puis [2] mais je n'arrive pas à suivre les instructions.

[1] https://forums.debian.net/viewtopic.php?p=723242
[2] 
https://mycroftproject.com/install.html?id=19956=all-debian-packages=ico=Debian+Packages+-+Names+%28All%29

Slts



Re: Nftables : Question d'un novice ...

2022-01-26 Thread Billard François-Marie

Bonjour

merci pour cette réponse, je vais faire un test dans la semaine.

je vais quand même essayer de creuser ces règles et d'en apprendre un 
peu plus.


Quelle documentation plus théorique sur ce procédé conseillez vous?

François-Marie


Le 24/01/2022 à 14:11, NoSpam a écrit :

Bonjour

Le 24/01/2022 à 13:56, Billard François-Marie a écrit :

Bonjour

question de novice quand à la gestion NFTABLES et n'étant pas 
spécialiste des réseaux.


Je dispose d'une machine qui d'un coté distribue des adresses pour un 
réseau local ( en filaire IP_Locale) et de l'autre coté un connexion 
WIFI (IP_WIFI) temporaire sur un portail captif (INTERNET).


Sur la même machine j'ai un serveur WEB local.

Ma question est quelle est la règle de routage pour que les requêtes 
sur des serveurs web en provenance de mon réseau local soient routées 
vers la connexion wifi.


nft add rule ip nat PREROUTING ip saddr 192.168.34.0/24 ip daddr != 
192.168.34.250 tcp dport 80 counter dnat to 10.0.0.1


Tu peux obtenir facilement les règles nftables en utilisant 
iptables-translate


iptables-translate -t nat -A PREROUTING -p tcp -s 192.168.34.0/24 ! -d 
192.168.34.250 --dport 80 -j DNAT --to 10.0.0.1


qui te donneras le résultat ci dessus



Autrement formulé cela donne :

Si demande d'accès au serveur web local (IP_Locale)

    alors pas de routage

    sinon routage vers le wifi.

J'ai bien lu des doc sur nftables et compris le principe global de ce 
système, mais je n'arrive pas a cerner comment définir la règle 
ci-dessus.


Merci pour votre aide.

Bien cordialement

François-Marie BILLARD