Re: OFF TOPIC - Problemas com mysql

[Mauricio Neto]

Amigos boa noite.

Quero agradecer a todos que me auxiliaram para solução do problema.

Hélio seu "chute" sobre estar usando dois processos mysql foi 
fundamental para solucionar o problema. Não estava com dois processos 
mysql mais configurações apontando para sockets diferentes, um apontando 
para/*/var/run*/mysqld/mysqld.sock /e outro para 
/*/run/*mysqld///mysqld.sock/. Por você ter "levantado essa bola" eu 
segui este caminho e encontrei o problema.


Alias o diretório//etc/mysql /criado por padrão na instalação do mysql 
com seus diversos arquivos de configuração parece ter sido criado 
propositalmente para testar a atenção e paciência ... :-)


Mas o importante é que esta resolvido.

Muito obrigado a todos,

Mauricio Neto

Em 25/04/2022 20:14, Mauricio Neto escreveu:


Helio boa tarde.

Achei interessante seu "chute" mas veja se estou com o raciocino errado:

No /etc/mysql/mysql.conf.d/mysqld.cnf

/[mysqld]//
//pid-file    = /var/run/mysqld/mysqld.pid//
//*socket  = /var/run/mysqld/mysqld.sock*//
//datadir = /dbase/mysql//
//log-error   = /var/log/mysql/error.log/

processos mysql:

/# netstat -ln | grep mysql
unix  2  [ ACC ] STREAM OUVINDO   18942 
/var/run/mysqld/mysqlx.sock
unix  2  [ ACC ] STREAM OUVINDO   18945 
/var/run/mysqld/mysqld.sock/


/# ps -ef |grep mysql//
//mysql   2812   1  0 17:04 ?    00:00:19 /usr/sbin/mysqld//
//root    3332    2541  0 18:15 pts/0    00:00:00 grep mysql/

O que me leva a crer que estou com apenas um processo mysql em 
execução e usando sockets.


mais isso me deixou com uma duvida:

/# netstat -tl | grep mys
tcp6   0  0 [::]:mysql [::]:*  OUÇA/

Obrigado

Mauricio Neto


Em 24/04/2022 11:24, Helio Loureiro escreveu:

Quando você conecta com o client, ele usa o arquivo de socket pra isso.

Eu chuto que o problema é que vc tem dois mysqld rodando.  Uma via 
TCP que parece estar certo, mas via socket entra no errado que parece 
ser um banco zerado (possivelmente a configuração default do MySQL).


./helio

On Sat, Apr 23, 2022, 16:05 Mauricio Neto  wrote:

Gustavo, bom dia e obrigado pelo retorno

É pratica minha  criar um filesystem separado para o database.
Então logo após a instalação do mysql, antes da instalação de
qualquer aplicativo que vá utilizar o banco, eu para o processo ,
copio os arquivos para o filesystem que defini para o database,
aplico as permissões necessárias, modifico o config do mysql e
reinicio o serviço.

O que acho muito estranho é que o Moodle e o Bacula estavam
funcionando perfeitamente. Moodle já com tema configurado e um
cursos disponível e o Bacula com backup full criado e testes de
recuperação que sempre efetuo. O problema apareceu em algum
momento após perfeito funcionamento das duas ferramentas
instaladas e testadas.

Apenas para confirmar, veja la nas evidencias que uso um ls
/dbase/mysql para mostrar a estrutura do mysql onde aparece os
bancos moodle e bacula e no arquivo de configuração do mysql
tenho a diretriz datadir = /dbase/mysql.
O Mysql inicia normalmente via systemctl start sem qualquer aviso
de erro log, com um arquivo de warning sobre usar o padrão de
senhas antigo. Consigo acessar normalmente o mysql (estranhamente
com root sem senha), o que não seria possível se  houvesse
divergência entre a localização do banco e a configuração no
arquivo.

Atenciosamente
Mauricio Neto



Em 23/04/2022 01:52, Gustavo Villela Goulart escreveu:

Opá Mauricio, boa noite!

Vc mexeu na conf do mysql?

Por default o path do datadir é: /var/lib/mysql
Seu datadir esta assim: /dbase/mysql

Se vc alterou essa configuração na mão, ou as aplicações que vc
esta usando fizeram essa alteração, é o que esta causando o
problema.
Para vc alterar o datadir do mysql, faça assim:
   - Pare o mysql
   - Copie todos os arquivos de /var/lib/mysql para o novo diretório
   - Altere o path  datadir        = /dbase/mysql
  - Inicie o mysql

Se vc não fez assim e só copiou os datafiles do bacula e da
outra aplicação, não vai funcionar. Se copiou com o banco
funcionando(mysql startado), provavelmente corrompeu os arquivos.

Espero ter ajudado.

Em sex., 22 de abr. de 2022 às 19:25, Mauricio Neto
 escreveu:

Amigo boa tarde.

Desculpe o off topic já que se trata de um problema de mysql
e não Debian mas como nesta comunidade temos conhecedores de
tudo relato uma situação muito estranha na esperança que
algum dos amigos já tenham visto algo parecido, ou posam
indicar um forum mais apropriado...

Instalei o mysql 8.0, Apache2, PHP7.4, o Moodle (EAD) e o
Bacula backup. tudo funcionando perfeitamente durante alguns
dias e sem que ocorresse qualquer evento estranho tenho o
seguinte cenário:

As aplicações não 

Re: file born 30 seconds after its creation on ext4 - bug?

[Vincent Lefevre]

On 2022-04-26 14:18:58 -0400, Stefan Monnier wrote:
> > On an ext4 filesystem, I got a file born 30 seconds after its
> > actual creation. Is this a bug?
> 
> I doubt it.
> Note that a file's atime/mtime/ctime is a property of the file itself,
> whereas "appearing" is defined by when the name you're checking
> becomes a link to it.
> 
> IOW, most likely the file was first created under a different name and
> then renamed.  This is very standard practice to make sure the final
> file name never refers to an incomplete file.

