Re: ssh no conecta (Bullseye en ambos equipos)

2021-05-15 Thread Zeque 
Walter,

 Es raro lo del timeout, probaste hacer un telnet al puerto?
nc -v 192.168.0.8 22
Revistaste el archivo hosts.deny  hosts.allow que nada haya cambiado?
Chequea también las reglas de firewall
iptables -L

Saludos!
Zeque

El 15 de mayo de 2021 12:49:37 ART, Walter Omar Dari  
escribió:
>Hola gente:
>
>Me quiero conectar a un equipo de la red local que antes tenía Buster y 
>no había problemas, pero no puedo a partir de que le instalé Bullseye. 
>No se si será por Bullseye u otro motivo.
>
>Cuando quiero conectar queda así...
>
>dari@debwal:~$ ssh 192.168.0.8 -vvv
>OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1k  25 Mar 2021
>debug1: Reading configuration data /etc/ssh/ssh_config
>debug1: /etc/ssh/ssh_config line 19: include 
>/etc/ssh/ssh_config.d/*.conf matched no files
>debug1: /etc/ssh/ssh_config line 21: Applying options for *
>debug2: resolve_canonicalize: hostname 192.168.0.8 is address
>debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> 
>'/home/wodari/.ssh/known_hosts'
>debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> 
>'/home/wodari/.ssh/known_hosts2'
>debug2: ssh_connect_direct
>debug1: Connecting to 192.168.0.8 [192.168.0.8] port 22.
>
>... después de un rato da un error de timeout.
>
>
>En el equipo al que me quiero conectar, el puerto 22 parece estar bien...
>
># netstat -plnt
>Active Internet connections (only servers)
>Proto Recv-Q Send-Q Local Address   Foreign Address 
>State   PID/Program name
>tcp0  0 127.0.0.1:530.0.0.0:* 
>LISTEN  652/connmand
>tcp0  0 0.0.0.0:22  0.0.0.0:* 
>LISTEN  586057/sshd: /usr/s
>tcp0  0 127.0.0.1:631   0.0.0.0:* 
>LISTEN  523630/cupsd
>tcp0  0 0.0.0.0:44025   0.0.0.0:* 
>LISTEN  -
>tcp0  0 127.0.0.1:250.0.0.0:* 
>LISTEN  1146/exim4
>tcp0  0 0.0.0.0:17500   0.0.0.0:* 
>LISTEN  581546/dropbox
>tcp0  0 127.0.0.1:17600 0.0.0.0:* 
>LISTEN  581546/dropbox
>tcp0  0 127.0.0.1:17603 0.0.0.0:* 
>LISTEN  581546/dropbox
>tcp0  0 0.0.0.0:111 0.0.0.0:* 
>LISTEN  1/init
>tcp6   0  0 :::1716 :::* 
>LISTEN  580502/kdeconnectd
>tcp6   0  0 ::1:53  :::* 
>LISTEN  652/connmand
>tcp6   0  0 :::22   :::* 
>LISTEN  586057/sshd: /usr/s
>tcp6   0  0 ::1:631 :::* 
>LISTEN  523630/cupsd
>tcp6   0  0 :::41785:::* 
>LISTEN  -
>tcp6   0  0 ::1:25  :::* 
>LISTEN  1146/exim4
>tcp6   0  0 :::17500:::* 
>LISTEN  581546/dropbox
>tcp6   0  0 :::111  :::* 
>LISTEN  1/init
>
>Los archivos de configuración ssh_config y sshd_config están iguales en 
>los dos equipos, en directorios ssh_config.d y sshd_config.d estàn 
>vacìos en ambos equipos.
>
>Desde el equipo al cual me quiero comunicar, al mío no tengo problemas, 
>ssh conecta sin problemas, el tema es cuando es al revés.
>
>Alguien me puede dar alguna pista ?
>
>Muchas gracias,
>-- 
>
>Walter O. Dari
>
>http://swcomputacion.com/
>http://swcomputacion.com/sistemas/
>https://facebook.com/swcomputacion/
>https://facebook.com/sistemasSW/
>
>Nuestros horarios:
>L a V 8 a 13 hs.
>S 11 a 14 hs.
>
>WhatsApp:
>2396 577140 (no se atienden llamadas)
>

Re: ssh no conecta (Bullseye en ambos equipos)

2021-05-15 Thread Walter Omar Dari 

Hola Camaleón, cómo va ?...

El 15/5/21 a las 14:27, Camaleón escribió:

El 2021-05-15 a las 12:49 -0300, Walter Omar Dari escribió:


Me quiero conectar a un equipo de la red local que antes tenía Buster y no
había problemas, pero no puedo a partir de que le instalé Bullseye. No se si
será por Bullseye u otro motivo.


Además d elo que te han comentado, revisa las opciones de configuración
de SSH en el sistema donde has puesto testing, quizá alguna opción te
esté dando guerra.



Los archivos de configuración, los contenidos en /etc/ssh/ son 
prácticamente idénticos en los dos equipos, salvo los archivos .key



  

Cuando quiero conectar queda así...

dari@debwal:~$ ssh 192.168.0.8 -vvv
OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1k  25 Mar 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolve_canonicalize: hostname 192.168.0.8 is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' ->
'/home/wodari/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' ->
'/home/wodari/.ssh/known_hosts2'
debug2: ssh_connect_direct
debug1: Connecting to 192.168.0.8 [192.168.0.8] port 22.

... después de un rato da un error de timeout.


Un error de timeout apunta a que el anfitrión (el equipo al que
conectas) corta la conexión por algún motivo (directiva de seguridad,
etc.); si llegas con un ping al equipo, así a bote pronto el cortafuegos
quedaría descartado.


El ping me responde inmediatamente...

$ ping 192.168.0.8
PING 192.168.0.8 (192.168.0.8) 56(84) bytes of data.
64 bytes from 192.168.0.8: icmp_seq=1 ttl=64 time=0.344 ms
64 bytes from 192.168.0.8: icmp_seq=2 ttl=64 time=0.330 ms
64 bytes from 192.168.0.8: icmp_seq=3 ttl=64 time=0.338 ms
64 bytes from 192.168.0.8: icmp_seq=4 ttl=64 time=0.331 ms
^C



(...)


Los archivos de configuración ssh_config y sshd_config están iguales en los
dos equipos, en directorios ssh_config.d y sshd_config.d estàn vacìos en
ambos equipos.


¿Y deberían ser iguales? :-?


Los parámetros en los archivos de configuración están iguales, tienen la 
configuración por defecto al instalar Debian Bullseye, no se tocaron en 
ninguno de los dos equipos.



  

Desde el equipo al cual me quiero comunicar, al mío no tengo problemas, ssh
conecta sin problemas, el tema es cuando es al revés.

Alguien me puede dar alguna pista ?


Prueba a conectarte desde el propio equipo (ssh root@localhost).


Conecta perfectamente


Me desorienta que no me de algún mensaje más, alguna pista en el modo 
"verbose"...






Saludos,



--

Walter O. Dari

http://swcomputacion.com/
http://swcomputacion.com/sistemas/
https://facebook.com/swcomputacion/
https://facebook.com/sistemasSW/

Nuestros horarios:
L a V 8 a 13 hs.
S 11 a 14 hs.

WhatsApp:
2396 577140 (no se atienden llamadas)

Re: ssh no conecta (Bullseye en ambos equipos)

2021-05-15 Thread Walter Omar Dari 

Hola...

El 15/5/21 a las 13:55, OddieX escribió:

El sáb, 15 may 2021 a las 13:34, Walter Omar Dari
() escribió:


Hola...

El 15/5/21 a las 13:12, OddieX escribió:



El sáb., 15 de mayo de 2021 12:50, Walter Omar Dari mailto:wlin...@gmail.com>> escribió:

 Hola gente:

 Me quiero conectar a un equipo de la red local que antes tenía Buster y
 no había problemas, pero no puedo a partir de que le instalé Bullseye.
 No se si será por Bullseye u otro motivo.

 [...]




Disculpa! Ahi estoy en la PC! Espero que eliminando ssh y borrando
todo lo viejo y reinstalando se te haya solucionado!



No, desinstalé y purgué las configuraciones, reinstalé y sigo en la 
misma situación.





Saludos!

Offtopic: Mods, sepan discuparme, cambie de cel distinto cliente de
correo y no sabia como hacer reply sin formato!



Saludos,

--

Walter O. Dari

http://swcomputacion.com/
http://swcomputacion.com/sistemas/
https://facebook.com/swcomputacion/
https://facebook.com/sistemasSW/

Nuestros horarios:
L a V 8 a 13 hs.
S 11 a 14 hs.

WhatsApp:
2396 577140 (no se atienden llamadas)

Re: OT: minimum bs for dd?

2021-05-15 Thread IL Ka 
>
>
> As noted, is there a minimum bs size for dd?
>
It seems that you can set bs as small as 1.

512 is the default because of HDD block size which used to be 512 bytes for
more than 30 years (before advanced format was invented)



>

Re: OT: minimum bs for dd?

2021-05-15 Thread The Wanderer 
On 2021-05-15 at 16:19, Bob Bernstein wrote:

> As noted, is there a minimum bs size for dd?

Yes: 1. dd will not accept a block size of 0, never mind a negative
block size. You can try it yourself:

$ dd if=/dev/zero of=/tmp/1zerobyte bs=1 count=1
1+0 records in
1+0 records out
1 byte copied, 0.000117071 s, 8.5 kB/s

That said, block sizes below a certain value will give you reduced
performance et cetera; what that value is depends on the physical
characteristics of the underlying hardware.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: OT: minimum bs for dd?

2021-05-15 Thread Linux-Fan 

Bob Bernstein writes:


As noted, is there a minimum bs size for dd?


AFAIK its one byte.

HTH
Linux-Fan

öö


pgpQux2oMAtlK.pgp
Description: PGP signature

OT: minimum bs for dd?

2021-05-15 Thread Bob Bernstein 

As noted, is there a minimum bs size for dd?

Thank you.

--
I draw from the absurd three 
consequences, which are my revolt, 
my freedom, and my passion,


  Camus

Re: ssh no conecta (Bullseye en ambos equipos)

2021-05-15 Thread Camaleón 
El 2021-05-15 a las 12:49 -0300, Walter Omar Dari escribió:

> Me quiero conectar a un equipo de la red local que antes tenía Buster y no
> había problemas, pero no puedo a partir de que le instalé Bullseye. No se si
> será por Bullseye u otro motivo.

Además d elo que te han comentado, revisa las opciones de configuración 
de SSH en el sistema donde has puesto testing, quizá alguna opción te 
esté dando guerra.
 
> Cuando quiero conectar queda así...
> 
> dari@debwal:~$ ssh 192.168.0.8 -vvv
> OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1k  25 Mar 2021
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf
> matched no files
> debug1: /etc/ssh/ssh_config line 21: Applying options for *
> debug2: resolve_canonicalize: hostname 192.168.0.8 is address
> debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' ->
> '/home/wodari/.ssh/known_hosts'
> debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' ->
> '/home/wodari/.ssh/known_hosts2'
> debug2: ssh_connect_direct
> debug1: Connecting to 192.168.0.8 [192.168.0.8] port 22.
> 
> ... después de un rato da un error de timeout.

Un error de timeout apunta a que el anfitrión (el equipo al que 
conectas) corta la conexión por algún motivo (directiva de seguridad, 
etc.); si llegas con un ping al equipo, así a bote pronto el cortafuegos
quedaría descartado.

(...)

> Los archivos de configuración ssh_config y sshd_config están iguales en los
> dos equipos, en directorios ssh_config.d y sshd_config.d estàn vacìos en
> ambos equipos.

¿Y deberían ser iguales? :-?
 
> Desde el equipo al cual me quiero comunicar, al mío no tengo problemas, ssh
> conecta sin problemas, el tema es cuando es al revés.
> 
> Alguien me puede dar alguna pista ?

Prueba a conectarte desde el propio equipo (ssh root@localhost).

Saludos,

-- 
Camaleón

Re: ssh no conecta (Bullseye en ambos equipos)

2021-05-15 Thread OddieX 
El sáb, 15 may 2021 a las 13:34, Walter Omar Dari
() escribió:
>
> Hola...
>
> El 15/5/21 a las 13:12, OddieX escribió:
> >
> >
> > El sáb., 15 de mayo de 2021 12:50, Walter Omar Dari  > > escribió:
> >
> > Hola gente:
> >
> > Me quiero conectar a un equipo de la red local que antes tenía Buster y
> > no había problemas, pero no puedo a partir de que le instalé Bullseye.
> > No se si será por Bullseye u otro motivo.
> >
> > Cuando quiero conectar queda así...
> >
> > dari@debwal:~$ ssh 192.168.0.8 -vvv
> > OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1k  25 Mar 2021
> > debug1: Reading configuration data /etc/ssh/ssh_config
> > debug1: /etc/ssh/ssh_config line 19: include
> > /etc/ssh/ssh_config.d/*.conf matched no files
> > debug1: /etc/ssh/ssh_config line 21: Applying options for *
> > debug2: resolve_canonicalize: hostname 192.168.0.8 is address
> > debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' ->
> > '/home/wodari/.ssh/known_hosts'
> > debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' ->
> > '/home/wodari/.ssh/known_hosts2'
> > debug2: ssh_connect_direct
> > debug1: Connecting to 192.168.0.8 [192.168.0.8] port 22.
> >
> > ... después de un rato da un error de timeout.
> >
> >
> > En el equipo al que me quiero conectar, el puerto 22 parece estar
> > bien...
> >
> > # netstat -plnt
> > Active Internet connections (only servers)
> > Proto Recv-Q Send-Q Local Address   Foreign Address
> > State   PID/Program name
> > tcp0  0 127.0.0.1:53 
> > 0.0.0.0:*
> > LISTEN  652/connmand
> > tcp0  0 0.0.0.0:22 
> > 0.0.0.0:*
> > LISTEN  586057/sshd: /usr/s
> > tcp0  0 127.0.0.1:631 
> >   0.0.0.0:*
> > LISTEN  523630/cupsd
> > tcp0  0 0.0.0.0:44025 
> >   0.0.0.0:*
> > LISTEN  -
> > tcp0  0 127.0.0.1:25 
> > 0.0.0.0:*
> > LISTEN  1146/exim4
> > tcp0  0 0.0.0.0:17500 
> >   0.0.0.0:*
> > LISTEN  581546/dropbox
> > tcp0  0 127.0.0.1:17600 
> >   0.0.0.0:*
> > LISTEN  581546/dropbox
> > tcp0  0 127.0.0.1:17603 
> >   0.0.0.0:*
> > LISTEN  581546/dropbox
> > tcp0  0 0.0.0.0:111 
> >   0.0.0.0:*
> > LISTEN  1/init
> > tcp6   0  0 :::1716 :::*
> > LISTEN  580502/kdeconnectd
> > tcp6   0  0 ::1:53  :::*
> > LISTEN  652/connmand
> > tcp6   0  0 :::22   :::*
> > LISTEN  586057/sshd: /usr/s
> > tcp6   0  0 ::1:631 :::*
> > LISTEN  523630/cupsd
> > tcp6   0  0 :::41785:::*
> > LISTEN  -
> > tcp6   0  0 ::1:25  :::*
> > LISTEN  1146/exim4
> > tcp6   0  0 :::17500:::*
> > LISTEN  581546/dropbox
> > tcp6   0  0 :::111  :::*
> > LISTEN  1/init
> >
> > Los archivos de configuración ssh_config y sshd_config están iguales en
> > los dos equipos, en directorios ssh_config.d y sshd_config.d estàn
> > vacìos en ambos equipos.
> >
> > Desde el equipo al cual me quiero comunicar, al mío no tengo problemas,
> > ssh conecta sin problemas, el tema es cuando es al revés.
> >
> > Alguien me puede dar alguna pista ?
> >
> > Muchas gracias,
> > --
> >
> > Walter O. Dari
> >
> > http://swcomputacion.com/ 
> > http://swcomputacion.com/sistemas/ 
> > https://facebook.com/swcomputacion/
> > 
> > https://facebook.com/sistemasSW/ 
> >
> > Nuestros horarios:
> > L a V 8 a 13 hs.
> > S 11 a 14 hs.
> >
> > WhatsApp:
> > 2396 577140 (no se atienden llamadas)
> >
> >
> >
> >
> > 1
> >
> >
> > Probaste apt-get remove --purge ssh e instalar nuevamente apt-get
> > install ssh?
>
>
> La verdad no se me ocurrió, después de pasar por varias versiones de
> Debian en la primera vez que me pasa de no tener una pista, ni siquiera
> en los logs.
> Voy a probar, si se llega a solucionar lo comento aquí mismo.
>
> >
> > Perdon no se si esta sin formato el mensaje estoy con cel nuevo y no le
> > cazo la onda aun
> >
>
> No hay problemas, gracias por responder.
>
> Saludos,
>
>
> --
>
> Walter O. Dari
>
> http://swcomputacion.com/
> http://swcomputacion.com/sistemas/
> https://facebook.com/swcomputacion/
> https://facebook.com/sistemasSW/
>
> Nuestros horarios:
> L a V 8 a 13 hs.
> S 11

Re: Howto disable automounting of all removeable media

2021-05-15 Thread davidson 

On Sat, 15 May 2021 Richard Owlett wrote:

I have disabled auto-mounting of removable media on my Stretch
install with MATE.


Here was Brian's advice for doing this on jessie with MATE:

 https://lists.debian.org/debian-user/2015/09/msg01077.html
 [...]
 Try

  gsettings set org.mate.media-handling automount false

Maybe it still works?

I don't have a system appropriate to test it out on. You'll have to be
the guinea pig.


I wish to do the same with my new Buster machine.

I've forgotten how and Google etc gives plethora of irrelevant hits.


For me, the first hit on duckduckgo.com with search terms

 automount "Richard Owlett" site:lists.debian.org

was your reply to that message.

--
Ce qui est important est rarement urgent
et ce qui est urgent est rarement important
-- Dwight David Eisenhower

Re: ssh no conecta (Bullseye en ambos equipos)

2021-05-15 Thread Walter Omar Dari 

Hola...

El 15/5/21 a las 13:12, OddieX escribió:



El sáb., 15 de mayo de 2021 12:50, Walter Omar Dari > escribió:


Hola gente:

Me quiero conectar a un equipo de la red local que antes tenía Buster y
no había problemas, pero no puedo a partir de que le instalé Bullseye.
No se si será por Bullseye u otro motivo.

Cuando quiero conectar queda así...

dari@debwal:~$ ssh 192.168.0.8 -vvv
OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1k  25 Mar 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include
/etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolve_canonicalize: hostname 192.168.0.8 is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' ->
'/home/wodari/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' ->
'/home/wodari/.ssh/known_hosts2'
debug2: ssh_connect_direct
debug1: Connecting to 192.168.0.8 [192.168.0.8] port 22.

... después de un rato da un error de timeout.


En el equipo al que me quiero conectar, el puerto 22 parece estar
bien...

# netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address
State       PID/Program name
tcp        0      0 127.0.0.1:53    
0.0.0.0:*

LISTEN      652/connmand
tcp        0      0 0.0.0.0:22  
0.0.0.0:*

LISTEN      586057/sshd: /usr/s
tcp        0      0 127.0.0.1:631  
  0.0.0.0:*

LISTEN      523630/cupsd
tcp        0      0 0.0.0.0:44025  
  0.0.0.0:*

LISTEN      -
tcp        0      0 127.0.0.1:25    
0.0.0.0:*

LISTEN      1146/exim4
tcp        0      0 0.0.0.0:17500  
  0.0.0.0:*

LISTEN      581546/dropbox
tcp        0      0 127.0.0.1:17600    
  0.0.0.0:*

LISTEN      581546/dropbox
tcp        0      0 127.0.0.1:17603    
  0.0.0.0:*

LISTEN      581546/dropbox
tcp        0      0 0.0.0.0:111    
  0.0.0.0:*

LISTEN      1/init
tcp6       0      0 :::1716                 :::*
LISTEN      580502/kdeconnectd
tcp6       0      0 ::1:53                  :::*
LISTEN      652/connmand
tcp6       0      0 :::22                   :::*
LISTEN      586057/sshd: /usr/s
tcp6       0      0 ::1:631                 :::*
LISTEN      523630/cupsd
tcp6       0      0 :::41785                :::*
LISTEN      -
tcp6       0      0 ::1:25                  :::*
LISTEN      1146/exim4
tcp6       0      0 :::17500                :::*
LISTEN      581546/dropbox
tcp6       0      0 :::111                  :::*
LISTEN      1/init

Los archivos de configuración ssh_config y sshd_config están iguales en
los dos equipos, en directorios ssh_config.d y sshd_config.d estàn
vacìos en ambos equipos.

Desde el equipo al cual me quiero comunicar, al mío no tengo problemas,
ssh conecta sin problemas, el tema es cuando es al revés.

Alguien me puede dar alguna pista ?

Muchas gracias,
-- 


Walter O. Dari

http://swcomputacion.com/ 
http://swcomputacion.com/sistemas/ 
https://facebook.com/swcomputacion/

https://facebook.com/sistemasSW/ 

Nuestros horarios:
L a V 8 a 13 hs.
S 11 a 14 hs.

WhatsApp:
2396 577140 (no se atienden llamadas)




1


Probaste apt-get remove --purge ssh e instalar nuevamente apt-get
install ssh?



La verdad no se me ocurrió, después de pasar por varias versiones de 
Debian en la primera vez que me pasa de no tener una pista, ni siquiera 
en los logs.

Voy a probar, si se llega a solucionar lo comento aquí mismo.



Perdon no se si esta sin formato el mensaje estoy con cel nuevo y no le 
cazo la onda aun




No hay problemas, gracias por responder.

Saludos,


--

Walter O. Dari

http://swcomputacion.com/
http://swcomputacion.com/sistemas/
https://facebook.com/swcomputacion/
https://facebook.com/sistemasSW/

Nuestros horarios:
L a V 8 a 13 hs.
S 11 a 14 hs.

WhatsApp:
2396 577140 (no se atienden llamadas)

Re: ssh no conecta (Bullseye en ambos equipos)

2021-05-15 Thread OddieX 
El sáb., 15 de mayo de 2021 12:50, Walter Omar Dari 
escribió:

> Hola gente:
>
> Me quiero conectar a un equipo de la red local que antes tenía Buster y
> no había problemas, pero no puedo a partir de que le instalé Bullseye.
> No se si será por Bullseye u otro motivo.
>
> Cuando quiero conectar queda así...
>
> dari@debwal:~$ ssh 192.168.0.8 -vvv
> OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1k  25 Mar 2021
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: include
> /etc/ssh/ssh_config.d/*.conf matched no files
> debug1: /etc/ssh/ssh_config line 21: Applying options for *
> debug2: resolve_canonicalize: hostname 192.168.0.8 is address
> debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' ->
> '/home/wodari/.ssh/known_hosts'
> debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' ->
> '/home/wodari/.ssh/known_hosts2'
> debug2: ssh_connect_direct
> debug1: Connecting to 192.168.0.8 [192.168.0.8] port 22.
>
> ... después de un rato da un error de timeout.
>
>
> En el equipo al que me quiero conectar, el puerto 22 parece estar bien...
>
> # netstat -plnt
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address   Foreign Address
> State   PID/Program name
> tcp0  0 127.0.0.1:530.0.0.0:*
> LISTEN  652/connmand
> tcp0  0 0.0.0.0:22  0.0.0.0:*
> LISTEN  586057/sshd: /usr/s
> tcp0  0 127.0.0.1:631   0.0.0.0:*
> LISTEN  523630/cupsd
> tcp0  0 0.0.0.0:44025   0.0.0.0:*
> LISTEN  -
> tcp0  0 127.0.0.1:250.0.0.0:*
> LISTEN  1146/exim4
> tcp0  0 0.0.0.0:17500   0.0.0.0:*
> LISTEN  581546/dropbox
> tcp0  0 127.0.0.1:17600 0.0.0.0:*
> LISTEN  581546/dropbox
> tcp0  0 127.0.0.1:17603 0.0.0.0:*
> LISTEN  581546/dropbox
> tcp0  0 0.0.0.0:111 0.0.0.0:*
> LISTEN  1/init
> tcp6   0  0 :::1716 :::*
> LISTEN  580502/kdeconnectd
> tcp6   0  0 ::1:53  :::*
> LISTEN  652/connmand
> tcp6   0  0 :::22   :::*
> LISTEN  586057/sshd: /usr/s
> tcp6   0  0 ::1:631 :::*
> LISTEN  523630/cupsd
> tcp6   0  0 :::41785:::*
> LISTEN  -
> tcp6   0  0 ::1:25  :::*
> LISTEN  1146/exim4
> tcp6   0  0 :::17500:::*
> LISTEN  581546/dropbox
> tcp6   0  0 :::111  :::*
> LISTEN  1/init
>
> Los archivos de configuración ssh_config y sshd_config están iguales en
> los dos equipos, en directorios ssh_config.d y sshd_config.d estàn
> vacìos en ambos equipos.
>
> Desde el equipo al cual me quiero comunicar, al mío no tengo problemas,
> ssh conecta sin problemas, el tema es cuando es al revés.
>
> Alguien me puede dar alguna pista ?
>
> Muchas gracias,
> --
>
> Walter O. Dari
>
> http://swcomputacion.com/
> http://swcomputacion.com/sistemas/
> https://facebook.com/swcomputacion/
> https://facebook.com/sistemasSW/
>
> Nuestros horarios:
> L a V 8 a 13 hs.
> S 11 a 14 hs.
>
> WhatsApp:
> 2396 577140 (no se atienden llamadas)
>
>
>
>
> 1


Probaste apt-get remove --purge ssh e instalar nuevamente apt-get install
ssh?


Perdon no se si esta sin formato el mensaje estoy con cel nuevo y no le
cazo la onda aun

Re: RESOLUTION --- Re: How to reference xxxdvd1.iso in sources.list

2021-05-15 Thread Thomas Schmitt 
Hi,

Richard Owlett wrote:
> IIRC there was a limit on the number of loop devices created {8?}.
> Is there any default limit now?

That would be
  man losetup
and
  https://www.kernel.org/doc/Documentation/admin-guide/devices.txt

The former seems to tell no limitation.
The latter lists "loopback devices" for "major" number 7 with unlimited
range for the "minor" device number. The "minor" number is the one that
gets appended to the "/dev/loop" name.
IIRC this "unlimited" range traditionally means 0 to 255. But the dev_t
variable in the result of stat(2) reserves 20 bits for the minor number:
  https://github.com/torvalds/linux/blob/master/include/linux/kdev_t.h

So this numbering might reach up to a million.

As experiment, a normal user creates a file of 1 MiB

  $ dd if=/dev/zero bs=1M count=1 of=/tmp/loop_test
  1+0 records in
  1+0 records out
  1048576 bytes (1.0 MB) copied, 0.00240163 s, 437 MB/s
  $

and the superuser connects it to loop device 1000:

  # losetup /dev/loop1000 /tmp/loop_test
  #

Checking the status of the device looks ok:

  # losetup /dev/loop1000
  /dev/loop1000: [2066]:5899 (/tmp/loop_test)
  #

(Don't ask me what the numbers mean ...)

To remove the device association:

  # losetup -d /dev/loop1000
  # losetup /dev/loop1000
  losetup: /dev/loop1000: No such file or directory
  #

Despite the error message the device file still exists.

  $ ls -l /dev/loop1000
  brw-rw 1 root disk 7, 1000 May 15 17:34 /dev/loop1000

(This is a fine example why any re-use of Unix error numbers should be well
thought. Here it was not so well done. losetup names the device file but
reports about its lack of association to a data file. That data file does
still exist, too. So no file is missing here.)

Now i remove the file /tmp/loop_test, but keep the device file
/dev/loop1000 out of superstition. It brings bad luck to delete in /dev.


> Also, I notice the phrase "auto-destruction of loop devices".

Reading the whole phrase it becomes clear that this is just about properly
cleaning up after umount:

  Since Linux 2.6.25 auto-destruction of loop devices is supported, mean‐
  ing  that  any  loop  device allocated by mount will be freed by umount
  independently of /etc/mtab.

> Might I lose one (or more) of my loop devices
> without some intentional explicit action by me?

You lose the association, which was created by mount.
I expect that you don't lose the device file. But even if the device file
vanishes, the next mount or losetup will create it again, if that same
loop device number is desired.

I use loop mounting often and did not notice any special risk of it.


Have a nice day :)

Thomas

ssh no conecta (Bullseye en ambos equipos)

2021-05-15 Thread Walter Omar Dari 

Hola gente:

Me quiero conectar a un equipo de la red local que antes tenía Buster y 
no había problemas, pero no puedo a partir de que le instalé Bullseye. 
No se si será por Bullseye u otro motivo.


Cuando quiero conectar queda así...

dari@debwal:~$ ssh 192.168.0.8 -vvv
OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1k  25 Mar 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include 
/etc/ssh/ssh_config.d/*.conf matched no files

debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolve_canonicalize: hostname 192.168.0.8 is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> 
'/home/wodari/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> 
'/home/wodari/.ssh/known_hosts2'

debug2: ssh_connect_direct
debug1: Connecting to 192.168.0.8 [192.168.0.8] port 22.

... después de un rato da un error de timeout.


En el equipo al que me quiero conectar, el puerto 22 parece estar bien...

# netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address 
State   PID/Program name
tcp0  0 127.0.0.1:530.0.0.0:* 
LISTEN  652/connmand
tcp0  0 0.0.0.0:22  0.0.0.0:* 
LISTEN  586057/sshd: /usr/s
tcp0  0 127.0.0.1:631   0.0.0.0:* 
LISTEN  523630/cupsd
tcp0  0 0.0.0.0:44025   0.0.0.0:* 
LISTEN  -
tcp0  0 127.0.0.1:250.0.0.0:* 
LISTEN  1146/exim4
tcp0  0 0.0.0.0:17500   0.0.0.0:* 
LISTEN  581546/dropbox
tcp0  0 127.0.0.1:17600 0.0.0.0:* 
LISTEN  581546/dropbox
tcp0  0 127.0.0.1:17603 0.0.0.0:* 
LISTEN  581546/dropbox
tcp0  0 0.0.0.0:111 0.0.0.0:* 
LISTEN  1/init
tcp6   0  0 :::1716 :::* 
LISTEN  580502/kdeconnectd
tcp6   0  0 ::1:53  :::* 
LISTEN  652/connmand
tcp6   0  0 :::22   :::* 
LISTEN  586057/sshd: /usr/s
tcp6   0  0 ::1:631 :::* 
LISTEN  523630/cupsd
tcp6   0  0 :::41785:::* 
LISTEN  -
tcp6   0  0 ::1:25  :::* 
LISTEN  1146/exim4
tcp6   0  0 :::17500:::* 
LISTEN  581546/dropbox
tcp6   0  0 :::111  :::* 
LISTEN  1/init


Los archivos de configuración ssh_config y sshd_config están iguales en 
los dos equipos, en directorios ssh_config.d y sshd_config.d estàn 
vacìos en ambos equipos.


Desde el equipo al cual me quiero comunicar, al mío no tengo problemas, 
ssh conecta sin problemas, el tema es cuando es al revés.


Alguien me puede dar alguna pista ?

Muchas gracias,
--

Walter O. Dari

http://swcomputacion.com/
http://swcomputacion.com/sistemas/
https://facebook.com/swcomputacion/
https://facebook.com/sistemasSW/

Nuestros horarios:
L a V 8 a 13 hs.
S 11 a 14 hs.

WhatsApp:
2396 577140 (no se atienden llamadas)

Re: Old 32 bits application

2021-05-15 Thread Nicolas FRANCOIS 
Le Sat, 15 May 2021 11:07:06 +0200,
Nicolas FRANCOIS  a écrit :

> Hi.
> 
> I have an old application, MuPAD 4.0.6, that I was able to launch on
> my previous Debian installations, mais with the last installation
> (Debian 10.9), I can't seem to be able to do this anymore.

I managed to copy the installation directory from my previous Debian...
And now it works. The only difference is a libz.so.? that I had renamed
libz.so.?.sav, don't know why, but it seems to do the trick :-?

Thanks for your answers, anyway ;-)

\bye

-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


pgpnS_GKNTX0M.pgp
Description: Signature digitale OpenPGP

Re: Vieille application 32 bits

2021-05-15 Thread Nicolas FRANCOIS 
Le Sat, 15 May 2021 10:46:19 +0200,
Nicolas FRANCOIS  a écrit :

> Salut.
> 
> J'ai une vieille application, MuPAD 4.0.6, que j'arrivais jusqu'ici à
> faire fonctionner sur mes Debian successives, mais après la dernière
> installation (Debian 10.9), je n'arrive plus à la lancer.

Merci pour votre aide. J'ai retrouvé l'ancien répertoire
d'installation, il semble que le seul problème était une libz.so.? dans
le répertoire lib que j'avais renommée en libz.so.?.sav... Et ça résout
le problème...

Des fois, il vaut mieux ne pas chercher à comprendre :-(

Encore merci à ceux qui se sont penchés sur mon problème :-)

\bye

-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


pgpQ8K1dLOFgk.pgp
Description: Signature digitale OpenPGP

light-locker focus on password

2021-05-15 Thread Keith Edmunds 
Running Bullseye with XFCE. light-locker is running.

When the PC is locked, by default it is the username field that has focus
rather than the password field. Most screen lockers focus on the password
field. If I just start typing my password, it appears in the username
field and is in plain text for all to see.

Is it possible to force light-locker to focus on the password field by
default?
-- 
"When I said I was going to become a comedian, they all laughed at me.
Well, they're not laughing now" - Bob Monkhouse

Re: RESOLUTION --- Re: How to reference xxxdvd1.iso in sources.list

2021-05-15 Thread Richard Owlett 

On 05/15/2021 07:18 AM, Thomas Schmitt wrote:

Hi,

Richard Owlett wrote:

I don't grok loop devices. [...]
Also the article I read evidently took advantage of "mount" being able to
loop mount without the loop option being explicitly referenced.


Yes. mount is smart enough to see that your "device" is a data file and
that it has to use a loop device.
A little test as superuser with already existing directory /mnt/iso:

   # mount debian-10.6.0-amd64-netinst.iso /mnt/iso
   mount: /dev/loop0 is write-protected, mounting read-only
   # ls /mnt/iso
   EFI
   ...
   win32-loader.ini

So it used the existing /dev/loop0. If no idle loop device is available
then it will create a new one.

See in man mount the section
   THE LOOP DEVICE



I wish to have the ISO's of all install DVDs on a dedicated
partition of my hard drive as a local repository.


You could mount them all, e.g. by a script which knows all their names
and the desired mount points. Each mount point would need its own line
in sources.list.



That raises a couple of questions.

IIRC there was a limit on the number of loop devices created {8?}.
Is there any default limit now?

Also, I notice the phrase "auto-destruction of loop devices".
That raises a red flag. Might I lose one (or more) of my loop devices 
without some intentional explicit action by me?


[snip discussion of extracting pool directories and possible uses of 
xorriso for possible later discussion]


Thanks.

Re: Vieille application 32 bits

2021-05-15 Thread Christophe Maquaire 
Le samedi 15 mai 2021 à 10:46 +0200, Nicolas FRANCOIS a écrit :
> Salut
Hello,
> J'ai une vieille application, MuPAD 4.0.6, que j'arrivais jusqu'ici à
> faire fonctionner sur mes Debian successives, mais après la dernière
> installation (Debian 10.9), je n'arrive plus à la lancer.
> 
> Dans le répertoire /opt/MuPAD-406, il y a un répertoire linux dans
> lequel se trouve le binaire mupad, et une série de librairies.
OK,
> 
> nico@gaston:~$ mupad
> ERROR: ld.so: object '/opt/MuPAD-406/linux/lib/libGLU.so.1' from
> LD_PRELOAD cannot be preloaded (cannot open shared object file):
> ignored. /opt/MuPAD-4.0.6/linux/bin/mupad: error while loading shared
> libraries: libmupvrs_qt.so.1.0.0: cannot open shared object file: No
> such file or directory
> 

Je ne connais rien à MuPAD, mais le message d'erreur indique 2 chemins
différents
/opt/MuPAD-4.0.6/linux/bin/mupad
et
/opt/MuPAD-406/linux/lib/libGLU.so.1

ainsi que 

No such file or directory

Il me semble que ton problème vient d'un mélange 406 et 4.0.6,
j'aurais tendance à créer un lien de l'inexistant vers l'existant pour
le résoudre. (ou à chercher les confusions 406 / 4.0.6)


Librement,
Christophe

Re: Vieille application 32 bits

2021-05-15 Thread Polyna-Maude Racicot-Summerside 
Salut.
As-tu installe l'architecture i386 ?
dpkg --add-architecture i386
Puis par la suite lesl librairies specifiques utilisees par ce logiciel.
Tu peux aussi expliquer un peu plus l'erreur que tu recois, ceci
aiderait a pouvoir t'aider.

> On 2021-05-15 4:46 a.m., Nicolas FRANCOIS wrote:
>> Salut.
>>
>> J'ai une vieille application, MuPAD 4.0.6, que j'arrivais jusqu'ici à
>> faire fonctionner sur mes Debian successives, mais après la dernière
>> installation (Debian 10.9), je n'arrive plus à la lancer.
>>
>> Dans le répertoire /opt/MuPAD-406, il y a un répertoire linux 
> dans
>> lequel se trouve le binaire mupad, et une série de librairies. Le
>> script de lancement est le suivant :
>>
>> <--- début /opt/MuPAD-406/share/bin/mupad --->
>> #!/bin/sh
>>
>> SHARE_BIN=`dirname "$0"`
>>
>> if test `basename "${SHARE_BIN}"` = bin  ; then
>>   SHARE=`dirname "${SHARE_BIN}"`
>>   if test `basename "${SHARE}"` = share ; then
>> MuPAD_ROOT_PATH=`dirname "${SHARE}"`
>>   else
>> MuPAD_ROOT_PATH=..
>>   fi
>> else
>>   MuPAD_ROOT_PATH=../..
>> fi
>> export MuPAD_ROOT_PATH
>>
>> if [ ! -s /usr/share/fonts/sciface/sfmatext.ttf -a ! -s
>> ~/.fonts/sfmatext.ttf ] ; then if [ ! -d ~/.fonts ] ; then
>> mkdir ~/.fonts/
>> fi
>> (cd "${MuPAD_ROOT_PATH}/share/fonts/";  cp * ~/.fonts/)
>> fi
>>
>> SYSINFO=`${MuPAD_ROOT_PATH}/share/bin/sysinfo`
>>
>> # echo ${MuPAD_ROOT_PATH}/${SYSINFO}
>> # LD_LIBRARY_PATH="${MuPAD_ROOT_PATH}/${SYSINFO}/lib:${LD_LIBRARY_PATH}"
>> LD_LIBRARY_PATH="/opt/MuPAD-406/linux/lib:${LD_LIBRARY_PATH}"
>> export LD_LIBRARY_PATH
>>
>> # workaround for problems with accelerated NVidia hardware on 64 bit
>> systems LD_PRELOAD=/opt/MuPAD-406/linux/lib/libGLU.so.1
>> "${MuPAD_ROOT_PATH}/${SYSINFO}/bin/mupad" "$@" 
>> # "${MuPAD_ROOT_PATH}/${SYSINFO}/bin/mupad" "$@"
>> <--- fin /opt/MuPAD-406/share/bin/mupad --->
>>
>> J'ai dû le tweaker un peu, parce qu'il ne réglait pas correctement la
>> variable LD_LIBRARY_PATH (je ne comprends pas pourquoi.
>>
>> Donc cette variable est réglée sur /opt/MuPAD-406/linux/lib, 
mais
>> j'obtiens ce genre de message :
>>
>> nico@gaston:~$ mupad
>> ERROR: ld.so: object '/opt/MuPAD-406/linux/lib/libGLU.so.1' from
>> LD_PRELOAD cannot be preloaded (cannot open shared object file):
>> ignored. /opt/MuPAD-4.0.6/linux/bin/mupad: error while loading shared
>> libraries: libmupvrs_qt.so.1.0.0: cannot open shared object file: No
>> such file or directory
>>
>> J'imagine que c'est parce que ce sont des librairies 32 bits, mais j'ai
>> activé l'architecture 32 bits pour Steam, donc normalement, ça ne
>> devrait pas poser de problème, si ?
>>
>> Avant, ça fonctionnait correctement, là, je suis un peu perdu.
>>
>> Quelqu'un a une idée de ce que je pourrais faire ?
>>
>> D'avance merci, et surtout merci aux courageux qui m'ont lu
>> jusqu'ici ;-)
>>
>> \bye
>>
> 

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



OpenPGP_signature
Description: OpenPGP digital signature

Re: RESOLUTION --- Re: How to reference xxxdvd1.iso in sources.list

2021-05-15 Thread Thomas Schmitt 
Hi,

Richard Owlett wrote:
> I don't grok loop devices. [...]
> Also the article I read evidently took advantage of "mount" being able to
> loop mount without the loop option being explicitly referenced.

Yes. mount is smart enough to see that your "device" is a data file and
that it has to use a loop device.
A little test as superuser with already existing directory /mnt/iso:

  # mount debian-10.6.0-amd64-netinst.iso /mnt/iso
  mount: /dev/loop0 is write-protected, mounting read-only
  # ls /mnt/iso
  EFI
  ...
  win32-loader.ini

So it used the existing /dev/loop0. If no idle loop device is available
then it will create a new one.

See in man mount the section
  THE LOOP DEVICE


> I wish to have the ISO's of all install DVDs on a dedicated
> partition of my hard drive as a local repository.

You could mount them all, e.g. by a script which knows all their names
and the desired mount points. Each mount point would need its own line
in sources.list.

-
Alternative:

Or you could also copy the ./pool trees of the one-by-one mounted ISOs to
a ./pool directory in the filesystem of your dedicated partition.

I understand that sources.list will then want the directory above ./pool
as source for packages. I.e. if you copy to
  /your/partition/pool
then it wants to see in the deb line
  /your/partition

Possibly you will have to set in that line the option
  [trusted=yes]
to compensate the lack of a skilled Debian setup in your copied tree.

-
Alternative:

For copying without being superuser and without mounting the ISO, you could
use xorriso. Like:

  ISO_PATH=./debian-10.6.0-amd64-netinst.iso
  xorriso -osirrox on:auto_chmod_on \
  -indev "$ISO_PATH" \
  -extract /pool /your/partition/pool

The option "auto_chmod_on" of xorriso command -osirrox causes:
  [that] access  restrictions  for  disk  directories get circumvented if
  those directories are owned  by  the  effective  user  who  runs
  xorriso.  This happens by temporarily granting rwx permission to
  the owner.
The first ISO extraction will work without this option. But when copying
multiple trees from ISOs to disk, it will enable xorriso to write into the
previously created directories under /your/partition/pool and to overwrite
existing files in that tree. Both is elsewise hampered by the fact that
xorriso copies the access permissions from the ISOs, where they are set to
be read-only.

-
Alternative:

Another method would be to let xorriso change the permissions in the ISO
before extraction and to tell it to discard the permission changes rather
than trying to write them as new session:

  xorriso -osirrox on \
  -indev "$ISO_PATH" \
  -chmod_r u+rw /pool -- \
  -extract /pool /your/partition/pool \
  -rollback_end

The "--" after -chmod_r is important because it ends the list of paths
to manipulate.
The command -rollback_end prevents the attempt to write a new session after
you made changes to the loaded ISO. Without it (and without an -outdev)
you would get an error message after successfule extraction:
  xorriso : FAILURE : No output drive acquired on attempt to write
and the exit value would be non-zero.

The extracted files will not be read-only afterwards. This eases manipulation
and removal of the pool tree, but also gives no protection against removal
by mistake. Read-only trees will need superuser power or a run of chmod -R
before you can remove files or the whole tree.


Have a nice day :)

Thomas

Howto disable automounting of all removeable media

2021-05-15 Thread Richard Owlett 
I have disabled auto-mounting of removable media on my Stretch install 
with MATE.


I wish to do the same with my new Buster machine.

I've forgotten how and Google etc gives plethora of irrelevant hits.

Help please.
TIA

Re: Vieille application 32 bits

2021-05-15 Thread raivac 
Si c'est cette application:
https://fr.m.wikipedia.org/wiki/MuPAD

Elle a été reprise:
https://fr.mathworks.com/products/symbolic.html
-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Re: Old 32 bits application

2021-05-15 Thread deloptes 
Nicolas FRANCOIS wrote:

> So I'm stuck. The 32 bits architecture is set (for Steam), so this
> could'nt be the problem? And it used to work on Debian 10...
> 
> If someone has an idea, I'm all ears :-)

AFAIK Debian 11 does not offer Qt4 which obviously is used by the app.

Perhaps consider using a jail or chroot or just a copy of the libraries are
needed.

RESOLUTION --- Re: How to reference xxxdvd1.iso in sources.list

2021-05-15 Thread Richard Owlett 

On 05/12/2021 02:05 PM, Richard Owlett wrote:

I've seen a reference to using the ISO file of DVDnn in a sources.list .
I remember that it gets identified as being ISO9660 and labeled as 
trusted, But I can't find a detailed example. All I find are references 
to unpacking the iso to a directory which is then loop mounted. That's 
not what I'm looking for.

Pointers please.
TIA


Exactly what I was looking for does not exist.
I had a poor recollection of a partially understood article.

I don't grok loop devices. Wikipedia summarizes by saying "In Unix-like 
operating systems, a loop device ... is a pseudo-device that makes a 
computer file accessible as a block device."


Also the article I read evidently took advantage of "mount" being able 
to loop mount without the loop option being explicitly referenced.


I have a machine dedicated to install experiments and a low data cap on 
my internet access. I wish to have the ISO's of all install DVDs on a 
dedicated partition of my hard drive as a local repository.

Old 32 bits application

2021-05-15 Thread Nicolas FRANCOIS 
Hi.

I have an old application, MuPAD 4.0.6, that I was able to launch on my
previous Debian installations, mais with the last installation (Debian
10.9), I can't seem to be able to do this anymore.

In folder /opt/MuPAD-406, there is a linux folder with bin/mupad
binary, and lib/several_32bits_libs. The starting script, in
share/bin, is like this :

<--- begin /opt/MuPAD-406/share/bin/mupad --->
#!/bin/sh

SHARE_BIN=`dirname "$0"`

if test `basename "${SHARE_BIN}"` = bin  ; then
  SHARE=`dirname "${SHARE_BIN}"`
  if test `basename "${SHARE}"` = share ; then
MuPAD_ROOT_PATH=`dirname "${SHARE}"`
  else
MuPAD_ROOT_PATH=..
  fi
else
  MuPAD_ROOT_PATH=../..
fi
export MuPAD_ROOT_PATH

if [ ! -s /usr/share/fonts/sciface/sfmatext.ttf -a ! -s
~/.fonts/sfmatext.ttf ] ; then if [ ! -d ~/.fonts ] ; then
mkdir ~/.fonts/
fi
(cd "${MuPAD_ROOT_PATH}/share/fonts/";  cp * ~/.fonts/)
fi

SYSINFO=`${MuPAD_ROOT_PATH}/share/bin/sysinfo`

# echo ${MuPAD_ROOT_PATH}/${SYSINFO}
# LD_LIBRARY_PATH="${MuPAD_ROOT_PATH}/${SYSINFO}/lib:${LD_LIBRARY_PATH}"
LD_LIBRARY_PATH="/opt/MuPAD-406/linux/lib:${LD_LIBRARY_PATH}"
export LD_LIBRARY_PATH

# workaround for problems with accelerated NVidia hardware on 64 bit
systems 
# LD_PRELOAD=/opt/MuPAD-406/linux/lib/libGLU.so.1
"${MuPAD_ROOT_PATH}/${SYSINFO}/bin/mupad" "$@" 
"${MuPAD_ROOT_PATH}/${SYSINFO}/bin/mupad" "$@" 
<--- end /opt/MuPAD-406/share/bin/mupad --->

I was forced to tweak it a little, because the LD_LIBRARY_PATH
variable didn't seem to be set correctly (I don't understand why).

With this variable set to /opt/MuPAD-406/linux/lib, I get this kind
of message :

nico@gaston:~$ mupad
ERROR: ld.so: object '/opt/MuPAD-406/linux/lib/libGLU.so.1' from
LD_PRELOAD cannot be preloaded (cannot open shared object file):
ignored. /opt/MuPAD-4.0.6/linux/bin/mupad: error while loading shared
libraries: libmupvrs_qt.so.1.0.0: cannot open shared object file: No
such file or directory

If I launch it without the workaround for Nvidia, I get this
kind of message for a normal account :

nico@gaston:/opt/MuPAD-4.0.6/linux/lib$ mupad
/opt/MuPAD-4.0.6/linux/bin/mupad: libz.so.1: no version information
available (required
by /lib/i386-linux-gnu/libpng16.so.16) /opt/MuPAD-4.0.6/linux/bin/mupad:
libz.so.1: no version information available (required
by /lib/i386-linux-gnu/libpng16.so.16) /opt/MuPAD-4.0.6/linux/bin/mupad:
relocation error: /lib/i386-linux-gnu/libpng16.so.16: symbol
inflateReset2 version ZLIB_1.2.3.4 not defined in file libz.so.1 with
link time reference

And from a root account :
root@gaston:/opt/MuPAD-4.0.6/share/bin# mupad
/opt/MuPAD-4.0.6/linux/bin/mupad: error while loading shared libraries:
libmupvrs_qt.so.1.0.0: cannot open shared object file: No such file or
directory

but:
nico@gaston:/opt/MuPAD-4.0.6/linux/lib$ ls -l
total 15412
drwxr-sr-x 2 root root4096 avril 23 12:46 gcclibs
-rw-r--r-- 1 root root  131388 déc.  31  2007 libexpat.so.1.0.0
drwxr-sr-x 2 root root4096 avril 23 12:46 libGLU
-rw-r--r-- 1 root root  507712 déc.  31  2007 libGLU.so.1
-rw-r--r-- 1 root root  120076 déc.  31  2007 libjpeg.so.62
-rwxr-xr-x 1 root root 2658980 déc.  31  2007 libmupvrs_qt.so.1.0.0
-rw-r--r-- 1 root root  179268 déc.  31  2007 libpng.so.3
-rwxr-xr-x 1 root root 3084596 déc.  31  2007 libQt3Support.so.4
-rwxr-xr-x 1 root root 1940548 déc.  31  2007 libQtCore.so.4
-rwxr-xr-x 1 root root 5621352 déc.  31  2007 libQtGui.so.4
-rwxr-xr-x 1 root root  385460 déc.  31  2007 libQtNetwork.so.4
-rwxr-xr-x 1 root root  188752 déc.  31  2007 libQtOpenGL.so.4
-rwxr-xr-x 1 root root  228472 déc.  31  2007 libQtSql.so.4
-rwxr-xr-x 1 root root  315244 déc.  31  2007 libQtXml.so.4
-rw-r--r-- 1 root root  269124 déc.  31  2007 libtiff.so.3
-rw-r--r-- 1 root root   55432 déc.  31  2007 libz.so
-rw-r--r-- 1 root root   55432 déc.  31  2007 libz.so.1

So I'm stuck. The 32 bits architecture is set (for Steam), so this
could'nt be the problem? And it used to work on Debian 10...

If someone has an idea, I'm all ears :-)

Thanks for any help.

\bye

-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


pgpk_rlnHvpg7.pgp
Description: Signature digitale OpenPGP

Vieille application 32 bits

2021-05-15 Thread Nicolas FRANCOIS 
Salut.

J'ai une vieille application, MuPAD 4.0.6, que j'arrivais jusqu'ici à
faire fonctionner sur mes Debian successives, mais après la dernière
installation (Debian 10.9), je n'arrive plus à la lancer.

Dans le répertoire /opt/MuPAD-406, il y a un répertoire linux dans
lequel se trouve le binaire mupad, et une série de librairies. Le
script de lancement est le suivant :

<--- début /opt/MuPAD-406/share/bin/mupad --->
#!/bin/sh

SHARE_BIN=`dirname "$0"`

if test `basename "${SHARE_BIN}"` = bin  ; then
  SHARE=`dirname "${SHARE_BIN}"`
  if test `basename "${SHARE}"` = share ; then
MuPAD_ROOT_PATH=`dirname "${SHARE}"`
  else
MuPAD_ROOT_PATH=..
  fi
else
  MuPAD_ROOT_PATH=../..
fi
export MuPAD_ROOT_PATH

if [ ! -s /usr/share/fonts/sciface/sfmatext.ttf -a ! -s
~/.fonts/sfmatext.ttf ] ; then if [ ! -d ~/.fonts ] ; then
mkdir ~/.fonts/
fi
(cd "${MuPAD_ROOT_PATH}/share/fonts/";  cp * ~/.fonts/)
fi

SYSINFO=`${MuPAD_ROOT_PATH}/share/bin/sysinfo`

# echo ${MuPAD_ROOT_PATH}/${SYSINFO}
# LD_LIBRARY_PATH="${MuPAD_ROOT_PATH}/${SYSINFO}/lib:${LD_LIBRARY_PATH}"
LD_LIBRARY_PATH="/opt/MuPAD-406/linux/lib:${LD_LIBRARY_PATH}"
export LD_LIBRARY_PATH

# workaround for problems with accelerated NVidia hardware on 64 bit
systems LD_PRELOAD=/opt/MuPAD-406/linux/lib/libGLU.so.1
"${MuPAD_ROOT_PATH}/${SYSINFO}/bin/mupad" "$@" 
# "${MuPAD_ROOT_PATH}/${SYSINFO}/bin/mupad" "$@"
<--- fin /opt/MuPAD-406/share/bin/mupad --->

J'ai dû le tweaker un peu, parce qu'il ne réglait pas correctement la
variable LD_LIBRARY_PATH (je ne comprends pas pourquoi.

Donc cette variable est réglée sur /opt/MuPAD-406/linux/lib, mais
j'obtiens ce genre de message :

nico@gaston:~$ mupad
ERROR: ld.so: object '/opt/MuPAD-406/linux/lib/libGLU.so.1' from
LD_PRELOAD cannot be preloaded (cannot open shared object file):
ignored. /opt/MuPAD-4.0.6/linux/bin/mupad: error while loading shared
libraries: libmupvrs_qt.so.1.0.0: cannot open shared object file: No
such file or directory

J'imagine que c'est parce que ce sont des librairies 32 bits, mais j'ai
activé l'architecture 32 bits pour Steam, donc normalement, ça ne
devrait pas poser de problème, si ?

Avant, ça fonctionnait correctement, là, je suis un peu perdu.

Quelqu'un a une idée de ce que je pourrais faire ?

D'avance merci, et surtout merci aux courageux qui m'ont lu
jusqu'ici ;-)

\bye

-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


pgpQLC6c0UEwv.pgp
Description: Signature digitale OpenPGP

[OT] developing envelopes [was: Printing addresses on a #10 envelope (US)?]

2021-05-15 Thread tomas 
On Sat, May 15, 2021 at 08:11:49AM +, Curt wrote:

[...]

> It wasn't near wordplay; it was definitely a *calembour*.

Ooooh, a new word: thanks for the gift :)

Cheers
 - t


signature.asc
Description: Digital signature

Re: Printing addresses on a #10 envelope (US)?

2021-05-15 Thread Curt 
On 2021-05-11,   wrote:
>
> That is so near a wordplay that I wonder whether it was
> intentional. Envelopers who use developes?
>

To develop is to free from that which envelops; envelop denotes to
enclose or enfold whereas develop means to unfold, make visible.
The two terms in their primary senses are antithetical.

It wasn't near wordplay; it was definitely a *calembour*.

Re: Thunderbird: how can I set permanent custom headers?

2021-05-15 Thread tomas 
[...]

> I added:
> 
> 
> user_pref("mail.identity.id1.headers", "archive");
> user_pref("mail.identity.id1.header.archive", "X-No-Archive: yes");

[...]

I quote part of the headers I see in your mail:

 | User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 | Thunderbird/78.3.1
 | X-No-Archive: yes
 | In-Reply-To: 
 | Content-Language: en-GB

...so it seems to work.

Cheers
 - t


signature.asc
Description: Digital signature

Re: Thunderbird: how can I set permanent custom headers?

2021-05-15 Thread Jonathan Dowland 

On Fri, May 14, 2021 at 08:13:56PM +0100, Ottavio Caruso wrote:
Groups.io are not official Thunderbird mailing lists. Anybody can 
create a Debian-devel mailing list on groups.io.


debian-user is not an official Thunderbird list either. At least
everyone on those groups.io lists will be familiar with Thunderbird.


--
Please do not CC me, I am subscribed to the list.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: Thunderbird: how can I set permanent custom headers?

2021-05-15 Thread didier gaumet 

Le 14/05/2021 à 21:13, Ottavio Caruso a écrit :

Groups.io are not official Thunderbird mailing lists. Anybody can create 
a Debian-devel mailing list on groups.io.


Hello,

You may ask a question on the Thunderbird official forum there:
https://support.mozilla.org/en-US/questions/new