You mean renamed by the Linux kernel??? (The script doesn't rename it.)

FYI, the script is the following one:

  
https://gitlab.inria.fr/mpfr/misc/-/blob/fed7770cf5f712871bd116ef80d93ea5885fc3f7/vl-tests/mpfrtests.sh

and the file in question is what appears as "$out".

And what I did was running from a MPFR working tree

  /path/to/mpfrtests.sh < /path/to/mpfrtests.data

where the mpfrtests.data file is the following one:

  
https://gitlab.inria.fr/mpfr/misc/-/blob/e0204b3423b9bc25c31548d2acc5b8e19a73f48d/vl-tests/mpfrtests.data

Note that I had never had any issue until now. This was the first
time I got errors saying that the file was missing.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: file born 30 seconds after its creation on ext4 - bug?

[Vincent Lefevre]

On 2022-04-26 12:47:53 -0500, Nicholas Geovanis wrote:
> On Tue, Apr 26, 2022 at 12:37 PM Nicholas Geovanis 
> wrote:
> 
> > On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre 
> > wrote:
> >
> >> On an ext4 filesystem, I got a file born 30 seconds after its
> >> actual creation. Is this a bug?
> >>
> >
> > Only experimentation can really back me up on this, but consider the
> > following:
> >
> > Every time you use the "|" operator or the ";" separator on a command-line,
> > new processes are being spawned. Which wait to be dispatched on a core.
> > But you are not serializing the dispatch of those processes, and
> > especially with
> > 16 fast cores, you can't predict their order of execution.
> >
> 
> A couple more observations:
> (1) It looks like you're trying to observe behavior in the very same
> filesystem in which
> the running executable is loaded from and its log files are being
> written-to. That's
> alot of variables in motion at once.
> 
> (2) Yes, the "|" is in a sense serializing I/O in "lt|head". But the
> filesystem is syncing
> buffered and disk-based content separately from that.

There are no parallel writes to the file, i.e. everything is
serialized from this point of view.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: file born 30 seconds after its creation on ext4 - bug?

[Vincent Lefevre]

On 2022-04-26 19:01:26 +0200, Thomas Schmitt wrote:
> It looks as if the file indeed does not exist when you inquire it.
> So if it got created by the script, maybe it was deleted or renamed
> shortly afterwards and created again 30 seconds later ?

The script doesn't do that. The file is created with

  echo "* $fqdn ($(${1:-.}/config.guess) / ${line#PROC:})" > "$out"

and every other line that writes to the file use >> "$out".

Note that if the file were created again, the first line with the FQDN
would no longer be in the file, but the line is still there.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Do I need a new hard drive?

[David Christensen]

On 4/26/22 15:04, Charles Curley wrote:




On Mon, 25 Apr 2022 14:56:50 -0700 David Christensen wrote:



On 4/25/22 07:18, Charles Curley wrote:



On Sun, 24 Apr 2022 22:52:15 -0700 David Christensen wrote:



Rather than a Live Linux distribution for troubleshooting, I install
Debian onto a USB flash drive (SanDisk Ultra Fit USB 3.0 16 GB).   I
keep it updated/ upgraded, and install whatever tools I want.  You
might want to make one that matches your Debian instance -- that
should eliminate the device enumeration differences.


Would that have solved this transposition? 



I would expect two matching Debian instances would enumerate the same 
drives in the same order on the same machine, but...




I suspect that Linux sets up
the boot drive as sda regardless of how the firmware sees things.



I have seen examples to the contrary.


When installing, I make sure the target device is /dev/sda -- installing 
to /dev/sdb, etc., is a recipe for future problems.




But otherwise a good idea, if a bit of work.



A complete Debian instance on a USB flash drive is an invaluable tool, 
and well worth the time to create and maintain.




Those Alchemy SATA cables look good.  Assuming you like them, I would
replace the factory cables with new Alchemy cables.


I'll keep that in mind. I have one spare, so I can swap that in in
pretty quick order if need be.



I would order more and make everything match.



I did figure that out, and tested the three remaining drives. All
tested with no errors.



Good.



I've done some of these. But as I am not seeing any more hard drive
issues, I'm not going to spend any more time on the rest.



Agreed.



7.  Boot memtest86+ and run overnight or longer.


Interestingly enough, memtest86 locks up right at the 4096 MB mark. It
also completely refuses to run on another system I have here. I'm going
to do some further testing, then report what I see in a new thread.



If you are certain your memtest86+ tool is good, then that is a 
significant finding.  I would download a current copy, burn it to USB, 
and try again.




Did you figure out what was preventing Debian from booting?  Is the
Debian instance fixed?


> Update. I had a friend with a power supply checker check the power
> supply. The +12 volt line is running at 11.5v, barely within spec.
> Fishy, but livable for the nonce.
>
> I had been running Finnix as Debian wouldn't boot. I pulled all the
> external USB lines except for a 3.5" external floppy disk drive. The
> USB problem that started all this went away, i.e. I stopped getting
> error messages in dmesg. I rebooted Finnix, and did not see the error
> message. Also, the boot speed was back to normal.
>
> An hour and a half ago I booted to the installed Debian system, and
> that now runs fine. I see no error messages for USB or for any of the
> drives. RAID looks nominal. I will monitor.
>
> The next step will be to add back external USB lines, one at a time,
> and see if the problem re-appears. It may have been something as simple
> as mild corrosion on a connector.


What is the make and model of the PSU?


Have you done a power budget calculation?  I wonder if your PC is 
pushing the PSU to the limit, and the USB devices push it over?



A weak PSU could cause memory errors, which will cause strange 
malfunctions.  Beware of chasing misleading symptoms.  If you can afford 
a spare PSU, A/B testing could be revealing.



David

Re: email lacks sender address

[Byung-Hee HWANG]

> Both Gmail and yw-1204
> does not break about this matter (verify certificate).

Correction: Exactly, i did't see any problems. Because i have been using always
self-signed certficate with sSMTP.

Sorry for confusing statement. 

Sincerely, Linux fan Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

Re: email lacks sender address

[Byung-Hee HWANG]

Dear Celejar,

Celejar  writes:

> On Tue, 26 Apr 2022 09:42:38 +0900
> 황병희  wrote:
>
>> Dear Greg,
>> 
>> Greg Wooledge  writes:
>> 
>> > (... thanks ...)
>> > unicorn:~$ apt-cache show ssmtp
>> > [...]
>> > Description-en: extremely simple MTA to get mail off the system to
>> > a mail hub
>> >  A secure, effective and simple way of getting mail off a system to your
>> >  mail hub. It contains no suid-binaries or other dangerous things - no mail
>> >  spool to poke around in, and no daemons running in the background. Mail is
>> >  simply forwarded to the configured mailhost. Extremely easy configuration.
>> >
>> > The entire point of this package is that it's meant to be used on a
>> > "dumb client" which does not wish to have its own outgoing mail queue.
>> > Instead, it forwards all of your mail to your "smart host" -- the MTA
>> > that has been set up for your organization's dumb clients to use.
>> >
>> > So, the single piece of information you need in order to use ssmtp is
>> > the hostname of your smart host.  Also known as your mail relay.  Or many
>> > other names.  It's where you want your outgoing mail to be handled.
>> >
>> 
>> Thanks for your time and your life!
>> 
>> Really i love sSMTP so much!!!
>
> FWIW, there's an outstanding ten year old bug against sSMTP pointing
> out that it doesn't bother to validate server TLS certificates. You'll
> have to decide whether this bothers you or not:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662960

That seems some technical issue. However i have no skills to repair that
C level program.

Actually i have no trouble with current sSMTP. Both Gmail and yw-1204
does not break about this matter (verify certificate). So for a while
i'll keep this state. It means that i will continue to use the sSMTP.

Sorry and thanks ^^^

Sincerely, Linux fan Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

Re: Certificado gratis para openvpn.

[Luis]

Todo lo que intento es configurar un cliente openvpn, y sin resultados aún. Mi 
conexión no es por cable, con IP real, es más bien compartiendo la conexión de 
datos del móvil mediante zona wifi, de modo que la IP que adquiere debian es 
192.168.43.x, que se la asigna el móvil 樂Sent from my Metro By T-Mobile 4G LTE 
Android Device
 Mensaje original De: Gonzalo Rivero  
Fecha: 26/4/22  7:33 p. m.  (GMT-05:00) A: luiseded...@nauta.cu Asunto: Re: 
Certificado gratis para openvpn. 

El 26/4/22 a las 16:51,
  luiseded...@nauta.cu escribió:

Hola,
  
  
  Es posible obtener algun cerfificado
  
  confiable para usar en openvpn?
  
  

Si estás por hacer tu propia conexión,
también podés generar tus propios certificados. 
  
Como en el fondo no es mas que una
cuestión de confianza, si establecés algún canal seguro para
transmitirlos (por ejemplo, llevarlos vos mismo a la otra
computadora), no tendrías que tener mayores problemas. 
  
Fijate los scripts en el directorio el
paquete extra easyrsa que antes era parte de la distribución de
openvpn

  

  

  
--
Gonzalo Rivero
(-.(-.(-.(-.(-.-).-).-).-).-)
  

Re: Wifi randomly stops after upgrade

[Marcelo Laia]

I found this:

https://bugzilla.kernel.org/show_bug.cgi?id=215698

Linux marcelo 5.16.0-6-amd64 #1 SMP PREEMPT Debian 5.16.18-1 (2022-03-29) 
x86_64 GNU/Linux

Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
(rev 01)
Subsystem: Dell Vostro 3470
Kernel driver in use: ath9k
Kernel modules: ath9k


dmesg

marcelo@marcelo:~$ sudo dmesg | grep ath

!/run/initramfs/fsck-root).
[9.602943] ath: phy0: WB335 2-ANT card detected
[9.602946] ath: phy0: Set BT/WLAN RX diversity capability
[9.612354] ath: phy0: Enable LNA combining
[9.613597] ath: phy0: ASPM enabled: 0x43
[9.613603] ath: EEPROM regdomain: 0x6c
[9.613604] ath: EEPROM indicates we should expect a direct regpair map
[9.613606] ath: Country alpha2 being used: 00
[9.613607] ath: Regpair used: 0x6c
[9.759588] ath9k :02:00.0 wlp2s0: renamed from wlan0
[9.962826] usbcore: registered new interface driver ath3k

marcelo@marcelo:~$ sudo dmesg | grep wlp2s0
[9.759588] ath9k :02:00.0 wlp2s0: renamed from wlan0
[   19.285650] wlp2s0: authenticate with 00:25:9c:13:d6:14
[   19.298402] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[   19.335316] wlp2s0: authenticated
[   19.337990] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[   19.374043] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[   19.374212] wlp2s0: associated
[   19.634072] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[  580.077470] wlp2s0: authenticate with 00:25:9c:13:d6:14
[  580.094458] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[  580.124751] wlp2s0: authenticated
[  580.127153] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[  580.149024] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[  580.149231] wlp2s0: associated
[  592.067221] wlp2s0: authenticate with 00:25:9c:13:d6:14
[  592.081948] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[  592.104936] wlp2s0: authenticated
[  592.106728] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[  592.128658] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[  592.128864] wlp2s0: associated
[  784.061188] wlp2s0: authenticate with 00:25:9c:13:d6:14
[  784.077559] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[  784.106433] wlp2s0: authenticated
[  784.110604] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[  784.133119] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[  784.133326] wlp2s0: associated
[ 2800.52] wlp2s0: deauthenticating from 00:25:9c:13:d6:14 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[ 2801.389782] wlp2s0: authenticate with 00:25:9c:13:d6:14
[ 2801.402513] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[ 2801.404520] wlp2s0: authenticated
[ 2801.406012] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[ 2801.426863] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[ 2801.427022] wlp2s0: associated
[ 2801.482160] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 2848.017518] wlp2s0: authenticate with 00:25:9c:13:d6:14
[ 2848.034633] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[ 2848.065999] wlp2s0: authenticated
[ 2848.067428] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[ 2848.108099] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[ 2848.108308] wlp2s0: associated
[ 2874.239289] wlp2s0: authenticate with 00:25:9c:13:d6:14
[ 2874.255443] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[ 2874.284893] wlp2s0: authenticated
[ 2874.288233] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[ 2874.327703] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[ 2874.327911] wlp2s0: associated
[ 3154.276456] wlp2s0: authenticate with 00:25:9c:13:d6:14
[ 3154.293314] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[ 3154.326079] wlp2s0: authenticated
[ 3154.330182] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[ 3154.352066] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[ 3154.352293] wlp2s0: associated
[ 3251.184978] wlp2s0: authenticate with 00:25:9c:13:d6:14
[ 3251.202766] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[ 3251.231450] wlp2s0: authenticated
[ 3251.239496] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[ 3251.261319] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[ 3251.261527] wlp2s0: associated
[ 3523.186485] wlp2s0: authenticate with 00:25:9c:13:d6:14
[ 3523.200934] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[ 3523.231492] wlp2s0: authenticated
[ 3523.233619] wlp2s0: associate with 00:25:9c:13:d6:14 (try 1/3)
[ 3523.254548] wlp2s0: RX AssocResp from 00:25:9c:13:d6:14 (capab=0x431 
status=0 aid=4)
[ 3523.254755] wlp2s0: associated
[ 3947.043683] wlp2s0: authenticate with 00:25:9c:13:d6:14
[ 3947.061516] wlp2s0: send auth to 00:25:9c:13:d6:14 (try 1/3)
[ 3947.091387] wlp2s0: authenticated
[ 3947.094331] wlp2s0: associate with 

Re: Do I need a new hard drive?

[Charles Curley]

Update. I had a friend with a power supply checker check the power
supply. The +12 volt line is running at 11.5v, barely within spec.
Fishy, but livable for the nonce.

I had been running Finnix as Debian wouldn't boot. I pulled all the
external USB lines except for a 3.5" external floppy disk drive. The
USB problem that started all this went away, i.e. I stopped getting
error messages in dmesg. I rebooted Finnix, and did not see the error
message. Also, the boot speed was back to normal.

An hour and a half ago I booted to the installed Debian system, and
that now runs fine. I see no error messages for USB or for any of the
drives. RAID looks nominal. I will monitor.

The next step will be to add back external USB lines, one at a time,
and see if the problem re-appears. It may have been something as simple
as mild corrosion on a connector.

Meanwhile, I did long tests on the hard drives and SSD; all passed.
I've seen no hard drive error messages all day.

On Mon, 25 Apr 2022 14:56:50 -0700
David Christensen  wrote:

> On 4/25/22 07:18, Charles Curley wrote:
> > On Sun, 24 Apr 2022 22:52:15 -0700
> > David Christensen  wrote:
> >   
> >> So, RAID 5 HDD's are sda, sdc, and sdd, and optical is sdb?  
> > 
> > Optical is sr0.   
> 
> 
> Interesting.  (Must be the SATA controller expansion card?)

Yup.

> 
>  > Debian and finnix see things differently. On both. sdc and sdd are
>  > part of the RAID array. On Debian, sda is the system drive: /,
>  > /home, /etc, swap, /boot, etc.. sdb is part of the RAID array.
>  > Finnix swaps those two.  
> 
> 
> Okay.
> 
> 
> Rather than a Live Linux distribution for troubleshooting, I install 
> Debian onto a USB flash drive (SanDisk Ultra Fit USB 3.0 16 GB).   I 
> keep it updated/ upgraded, and install whatever tools I want.  You
> might want to make one that matches your Debian instance -- that
> should eliminate the device enumeration differences.

Would that have solved this transposition? I suspect that Linux sets up
the boot drive as sda regardless of how the firmware sees things.

But otherwise a good idea, if a bit of work.


> 
> 
>  >> SATA cables -- Color?  Locking or non-locking connectors?Came
>  >> with motherboard or aftermarket?  If the latter, make and model?  
>  >
>  > All black, two red. The black ones came with the computer. The red
>  > ones are aftermarket, Alchemy SATA3 30 cm. BFA-MSC-SATA330RK-RP.
>  > All lock.  
> 
> 
> https://www.frozencpu.com/products/14060/cab-572/Bitfenix_Alchemy_Multisleeve_SATA_30_Cable_-_30cm_-_Red_BFA-MSC-SATA330RK-RP.html
> 
> 
> Those Alchemy SATA cables look good.  Assuming you like them, I would 
> replace the factory cables with new Alchemy cables.

I'll keep that in mind. I have one spare, so I can swap that in in
pretty quick order if need be.


> 
> 
>  >> Please run long tests now on all three drives.  Save all of the
>  >> reports. Post the report(s) for any drive(s) with SMART failures
>  >> and/or dmesg(1) errors.  
>  >
>  > Long tests run about 10 hours. I did one overnight on sdd, and it
>  > reported no errors. No dmesg errors sine the ones I reported in the
>  > original email.  
> 
> 
> I launch SMART tests on all of the drives at the same time.  The 
> microcontroller in each drive runs the test for that drive 
> independently, so it is okay to run all the tests concurrently.

I did figure that out, and tested the three remaining drives. All
tested with no errors.



> 
> 
> I still don't see the source of the original dmesg(1) errors.  I
> would:

I've done some of these. But as I am not seeing any more hard drive
issues, I'm not going to spend any more time on the rest.


> 
> 7.  Boot memtest86+ and run overnight or longer.

Interestingly enough, memtest86 locks up right at the 4096 MB mark. It
also completely refuses to run on another system I have here. I'm going
to do some further testing, then report what I see in a new thread.


> 
> 
> If and when you have convinced yourself that all of the hardware is 
> good, then software is what remains.

Yup.

> 
> 
> Did you figure out what was preventing Debian from booting?  Is the 
> Debian instance fixed?

I think so; see above.

-- 
Does anybody read signatures any more?

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

Re: Certificado gratis para openvpn.

[Yoel Villarreal]

LetsEncrypt?

En 26 de abril de 2022 3:52:07 p. m. luiseded...@nauta.cu escribió:


Hola,

Es posible obtener algun cerfificado
confiable para usar en openvpn?

Saludos,

Luis Esteban.



Enviado con Aqua Mail para Android
https://www.mobisystems.com/aqua-mail

Re: email lacks sender address

[David Wright]

On Tue 26 Apr 2022 at 09:25:48 (-0400), Haines Brown wrote:
> On Tue, Apr 26, 2022 at 10:10:48AM +0100, Jonathan Dowland wrote:
> > On Mon, Apr 25, 2022 at 11:39:01AM -0400, Haines Brown wrote:
> > > I infer that exim is not being given the envelop address of the
> > > sender.
> > 
> > Quoting /etc/exim4/exim4.conf.template:
> > 
> > # By default, exim forces a Sender: header containing the local
> > # account name at the local host name in all locally submitted messages
> > # that don't have the local account name at the local host name in the
> > # From: header, deletes any Sender: header present in the submitted
> > # message and forces the envelope sender of all locally submitted
> > # messages to the local account name at the local host name.
> > # The following settings allow local users to specify their own envelope 
> > sender
> > # in a locally submitted message. Sender: headers existing in a locally
> > # submitted message are not removed, and no automatic Sender: headers
> > # are added. These settings are fine for most hosts.
> > # If you run exim on a classical multi-user systems where all users
> > # have local mailboxes that can be reached via SMTP from the Internet
> > # with the local FQDN as the domain part of the address, you might want
> > # to disable the following three lines for traceability reasons.
> > .ifndef MAIN_FORCE_SENDER
> > local_from_check = false
> > local_sender_retain = true
> > untrusted_set_sender = *
> > .endif
> > 
> >   Jonathan Dowland
> > ✎j...@debian.org
> >    https://jmtd.net
> 
> Johathan, many thanks for pointing out the content of exim 
> configuration template. The exim config files are so intimidating that 
> unless there is a reason to so so an amateur like myself tries to 
> avoid them.

I would be very surprised if you had /any/ need to configure exim4
beyond what is offered by Debian's  dpkg-reconfigure exim4-config
script (which writes /etc/exim4/update-exim4.conf.conf for you)
and adding a line of credentials to /etc/exim4/passwd.client so
that you can authenticate your system to your smarthost.

> What I get out of this is that my MUA (mutt) might generate a message 
> that lacks a local account name (I assume it is defined by the content 
> of /etc/mailname, whicn in my case happens to be lenin.histomat.net). 
> I infer this is the value that appaars in the Sender: line of the 
> message header consructed by mutt. 
> 
> The above text describes what exim does if that Sender: line in the 
> header happens to be empt or missing. If I understand correctly, exim 
> deletes the empty Sender: line and instead uses the value of 
> /etc/mailname to be the envelop sender. Is this so?

Do you know why mutt is adding a Sender: line to your emails?
Did you ask it to, or have you been asked to by someone else?

But don't confuse the specific "Sender:" field in the header with the
conversational use of "sender" to talk about the person/software/system
that's sending the email. (The emails you send here do not contain
a Sender: field.)

A typical, straightforward, email contains a From: field, which is the
email address of the sender (not Sender), as opposed to the recipient
(ie the To: field). Again, typically, straightforwardly, the From:
and To: fields will be used to generate the envelope's MAIL FROM
and RCPT TO addresses.

> The text goes on to say that if the three lines it specifies at the 
> end are present, it allows the user to specify whatever he/she 
> likes to appear as the envelop's sender.
> 
> This raises questions. 
> 
> First, the implication seems to be that an empty Sender: line means 
> that mutt is falling down on the job and for some reason this past 
> week ceasad to provide a value for the Sender: line in the header of 
> the some mail it sent to exim. So is the obvious thing to do is fix 
> mutt? Since I've been using the same mutt configuration for years, its 
> not a configuration problem but samage to mutt. Looks like a reinstall 
> and slow reconstruction of its confirturation. 

You have to tell mutt what to use. It can't assume that your $LOGNAME
and /etc/mailname are, taken together, going to generate a satisfactory
From: field for an email.

It sounds as if you're making too many assumptions about what mutt
can determine about you, like what your sending and receiving email
addresses are. (Like in your next line: without any configuration)

> I already ran mutt without any configuration and it didn't seem to 
> help.  I sumitted by domain name to an online mail tesing site and get 
> "Unverified address: postoffice.omnis.com said: 521 5.5.1 Protocol 
> error." Omnis told me the problem was the Sender: line was empty in 
> some messages.  

This is why I'm struggling to understand your situation. It's not like
mutt to randomly choose whether to bother to add fileds to the header.
What did Omnis actually say, literally?

In your OP, you wrote "554 5.7.1 Empty Sender Address
  is prohibited through this server; from=<>"

I 

Certificado gratis para openvpn.

[luisededios]

Hola,

Es posible obtener algun cerfificado
confiable para usar en openvpn?

Saludos,

Luis Esteban.

No puedo imprimir en impresora en red

[Marcelo Eduardo Giordano]

Amigos:

Acabo de instalar debian en mi nueva notebook e instalo mis dos 
impresoras y en ambas no puedo imprimir


una impresora es una impresora XEROX B215 que se conecta directamente a 
la red y que me el sistema me la detectó automaticamente. Sin embargo al 
imprimir me dice "No suitable destinacion host found by cups browsed"


Tampoco puedo imprimir en una Epson L3110 que esta conectada en red en 
otra pc con debian y me dice "la configuracion de la impresora es 
incorrecta o la impresora ya no existe"


Ambas impresoras puedo imprimir perfectamente desde otra pc con Arch

Muchas gracias

Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Andrew M.A. Cater]

On Tue, Apr 26, 2022 at 01:31:02PM +, Schwibinger Michael wrote:
> 
> Good afternoon.
> Thank You
> 
> We dont use WIFI.
> 
> Desktops
> 
> We do
> connect with cable to the WWW.
> Also mouse and keyboard is with cable.
> 

OK: in many ways that makes it easier. I would still suggest the firmware
disk - if only because that also may include manufacturer's security fixes
for the code that runs deep within the main processor in your machine, for
example.

As Greg says, you can find exactly which firmware you need by runnng the 
command he gave.

If you are happy to rebuild the computer you have with new software -
wiping out the previous attempts to upgrade Debian in place - then:

* Prepare a USB stick / CD with the .iso file.

* Go into the menu which supports boot from different media
[This is sometimes accessed by holding down F1 or F2 or F12 or the Delete key]

* Boot from the install medium and follow the prompts. If you have another
computer available, I would suggest that you also have the release notes
for Bullseye open at the same time -
 https://www.debian.org/releases/stable/amd64/release-notes/

I would suggest the graphical mode install, perhaps.

You said in one of the earliest messages that you have previously been
using Debian LXDE desktop. The first choice for Debian desktop is GNOME
which may use more memory / more resources.

If you wish to use LXDE as your install, when it gets to the screen for
selecting software - deselect GNOME and select LXDE instead. The selections
can be changed by selecting them then hitting the spacebar, I think

Hope this helps.

> Regards
> Sophie
> 
> 
All the best, as ever,
 
 Andy Cater
> 

Re: file born 30 seconds after its creation on ext4 - bug?

[Nicholas Geovanis]

On Tue, Apr 26, 2022 at 12:37 PM Nicholas Geovanis 
wrote:

> On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre 
> wrote:
>
>> On an ext4 filesystem, I got a file born 30 seconds after its
>> actual creation. Is this a bug?
>>
>
> Only experimentation can really back me up on this, but consider the
> following:
>
> Every time you use the "|" operator or the ";" separator on a command-line,
> new processes are being spawned. Which wait to be dispatched on a core.
> But you are not serializing the dispatch of those processes, and
> especially with
> 16 fast cores, you can't predict their order of execution.
>

A couple more observations:
(1) It looks like you're trying to observe behavior in the very same
filesystem in which
the running executable is loaded from and its log files are being
written-to. That's
alot of variables in motion at once.

(2) Yes, the "|" is in a sense serializing I/O in "lt|head". But the
filesystem is syncing
buffered and disk-based content separately from that.


> I know that such issues can be observed with NFS, but here this
>> is just a local ext4 filesystem.
>>
>> Here are the details.
>>
>> I started a shell script:
>>
>> cventin:~> ps -p 667828 -o lstart,cmd
>>  STARTED CMD
>> Tue Apr 26 14:43:15 2022 /bin/sh /home/vlefevre/wd/mpfr/tests/mpfrtests.sh
>>
>> This script creates a file mpfrtests.cventin.lip.ens-lyon.fr.out
>> very early. But the first attempts to look at this file failed:
>>
>> cventin:~/software/mpfr> tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
>> zsh: no match
>> zsh: no match
>> cventin:~/software/mpfr[1]> tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
>> zsh: no match
>> zsh: no match
>> cventin:~/software/mpfr[1]> lt|head
>>  <14:43:42
>> total 7016
>> -rw-r--r--  1  188644 2022-04-26 14:43:42 config.log
>> -rw-r--r--  12861 2022-04-26 14:43:42 conftest.c
>> -rw-r--r--  1   0 2022-04-26 14:43:42 conftest.err
>> -rw-r--r--  11907 2022-04-26 14:43:42 confdefs.h
>> -rwxr-xr-x  1  632161 2022-04-26 14:43:16 configure.lineno*
>> drwxr-xr-x  24096 2022-04-26 14:43:11 doc/
>> drwxr-xr-x  34096 2022-04-26 14:43:11 tune/
>> -rwxr-xr-x  1   23568 2022-04-26 14:43:11 depcomp*
>> drwxr-xr-x  5   36864 2022-04-26 14:43:11 tests/
>> cventin:~/software/mpfr> lt|head
>> <14:43:47
>> total 6416
>> -rw-r--r--  1   19436 2022-04-26 14:43:47 config.log
>> -rw-r--r--  1 561 2022-04-26 14:43:47 conftest.c
>> -rw-r--r--  1   0 2022-04-26 14:43:47 conftest.err
>> -rw-r--r--  14138 2022-04-26 14:43:47 mpfrtests.cfgout
>> -rw-r--r--  1 500 2022-04-26 14:43:47 confdefs.h
>> -rwxr-xr-x  1  632161 2022-04-26 14:43:45 configure.lineno*
>> -rw-r--r--  1 878 2022-04-26 14:43:45
>> mpfrtests.cventin.lip.ens-lyon.fr.out
>> drwxr-xr-x  34096 2022-04-26 14:43:44 tune/
>> drwxr-xr-x  4   36864 2022-04-26 14:43:44 tests/
>>
>> According to /usr/bin/stat, the file birth is
>>
>>  Birth: 2022-04-26 14:43:45.537241731 +0200
>>
>> thus 30 seconds after the script started!
>>
>> Note that the configure.lineno file is created *after*
>> mpfrtests.cventin.lip.ens-lyon.fr.out, and one can see that
>> at 14:43:16, configure.lineno was already created.
>>
>> This is a 12-core Debian/unstable machine with
>>
>> Linux cventin 5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18)
>> x86_64 GNU/Linux
>>
>> --
>> Vincent Lefèvre  - Web: 
>> 100% accessible validated (X)HTML - Blog: 
>> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
>>
>>

Re: file born 30 seconds after its creation on ext4 - bug?

[Nicholas Geovanis]

On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre  wrote:

> On an ext4 filesystem, I got a file born 30 seconds after its
> actual creation. Is this a bug?
>

Only experimentation can really back me up on this, but consider the
following:

Every time you use the "|" operator or the ";" separator on a command-line,
new processes are being spawned. Which wait to be dispatched on a core.
But you are not serializing the dispatch of those processes, and especially
with
16 fast cores, you can't predict their order of execution.


> I know that such issues can be observed with NFS, but here this
> is just a local ext4 filesystem.
>
> Here are the details.
>
> I started a shell script:
>
> cventin:~> ps -p 667828 -o lstart,cmd
>  STARTED CMD
> Tue Apr 26 14:43:15 2022 /bin/sh /home/vlefevre/wd/mpfr/tests/mpfrtests.sh
>
> This script creates a file mpfrtests.cventin.lip.ens-lyon.fr.out
> very early. But the first attempts to look at this file failed:
>
> cventin:~/software/mpfr> tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
> zsh: no match
> zsh: no match
> cventin:~/software/mpfr[1]> tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
> zsh: no match
> zsh: no match
> cventin:~/software/mpfr[1]> lt|head
>  <14:43:42
> total 7016
> -rw-r--r--  1  188644 2022-04-26 14:43:42 config.log
> -rw-r--r--  12861 2022-04-26 14:43:42 conftest.c
> -rw-r--r--  1   0 2022-04-26 14:43:42 conftest.err
> -rw-r--r--  11907 2022-04-26 14:43:42 confdefs.h
> -rwxr-xr-x  1  632161 2022-04-26 14:43:16 configure.lineno*
> drwxr-xr-x  24096 2022-04-26 14:43:11 doc/
> drwxr-xr-x  34096 2022-04-26 14:43:11 tune/
> -rwxr-xr-x  1   23568 2022-04-26 14:43:11 depcomp*
> drwxr-xr-x  5   36864 2022-04-26 14:43:11 tests/
> cventin:~/software/mpfr> lt|head
> <14:43:47
> total 6416
> -rw-r--r--  1   19436 2022-04-26 14:43:47 config.log
> -rw-r--r--  1 561 2022-04-26 14:43:47 conftest.c
> -rw-r--r--  1   0 2022-04-26 14:43:47 conftest.err
> -rw-r--r--  14138 2022-04-26 14:43:47 mpfrtests.cfgout
> -rw-r--r--  1 500 2022-04-26 14:43:47 confdefs.h
> -rwxr-xr-x  1  632161 2022-04-26 14:43:45 configure.lineno*
> -rw-r--r--  1 878 2022-04-26 14:43:45
> mpfrtests.cventin.lip.ens-lyon.fr.out
> drwxr-xr-x  34096 2022-04-26 14:43:44 tune/
> drwxr-xr-x  4   36864 2022-04-26 14:43:44 tests/
>
> According to /usr/bin/stat, the file birth is
>
>  Birth: 2022-04-26 14:43:45.537241731 +0200
>
> thus 30 seconds after the script started!
>
> Note that the configure.lineno file is created *after*
> mpfrtests.cventin.lip.ens-lyon.fr.out, and one can see that
> at 14:43:16, configure.lineno was already created.
>
> This is a 12-core Debian/unstable machine with
>
> Linux cventin 5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18)
> x86_64 GNU/Linux
>
> --
> Vincent Lefèvre  - Web: 
> 100% accessible validated (X)HTML - Blog: 
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
>
>

Re: file born 30 seconds after its creation on ext4 - bug?

[Thomas Schmitt]

Hi,

Vincent Lefevre wrote:
> This script creates a file mpfrtests.cventin.lip.ens-lyon.fr.out
> very early. But the first attempts to look at this file failed:

It looks as if the file indeed does not exist when you inquire it.
So if it got created by the script, maybe it was deleted or renamed
shortly afterwards and created again 30 seconds later ?

Consider to inquire the file in the script for birth time and inode number
immediately after it was created. Compare these properties with the
properties of the file which you see 30 seconds later.


Have a nice day :)

Thomas

Re: email lacks sender address

[Celejar]

On Tue, 26 Apr 2022 09:42:38 +0900
황병희  wrote:

> Dear Greg,
> 
> Greg Wooledge  writes:
> 
> > (... thanks ...)
> > unicorn:~$ apt-cache show ssmtp
> > [...]
> > Description-en: extremely simple MTA to get mail off the system to a mail 
> > hub
> >  A secure, effective and simple way of getting mail off a system to your
> >  mail hub. It contains no suid-binaries or other dangerous things - no mail
> >  spool to poke around in, and no daemons running in the background. Mail is
> >  simply forwarded to the configured mailhost. Extremely easy configuration.
> >
> > The entire point of this package is that it's meant to be used on a
> > "dumb client" which does not wish to have its own outgoing mail queue.
> > Instead, it forwards all of your mail to your "smart host" -- the MTA
> > that has been set up for your organization's dumb clients to use.
> >
> > So, the single piece of information you need in order to use ssmtp is
> > the hostname of your smart host.  Also known as your mail relay.  Or many
> > other names.  It's where you want your outgoing mail to be handled.
> >
> 
> Thanks for your time and your life!
> 
> Really i love sSMTP so much!!!

FWIW, there's an outstanding ten year old bug against sSMTP pointing
out that it doesn't bother to validate server TLS certificates. You'll
have to decide whether this bothers you or not:

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

-- 
Celejar

Re: exim4 and oAuth

[Celejar]

On Mon, 25 Apr 2022 19:41:29 + (UTC)
mike.junk...@att.net wrote:

> I recently switch ISPs to Frontier.com and find that my emails aren't
> going out due to Frontier's insistence on using oAuth which as far as
> I can tell is beyond Exim4's capabilities.
> Feel free to contradict me if you know otherwise.
> I've seen one note suggesting that Mutt can do oAuth but find
> nothing in the docs confirming this nor how to make it so.
> Any pointers would be appreciated.

I haven't tried this myself, but one potential approach is to use
email-oauth2-proxy, which allows non-OAuth-aware applications to talk
to services that require OAuth:

https://github.com/simonrob/email-oauth2-proxy

-- 
Celejar

Re: email lacks sender address

[Curt]

On 2022-04-26, Vincent Lefevre  wrote:
> On 2022-04-24 23:30:34 -0400, Haines Brown wrote:
>> I placed these two lines in ~./muttrc/muttrc
>> 
>>   set envelope_from_address=hai...@histomat.net
>>   set use_envelope_from=hai...@histomat.net
>> 
>> but still get 521 5.5.1 Protocol error om outgoing messages.
>
> Note that use_envelope_from is a boolean. If you do not get
> an error message from Mutt ("Usage: set variable=yes|no"),
> this means that this muttrc file hasn't been read.
>


Actually, we already pointed this out earlier, and I believe David W.
wondered why no error message was being generated by mutt given this
configuration error (which could be nicely explained by the config file
simply not being read).

But sadly the OP never followed up on these points.

Re: Fixed Mate desktop spamming xorg logs - now video jagged

[Johann Klammer]

On 04/22/2022 01:50 AM, Jeremy Ardley wrote:
> I'm using Mate 1.20. I noticed a continual flood in my /var/log/Xorg.0.log
> 
> modeset(0): Failed to get GBM bo for flip to new front.
> 
> I tracked down the error at
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1645553
> 
> I used more or less the procedure documented by pkoz 2018-12-28 08:17:40 UTC 
> and the spamming stopped.
> 
> MATE menu>System>Preferences>Look and Feel>Windows>General tab>Enable 
> software compositing window manager checkbox.
> 
> However, some artefacts developed such as black borders on menu panels. Not 
> so much a problem.
> 
> The big problem now is video playing has obvious tearing of the image.
> 
> My video card is
> 
> 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
> Caicos PRO [Radeon HD 7450]
> 
> and my system
> 
> PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
> NAME="Debian GNU/Linux"
> VERSION_ID="11"
> 
> Any suggestions on how to get clean video again?
> 
look in your xorg.conf to see what module gets loaded.
then read the manpage and randomly disable/enable settings 
until something works.

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-24 23:30:34 -0400, Haines Brown wrote:
> I placed these two lines in ~./muttrc/muttrc
> 
>   set envelope_from_address=hai...@histomat.net
>   set use_envelope_from=hai...@histomat.net
> 
> but still get 521 5.5.1 Protocol error om outgoing messages.

Note that use_envelope_from is a boolean. If you do not get
an error message from Mutt ("Usage: set variable=yes|no"),
this means that this muttrc file hasn't been read.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: email lacks sender address

[Vincent Lefevre]

On 2022-04-26 09:25:48 -0400, Haines Brown wrote:
> What I get out of this is that my MUA (mutt) might generate a message 
> that lacks a local account name (I assume it is defined by the content 
> of /etc/mailname, whicn in my case happens to be lenin.histomat.net). 

No, /etc/mailname is just the FQDN (or something simpler in
some cases).

You should just use

  set use_envelope_from

in your muttrc, and provide a valid "From:" header.

(I use "set envelope_from", but envelope_from is actually the old name
for use_envelope_from.)

And make sure that $sendmail is equivalent to
"/usr/sbin/sendmail -oem -oi".

> Another question. The implication is that if the three lines are 
> present in the exim configuration it whould allow the user to specify 
> the envelop sender.

FYI, I haven't touched these 3 lines.

> Is this merley a statement of fact or is the template file used to
> construct the exim configuration?

Yes, it is used to generate the configuration file, which is
"/var/lib/exim4/config.autogenerated".

> In exim configuration I hide outgoing local mail name and provide
> the domain name without prepending host name. I assume
> this is irrevant and is merley a cosmetic isaue. Is that so?

Probably. But if you provide the correct addresses with Mutt,
this shouldn't matter.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Celejar]

On Tue, 26 Apr 2022 09:32:23 -0400
Greg Wooledge  wrote:

...

> Firmware is executable code that runs inside of a device (such as a
> network interface) rather than in your CPU.
> 
> Many modern devices require some non-free firmware in order to perform
> their duties correctly.  This is *especially* the case with wireless
> network interfaces, but also applies to video chipsets and other things.
> 
> If your devices are old enough, you may not need any.  If your devices
> are newer, you probably need some.

Just FTR, some rather old wired ethernet adaptors, such as the Broadcom
NetXtreme II (BCM5716) in my Dell R210 II, also require non-free
firmware to function:

https://packages.debian.org/buster/firmware-bnx2

-- 
Celejar

Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Greg Wooledge]

On Tue, Apr 26, 2022 at 01:41:07PM +, Schwibinger Michael wrote:
> What does mean
> 
> firmware is free
> firmware is not free?

Firmware can be free OR non-free.

Firmware for wireless interfaces is ALMOST ALWAYS non-free, because of
proprietary secrets that the wireless chip manufacturer is forced to
keep.  The government does not want end users to be able to violate the
frequency restrictions, so they force the manufacturers to keep the
technical details hidden from the users.

Firmware for video chipsets is typically non-free because of trade secrets
that the manufacturers are trying to keep hidden from their competition.

For the love of glob, just FIND OUT WHETHER YOU ARE MISSING ANY FIRMWARE
by running this command:

sudo dmesg | grep -i firmware

If you are missing some, then GO GET IT!

SHEESH.

Re: Recommendations for a home server running Debian Bullseye (11)?

[Christian Britz]

On 2022-04-26 15:28 UTC+0200, Stefan Monnier wrote:

> As a Debian user who considers current computer hardware should have a life
> expectancy of at least 10 years, my main question w.r.t to those beasts
> is what part of the hardware is supported by the vanilla Linux kernel
> (since that's generally the best guarantee around of long term support).
> 
> IIUC RK3339 is fairly well supported (thanks in large part to some
> Chromebooks, IIRC), right?  What about the wifi/BT?

I can only talk about the Raspi 4B, which is well supported by the
kernel in Debian stable, I don't use Wifi/BT, but they are supposed to
work. See also https://wiki.debian.org/RaspberryPi4. Hardware
accelerated 3D seems to be missing, I personally don't need it on my
headless home server, it has never been attached to a display. There is
a friendly community in #debian-raspberrypi on IRC. AFAIK there is work
ongoing to support 3D acceleration. As a starting point for
installation, I can recommend the images provided at
http://raspi.debian.net.

Christian

-- 
http://www.cb-fraggle.de

AW: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Schwibinger Michael]

Good afternoon.
Thank You

We dont use WIFI.

Desktops

We do
connect with cable to the WWW.
Also mouse and keyboard is with cable.

Regards
Sophie



Von: Andrew M.A. Cater 
Gesendet: Montag, 25. April 2022 18:26
An: debian-user@lists.debian.org 
Betreff: Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE 
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

On Mon, Apr 25, 2022 at 07:18:48PM +0100, Brian wrote:
> On Mon 25 Apr 2022 at 17:24:29 +, Andrew M.A. Cater wrote:
>
> > On Mon, Apr 25, 2022 at 06:15:40PM +0100, Brian wrote:
> > > On Mon 25 Apr 2022 at 16:59:57 +, Andrew M.A. Cater wrote:
> > >
> > > > Hello Sophie,
> > > > >
> > > > >
> > > > > > 
> > > > > >
> > > > > >
> > > > > > Good afternoon.
> > > > > >
> > > > > > Thank You.
> > > > > >
> > > > > > We do backup every evening.
> > > > > >
> > > > > > What version of Debian from Debian URL is the best do download and 
> > > > > > burn on
> > > > > > CD?
> > > > > >
> > > >
> > > > We still don't know what the actual computer you use is :(
> > > >
> > > > Unless it is a (very old) 32 bit only machine, I would recommend
> > > >
> > > > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.3.0+nonfree/amd64/iso-cd/firmware-11.3.0-amd64-netinst.iso
> > > >
> > > > This is unofficial only because it contains non-free firmware. The 
> > > > firmware
> > > > may be necessary for your machine to boot and work well: it will almost
> > > > certainly be required if you are installing over a WiFi connection.
> > >
> > > I am aware that this ISO has non-free packages for a wireless
> > > connection and that any needed will be used and installed by
> > > d-i. However, what about micorode packages, firmware-intel-sound,
> > > bluez-firmwarem and dahdi-firmware? At which stage(s) of an
> > > installation does d-i become aware of them?
> > >
> >
> > Some of these are recognised at inital boot: if unsure, they can be
> > added. For myself, I normally install the metapackages 
> > firmware-linux-nonfree
> > and firmware-misc-nonfree which solve the problem. As the discussion 
> > elsewhere
> > on Debian mailing lists is showing, it is really very difficult indeed to
> > do without all firmware.
>
> The need for a non-free WiFi firmware is recognised and the user is
> given the choice to install it or not. I have never come across d-i
> offering to install other non-free packages, which is what one would
> expect. Are you sure they are even considered?
>

I'm fairly sure that microcode may get installed. As I say, I get round
the problem by installing the two metapackages which pull in everything
needed.

> The "discussion elsewhere" seems to be specifically about firmware
> and looks to be going somewhere. About time!
>
>

As someone who also works with the images team: I have the highest regard
for the opinions of Steve McIntyre and Andy Simpkins with whom I work
whenever we do release testing.

All the best, as ever,

Andy Cater

AW: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Schwibinger Michael]

Good afternoon
Thank You.

We did the check.

64 is possible.

Its a single desktop
without connectiions to other PCs.

Regards
Sophie



Von: Hans 
Gesendet: Montag, 25. April 2022 11:18
An: debian-user@lists.debian.org 
Betreff: Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE 
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

Am Montag, 25. April 2022, 12:58:48 CEST schrieb Schwibinger Michael:
Best version, if you do not want to have administration work, would be
Debian-11 (which is bullseye). You should choose "stable", which is well
tested and does not have much changes in the future.

Of course you will chose the correct version for your hardware. I suppose (if
the computer is not too old), will be amd64, which is 64-Bit. Make sure, you
get the correct one.

Good luck!

Best

Hans



> 
>
>
> Good afternoon.
>
> Thank You.
>
> We do backup every evening.
>
> What version of Debian from Debian URL is the best do download and burn on
> CD?
>
> We want to repair Debian
> for learning-studying Linux.
>
> Thank You
>
> Sophie
>
>
>

file born 30 seconds after its creation on ext4 - bug?

[Vincent Lefevre]

On an ext4 filesystem, I got a file born 30 seconds after its
actual creation. Is this a bug?

I know that such issues can be observed with NFS, but here this
is just a local ext4 filesystem.

Here are the details.

I started a shell script:

cventin:~> ps -p 667828 -o lstart,cmd
 STARTED CMD
Tue Apr 26 14:43:15 2022 /bin/sh /home/vlefevre/wd/mpfr/tests/mpfrtests.sh

This script creates a file mpfrtests.cventin.lip.ens-lyon.fr.out
very early. But the first attempts to look at this file failed:

cventin:~/software/mpfr> tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
zsh: no match
zsh: no match
cventin:~/software/mpfr[1]> tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
zsh: no match
zsh: no match
cventin:~/software/mpfr[1]> lt|head   <14:43:42
total 7016
-rw-r--r--  1  188644 2022-04-26 14:43:42 config.log
-rw-r--r--  12861 2022-04-26 14:43:42 conftest.c
-rw-r--r--  1   0 2022-04-26 14:43:42 conftest.err
-rw-r--r--  11907 2022-04-26 14:43:42 confdefs.h
-rwxr-xr-x  1  632161 2022-04-26 14:43:16 configure.lineno*
drwxr-xr-x  24096 2022-04-26 14:43:11 doc/
drwxr-xr-x  34096 2022-04-26 14:43:11 tune/
-rwxr-xr-x  1   23568 2022-04-26 14:43:11 depcomp*
drwxr-xr-x  5   36864 2022-04-26 14:43:11 tests/
cventin:~/software/mpfr> lt|head  <14:43:47
total 6416
-rw-r--r--  1   19436 2022-04-26 14:43:47 config.log
-rw-r--r--  1 561 2022-04-26 14:43:47 conftest.c
-rw-r--r--  1   0 2022-04-26 14:43:47 conftest.err
-rw-r--r--  14138 2022-04-26 14:43:47 mpfrtests.cfgout
-rw-r--r--  1 500 2022-04-26 14:43:47 confdefs.h
-rwxr-xr-x  1  632161 2022-04-26 14:43:45 configure.lineno*
-rw-r--r--  1 878 2022-04-26 14:43:45 mpfrtests.cventin.lip.ens-lyon.fr.out
drwxr-xr-x  34096 2022-04-26 14:43:44 tune/
drwxr-xr-x  4   36864 2022-04-26 14:43:44 tests/

According to /usr/bin/stat, the file birth is

 Birth: 2022-04-26 14:43:45.537241731 +0200

thus 30 seconds after the script started!

Note that the configure.lineno file is created *after*
mpfrtests.cventin.lip.ens-lyon.fr.out, and one can see that
at 14:43:16, configure.lineno was already created.

This is a 12-core Debian/unstable machine with

Linux cventin 5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) x86_64 
GNU/Linux

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

AW: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Schwibinger Michael]

Good afternoon

Thank You.

What does mean

firmware is free
firmware is not free?


Regards
Sophie



Von: Greg Wooledge 
Gesendet: Dienstag, 26. April 2022 13:32
An: debian-user@lists.debian.org 
Betreff: Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE 
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

On Tue, Apr 26, 2022 at 01:27:39PM +, Schwibinger Michael wrote:
> What is firmware?
> Do I need it?
> Is it dangerous?

Firmware is executable code that runs inside of a device (such as a
network interface) rather than in your CPU.

Many modern devices require some non-free firmware in order to perform
their duties correctly.  This is *especially* the case with wireless
network interfaces, but also applies to video chipsets and other things.

If your devices are old enough, you may not need any.  If your devices
are newer, you probably need some.

You can check by using

  sudo dmesg | grep -i firmware

(or any equivalent way of running dmesg as root).

As for whether it's dangerous... it's kind of a pointless question.  Either
you trust the manufacturer of the device, who is also the author of the
firmware, or you do not.

Re: [HS] Recherche spécialiste PHP-7

[ajh.valmer]

On Tuesday 26 April 2022 14:30:14 Daniel Caillibaud wrote:
> Le 25/04/22 à 12:00, ajh.val...@bbox.fr a écrit :
> > Je recherche un bon spécialiste PHP-7.2.

> Euh, je crois que tu peux passer directement à php8.1, 7.2 était maintenue 
> jusqu'à fin 2020,
> 7.3 est déjà en EOL et 7.4 meurt dans 6 mois.
> Avec 8.1 tu peux tenir jusque fin 2024 : 
> https://www.php.net/supported-versions.php
> Sur https://www.php.net/eol.php tu as les liens vers les guides de migration 
> (5.6 > 7.0 > 7.1 >
> 7.2 > 7.4 > 8.0 > 8.1), avec à chaque fois la liste de ce qui change.

Les différences importantes se situent au passage de php5 vers php7.
Après, les différences de php7 vers php8 sont minimes.
Je l'ai vu entre les versions php5.1 à php5.6.

https://www.php.net/eol.php guides migration 5.6 vers 7.0.
ne donnent pas les modifications essentielles, 
telles, la nouvelle syntaxe d'appel à une base de données
et les nouveaux scripts php7 à englober dans le SQL.

AW: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Schwibinger Michael]

Good afternoon

Thank You

64 bit is possible.

What do we do

BURN DVDs with pics
GIMP
LEAFPAD

Claws
Firefox

Single Desktop.

Regards
Sophie

Von: Andrew M.A. Cater 
Gesendet: Montag, 25. April 2022 16:59
An: debian-user@lists.debian.org 
Betreff: Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE 
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

Hello Sophie,
>
>
> > 
> >
> >
> > Good afternoon.
> >
> > Thank You.
> >
> > We do backup every evening.
> >
> > What version of Debian from Debian URL is the best do download and burn on
> > CD?
> >

We still don't know what the actual computer you use is :(

Unless it is a (very old) 32 bit only machine, I would recommend

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.3.0+nonfree/amd64/iso-cd/firmware-11.3.0-amd64-netinst.iso

This is unofficial only because it contains non-free firmware. The firmware
may be necessary for your machine to boot and work well: it will almost
certainly be required if you are installing over a WiFi connection.

The disk listed above is a network install disk: it is small to download
but uses network bandwidth to pull down the rest of the Debian packages
required.

If you can _only_ boot from CD, then you need a program capable of
burning a .iso to a disk.

If you have a machine running Windows, you can use a program called
Rufus very effectively to write the .iso image to a USB stick.
See also: https://wiki.debian.org/DebianInstall

See also the installation guide at 
https://www.debian.org/releases/stable/amd64/index.en.html.

I hope this helps. With every good wish, as ever,

Andy Cater.


> > We want to repair Debian
> > for learning-studying Linux.
> >
> > Thank You
> >
> > Sophie
> >
> >
> >
>

Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Greg Wooledge]

On Tue, Apr 26, 2022 at 01:27:39PM +, Schwibinger Michael wrote:
> What is firmware?
> Do I need it?
> Is it dangerous?

Firmware is executable code that runs inside of a device (such as a
network interface) rather than in your CPU.

Many modern devices require some non-free firmware in order to perform
their duties correctly.  This is *especially* the case with wireless
network interfaces, but also applies to video chipsets and other things.

If your devices are old enough, you may not need any.  If your devices
are newer, you probably need some.

You can check by using

  sudo dmesg | grep -i firmware

(or any equivalent way of running dmesg as root).

As for whether it's dangerous... it's kind of a pointless question.  Either
you trust the manufacturer of the device, who is also the author of the
firmware, or you do not.

AW: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

[Schwibinger Michael]

Good afternoon
Thank You.

What is firmware?
Do I need it?
Is it dangerous?

Regards
Sophie



Von: Andrew M.A. Cater 
Gesendet: Montag, 25. April 2022 17:24
An: debian-user@lists.debian.org 
Betreff: Re: AW: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE 
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry

On Mon, Apr 25, 2022 at 06:15:40PM +0100, Brian wrote:
> On Mon 25 Apr 2022 at 16:59:57 +, Andrew M.A. Cater wrote:
>
> > Hello Sophie,
> > >
> > >
> > > > 
> > > >
> > > >
> > > > Good afternoon.
> > > >
> > > > Thank You.
> > > >
> > > > We do backup every evening.
> > > >
> > > > What version of Debian from Debian URL is the best do download and burn 
> > > > on
> > > > CD?
> > > >
> >
> > We still don't know what the actual computer you use is :(
> >
> > Unless it is a (very old) 32 bit only machine, I would recommend
> >
> > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.3.0+nonfree/amd64/iso-cd/firmware-11.3.0-amd64-netinst.iso
> >
> > This is unofficial only because it contains non-free firmware. The firmware
> > may be necessary for your machine to boot and work well: it will almost
> > certainly be required if you are installing over a WiFi connection.
>
> I am aware that this ISO has non-free packages for a wireless
> connection and that any needed will be used and installed by
> d-i. However, what about micorode packages, firmware-intel-sound,
> bluez-firmwarem and dahdi-firmware? At which stage(s) of an
> installation does d-i become aware of them?
>

Some of these are recognised at inital boot: if unsure, they can be
added. For myself, I normally install the metapackages firmware-linux-nonfree
and firmware-misc-nonfree which solve the problem. As the discussion elsewhere
on Debian mailing lists is showing, it is really very difficult indeed to
do without all firmware.

All the very best, as ever,

Andy Cater

> --
> Brian.
>

Re: email lacks sender address

[Haines Brown]

On Tue, Apr 26, 2022 at 10:10:48AM +0100, Jonathan Dowland wrote:
> On Mon, Apr 25, 2022 at 11:39:01AM -0400, Haines Brown wrote:
> > I infer that exim is not being given the envelop address of the
> > sender.
> 
> Quoting /etc/exim4/exim4.conf.template:
> 
> # By default, exim forces a Sender: header containing the local
> # account name at the local host name in all locally submitted messages
> # that don't have the local account name at the local host name in the
> # From: header, deletes any Sender: header present in the submitted
> # message and forces the envelope sender of all locally submitted
> # messages to the local account name at the local host name.
> # The following settings allow local users to specify their own envelope 
> sender
> # in a locally submitted message. Sender: headers existing in a locally
> # submitted message are not removed, and no automatic Sender: headers
> # are added. These settings are fine for most hosts.
> # If you run exim on a classical multi-user systems where all users
> # have local mailboxes that can be reached via SMTP from the Internet
> # with the local FQDN as the domain part of the address, you might want
> # to disable the following three lines for traceability reasons.
> .ifndef MAIN_FORCE_SENDER
> local_from_check = false
> local_sender_retain = true
> untrusted_set_sender = *
> .endif
> 
> Jonathan Dowland
> ✎  j...@debian.org
>  https://jmtd.net

Johathan, many thanks for pointing out the content of exim 
configuration template. The exim config files are so intimidating that 
unless there is a reason to so so an amateur like myself tries to 
avoid them.

What I get out of this is that my MUA (mutt) might generate a message 
that lacks a local account name (I assume it is defined by the content 
of /etc/mailname, whicn in my case happens to be lenin.histomat.net). 
I infer this is the value that appaars in the Sender: line of the 
message header consructed by mutt. 

The above text describes what exim does if that Sender: line in the 
header happens to be empt or missing. If I understand correctly, exim 
deletes the empty Sender: line and instead uses the value of 
/etc/mailname to be the envelop sender. Is this so?

The text goes on to say that if the three lines it specifies at the 
end are present, it allows the user to specify whatever he/she 
likes to appear as the envelop's sender.

This raises questions. 

First, the implication seems to be that an empty Sender: line means 
that mutt is falling down on the job and for some reason this past 
week ceasad to provide a value for the Sender: line in the header of 
the some mail it sent to exim. So is the obvious thing to do is fix 
mutt? Since I've been using the same mutt configuration for years, its 
not a configuration problem but samage to mutt. Looks like a reinstall 
and slow reconstruction of its confirturation. 

I already ran mutt without any configuration and it didn't seem to 
help.  I sumitted by domain name to an online mail tesing site and get 
"Unverified address: postoffice.omnis.com said: 521 5.5.1 Protocol 
error." Omnis told me the problem was the Sender: line was empty in 
some messages.  
 
Another question. The implication is that if the three lines are 
present in the exim configuration it whould allow the user to specify 
the envelop sender. Is this merley a statement of fact or 
is the template file used to construct the exim configuration? If the 
latter, then I should be able to write my own envelope sender line.

I can't imagine why I would want to do that, but if I did, how does 
one go about doing it? In the exim4 configuraiton routine one defines 
the define default system mail name. Is this value the name used for 
the envelope sender? Sometimes I have merely put in the host name and 
some times appended the domain name to it. Seems to work in either 
case. When the problem being discussed came up I changed from the 
former to the latter when I reconfigured exim. It did not help.

In exim configuration I hide outgoing local mail name and provide
the domain name without prepending host name. I assume
this is irrevant and is merley a cosmetic isaue. Is that so?

Re: [HS] Recherche spécialiste PHP-7

[Daniel Caillibaud]

Le 25/04/22 à 12:00, ajh.val...@bbox.fr a écrit :
> Bonjour,
> 
> Je recherche un bon spécialiste PHP-7.2.

Euh, je crois que tu peux passer directement à php8.1, 7.2 était maintenue 
jusqu'à fin 2020,
7.3 est déjà en EOL et 7.4 meurt dans 6 mois.

Avec 8.1 tu peux tenir jusque fin 2024 : 
https://www.php.net/supported-versions.php

Sur https://www.php.net/eol.php tu as les liens vers les guides de migration 
(5.6 > 7.0 > 7.1 >
7.2 > 7.4 > 8.0 > 8.1), avec à chaque fois la liste de ce qui change.

-- 
Daniel

On ne peut pas juger quelqu'un à ses fréquentations ;
ne perdons pas de vue que Judas avait des amis irréprochables.
Tristan Bernard

Re: zwart op wit, constrastrijk

[Paul van der Vlis]

Op 25-04-2022 om 12:31 schreef Paul van der Vlis:

Ik ben een andere terminal gebruiken ("mate-terminal"), deze heeft 
default een zwarte achtergrond. Daarop zie je wel goed de lichte kleuren.


Mate-terminal is verder ook een fijne terminal, die alles kan wat ik 
nodig heb.


Wat ik bijvoorbeeld belangrijk vind is dat ik de titel kan aanpassen, 
zodat ik terminals goed van elkaar kan onderscheiden (ik heb altijd heel 
veel terminals open).


Groet,
Paul


--
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl/

Re: Recommendations for a home server running Debian Bullseye (11)?

[Christian Britz]

On 2022-04-26 10:49 UTC+0200, Jeremy Ardley wrote:

> I also use a fanless home server, but it's definitely no slouch.
> 
> My one is a NanoPi M4V2 usingRockchip RK3399 64-bit Dual Core Cortex-A72 + 
> Quad Core Cortex-A53 It 
[...]
> snappy. It gets 12.47 seconds in the hardinfo n-queens test which is 
> slightly slower than an Intel Core-2 Duo T7250 @ 2GHz What does the 
> RPi4B get on hardinfo? -- 

12.06 - not too bad compared to the 7.33 of the Intel Core i5-1035G1 of
my IdeaPad! :-)

-- 
http://www.cb-fraggle.de

Re: email lacks sender address

[Jonathan Dowland]

On Mon, Apr 25, 2022 at 11:39:01AM -0400, Haines Brown wrote:

I infer that exim is not being given the envelop address of the
sender.


Quoting /etc/exim4/exim4.conf.template:

# By default, exim forces a Sender: header containing the local
# account name at the local host name in all locally submitted messages
# that don't have the local account name at the local host name in the
# From: header, deletes any Sender: header present in the submitted
# message and forces the envelope sender of all locally submitted
# messages to the local account name at the local host name.
# The following settings allow local users to specify their own envelope sender
# in a locally submitted message. Sender: headers existing in a locally
# submitted message are not removed, and no automatic Sender: headers
# are added. These settings are fine for most hosts.
# If you run exim on a classical multi-user systems where all users
# have local mailboxes that can be reached via SMTP from the Internet
# with the local FQDN as the domain part of the address, you might want
# to disable the following three lines for traceability reasons.
.ifndef MAIN_FORCE_SENDER
local_from_check = false
local_sender_retain = true
untrusted_set_sender = *
.endif


--
Please do not CC me for listmail.

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

Re: Recommendations for a home server running Debian Bullseye (11)?

[Jonathan Dowland]

On Mon, Apr 25, 2022 at 10:25:46AM -0500, Tom Browder wrote:

I am looking for a commercial grade server (for home use) to replace my
remote ones. I am looking at Dell's site and an almost-empty chassis with a
low-end Intel, 1 TB SATA, and 8 Gb ECC  RAM is in the $800 ball park. It
looks very upgradeable.

Anyone have any suggestions on whether to buy or not? I would add at least
two 1 Tb SSD from Crucial to it.


I don't think you've provided enough information about how you want to
use it and any other constraints (noise, space, energy cost) which play
into the decision making, but here's a write-up of my home server in
case it's any use:



--
Please do not CC me for listmail.

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

Re: Recommendations for a home server running Debian Bullseye (11)?

[Jeremy Ardley]

On 26/4/22 2:56 pm, Christian Britz wrote:


On 2022-04-25 23:58 UTC+0200, Stefan Monnier wrote:


That's quite vague.  I myself use a BananaPi as home server with good
results (for my use case anyway), but I'm pretty sure that it wouldn't
cover half the needs of some other people's notion of "home server".

I agree with Stefan. I am using myself a fanless Raspberry PI 4B as a
home server and it is perfectly able to serve DLNA, files, low traffic
web and an IRC proxy, most of the times it is idling.



I also use a fanless home server, but it's definitely no slouch.

My one is a NanoPi M4V2 usingRockchip RK3399 64-bit Dual Core Cortex-A72 + Quad Core Cortex-A53 It 
also has a very fast NVME drive (Though you still have to keep your boot 
sector on the SD) The good things about it are 4 GB RAM, 4 USB3 ports, 
Gigabit LAN, Wireless LAN and bluetooth (plus heaps extra to make it a 
workstation). It runs armbian out of the box. It seems to be very 
snappy. It gets 12.47 seconds in the hardinfo n-queens test which is 
slightly slower than an Intel Core-2 Duo T7250 @ 2GHz What does the 
RPi4B get on hardinfo? -- 


Jeremy



OpenPGP_signature
Description: OpenPGP digital signature

"Disabling IRQ #9" - how to check for impact

[Christian Britz]

Hello Debianists,

some days ago I updated the BIOS of my Lenovo IdeaPad S145-15IIL (had to
boot a certain proprietary OS for this). I think since then there is a
new error in the kernel log. I never noticed it before.

[9.967601] irq 9: nobody cared (try booting with the "irqpoll" option)
[9.967607] CPU: 1 PID: 981 Comm: sddm-greeter Tainted: G
OE 5.10.0-13-amd64 #1 Debian 5.10.106-1
[9.967608] Hardware name: LENOVO 81W8/LNVNB161216, BIOS DKCN54WW
01/27/2022
[9.967608] Call Trace:
[9.967615]  dump_stack+0x6b/0x83
[...]
[9.967636] handlers:
[9.967639] [<872fa119>] acpi_irq
[9.967640] Disabling IRQ #9

This IRQ seems to be related to ACPI on this machine. I am unsure, what
exactly gets diabled and what might be the impact. So far I notice no
problems with performance or overheating, compiling a small tool went as
always I would say.

Do you have any hints for me about what I should/could check?

Regards,
Christian

-- 
http://www.cb-fraggle.de

Re: Debian 11 bullseye - will it work on 12th gen core i3-12100?

[Christian Britz]

On 2022-04-25 19:16 UTC+0200, Georgi Naplatanov wrote:

> Debian 11 was released almost 1 year ago. For new hardware you will need
> Debian testing. For Debian 11 (current stable) you'll need second hand
> hardware.

Or a kernel from backports. There was a discussion on this list recently
about how to integrate a backported kernel into the installer. I did not
try it out though.

-- 
http://www.cb-fraggle.de

Re: Recommendations for a home server running Debian Bullseye (11)?

[Christian Britz]

On 2022-04-25 23:58 UTC+0200, Stefan Monnier wrote:

> That's quite vague.  I myself use a BananaPi as home server with good
> results (for my use case anyway), but I'm pretty sure that it wouldn't
> cover half the needs of some other people's notion of "home server".

I agree with Stefan. I am using myself a fanless Raspberry PI 4B as a
home server and it is perfectly able to serve DLNA, files, low traffic
web and an IRC proxy, most of the times it is idling.

The "commercial grade" beast which you describe sounds very different to
a "normal" home server use case, so you should maybe better describe the
scenario for the operation of the server. If it is supposed to host high
traffic websites, your home internet connection might be the limiting
factor anyway, not the hardware specs.

Regards,
Christian

-- 
http://www.cb-fraggle.de