Re: Can't list root directory

[Loren M. Lang]

On January 31, 2024 1:28:37 PM PST, hw  wrote:
>On Wed, 2024-01-31 at 09:27 -0500, Gary Dale wrote:
>> On 2024-01-30 15:54, hw wrote:
>> > On Mon, 2024-01-29 at 11:42 -0500, Gary Dale wrote:
>> > > I'm running Debian/Trixie on an AMD64 workstation. I've lost the ability
>> > > to see the root directory even when I am logged in as root (su -).
>> > > 
>> > > This has been happening intermittently for several months. I initially
>> > > thought it might be related to failing NVME drive that was part of a
>> > > RAID1 array that is mounted as "/" but I replaced the device and the
>> > > problem is still happening.
>> > > [...]
>> > What happens when you put the device you replaced back?
>> > 
>> How could putting a known-failing device back in help? The problem 
>> existed before I replaced it and continues to exist after the replacement.
>
>It sounded like you were able to list the root directory (at least
>sometimes) before you did the replacement.  Manually failing the
>device (perhaps after adding it back first) could make a difference.
>
>I've seen such indefinite hangs only when an NFS share has become
>unreachable after it had been mounted.  You could use clonezilla to
>make a copy and then perhaps convert the file system to btrfs.
>
>Do you still have the problem when you remove one of the NVME storage
>things?  Perhaps you have the equivivalent of a bad SATA cable or the
>mainboard doesn't like it when you access two of those at the same
>time, or something like that.  Even simple network cables can behave
>very strangely, and NVME may be a bit more complicated than that.
>
>Running fsck on every boot to work around an issue like this is
>certainly a bad idea.  Doesn't fsck report anything?  If it really
>makes a difference in itself rather than creating some side effect
>that leads to the root directory being readable, it should report
>something.  Perhaps you need to increase its verbosity.
>
>If there's no report then it would look like a side effect and raise
>the question what side effect it might be.  Does fsck run before the
>RAID has been brought up or after?  Is the RAID up when booting is
>completed?  What does mdadm say about the device(s)?  Can you still
>list the root directory when you manually fail either drive?  What
>exactly are the circumstances under which you can and not list the
>root directory?
>
>You need to do some investigating and ask questions like those ...
>

Also, instead of doing "ls -l /" which will stat() every child folder under 
root, try "/bin/ls -f /" and see if that is successful. That will only do a 
readdir() on root itself. Also, it might be interesting to get a log of "strace 
ls -l /" to confirm exactly where the hang happens.

-Loren 

-- 
Sent from my Nexus 4 with K-9 Mail. Please excuse my brevity.

bibliothèque libre C ou C++ Debian compatible pour JSON5 ou HJSON

[Basile Starynkevitch]

Bonjour la liste


Pour le moteur d'inférences RefPerSys (voir http://refpersys.org/ ) 
je cherche une bibliothèque libre (sous licence GPLv3+ ou LGPLv2+ ou 
compatible au moins avec la licence CeCILL) qui peut encoder et décoder 
des fichiers et des chaînes de caractères (encodées UTF-8) au format 
JSON5 (voir https://json5.org/ ...) ou HJSON (voir 
https://hjson.github.io/ ou j'ai trouvé 
https://github.com/hjson/hjson-cpp/releases ...)



Avez vous une telle bibliothèque à me suggérer?


(je cherche aussi des contributeurs, ou des possibilités de faire un 
exposé dans la suite de ceux faits en 2020 en 
https://afia.asso.fr/journee-hommage-j-pitrat/ ...)


Librement

--
Basile Starynkevitch 
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
See/voir:   https://github.com/RefPerSys/RefPerSys

Re: Memoria Intel Optane Debian 12

[Roberto José Blandino Cisneros]

El 8/12/23 a las 03:12, Camaleón escribió:

El 2023-12-07 a las 18:51 -0500, Gabo escribió:


El jue, 7 de dic de 2023, 12:02, Camaleón  escribió:


El 2023-12-06 a las 20:48 -0500, Gabo escribió:


Quería saber si es posible utilizar o configurar la memoria Intel Optane

de

un laptop acer al cual le instalé Debian 12.

Se supone que esa memoria sirve para acelerar el computador. Esto es
posible para debian 12?

Si tienes un sistema Optane compatible, en teoría no tienes que hacer
nada, debe estar configurado de fábrica para tener el mejor
rendimiento:

Memoria Intel Optane™ en computadoras Acer

https://community.acer.com/es/kb/articles/14274-memoria-intel-optane-en-computadoras-acer

(...)


Ahora bien, por aquí dicen Intel que NO es compatible con Linux:

***
Es compatible la memoria Intel® Optane™ con Linux*?

https://www.intel.la/content/www/xl/es/support/articles/56875/memory-and-storage/intel-optane-memory.html

La aceleración del sistema con memoria Intel® Optane™ es compatible con
el sistema operativo Windows 10 de 64 bits.  No es compatible con
ningún otro sistema operativo, incluyendo Linux.
***


Sí, efectivamente, yo había visto este artículo, estaba pensando en que
depronto alguien hubiera desarrollado algún tipo de controlador, pero con
software basado en Linux/Debian, para poder usar esa memoria como caché o
algo así y mejorar el rendimiento del computador, pero eso es como difícil
de hacer.

Cuando escribo el comando lspci o fdisk -l, no veo que diga Intel Optane o
similar, es como si no la viera.

Me da la sensación que eso del Optane es similar al falso RAID (Intel
Matrix) y esos inventos que se sacan de la manga las megaempresas a las
que les gusta las técnicas de mercadontecnia más que una zanahoria a un
burro :-)


Ante la duda, en Linux evitaría usar o configurar nada que no fuera
estándar/normalizado, para evitar cualquier problema de compatibilidad,
presente y/o futuro :-/


Muchas gracias Camaleón por tu respuesta.

Es que al computador, que originalmente tenía Windows 10, con su memoria
Intel Optane, iniciaba súper rápido, luego se me metió como un virus y tuve
que restablecerlo, pero luego salió actualización a Windows 11 y quedó muy
lento. Entonces dije, Debian el mejor! Y lo instalé, pero también quedó
como lento, incluso en funciones sencillas ya con debían 12 y entorno KDE
plasma, con comandos sencillos como cambiar entre ventanas con alt+Tab se
queda como trabado, pensé que esa memoria Intel Optane podría causar alguna
incompatibilidad

Este portátil tiene 4GB de RAM, será muy poca para debian 12 y KDE plasma?

Te diría que 4 gigas de RAM HOY es poco para todo, salvo que uses un
sistema muy afinado (p. ej., una distribución de Linux tipo súper-ligera como
Tiny o Puppy y además, con un entorno gráfico básico, como XFCE o LXDE,
o simplemente un gestor de ventanas).

Pero GNOME, KDE y las aplicaciones convencionales (LibreOffice,
Firefox, Chrome...) te van a pedir «manduca».

En cualquier caso, Intel ha dejado de desarrrollar Optane¹ (por algo
será), así que para mejorar el rendimiento general del equipo, optaría
por desactivar de la BIOS/UEFI² toda referencia a Optane, manteniendo un
sistema lo más limpio, neutral y normalizado posible, y añadiaría el
máximo de memoria RAM física que te admita el equipo.

Yo estoy con un equipo viejote del año 2008 y 8 GiB de RAM (la placa
base no admite más), pero para los discos mecánicos he activado AHCI,
tengo XFCE y he desactivado todo lo relativo a la aceleración gráfica
3D en el navegador y los efectos del entorno gráfico, etc.

El equipo vuela, como si Red Bull le hubiera dado aalas :-)

sm01@stt008:~$ cat /proc/cpuinfo | grep name | head -n 1
model name  : Intel(R) Core(TM)2 Quad CPUQ9550  @ 2.83GHz

sm01@stt008:~$ cat /proc/meminfo | head -n 1
MemTotal:8134172 kB


Y si a lo que ha dicho Camaleón le sumas reemplazar tus discos mecánicos 
por sólidos,

eso acelerará tu equipo.

Y recuerda que en discos sólidos se recomienda no usar swap.

Yo me he quedado prendado de XFCE4, con baja o alta memoria, me he 
quedado con este

escritorio.

Pero ahí la magia de linux, escoges el que más te guste o te sea útil en 
tu escritorio ya sea

por recursos o por lujo.

Saludos.



¹ 
https://www.intel.com/content/www/us/en/support/articles/91826/memory-and-storage.html
² Sólo si vas a instalar desde cero el equipo, no hagas cambios de
este tipo con un sistema operativo ya instalado y funcionando ya que te
lo pude dejar inoperativo.

Saludos,

Re: ⚠ No actualicéis a Debian 12.3 ⚠

[Roberto José Blandino Cisneros]

El 16/12/23 a las 15:18, JavierDebian escribió:



El 10/12/23 a las 06:15, Camaleón escribió:

Hola,

Pues eso, acabo de leer que se retrasa por problemas con un bug de ext4
(corrupción de archivos) y en Debian recomiendan PAUSAR las 
actualizaciones,

sobre todo en sistemas que tienen configuradas las actualizaciones
desatendidas.

Debian 12.3 image release delayed
https://www.debian.org/News/2023/2023120902

P.S. El asunto se inicia y finaliza con dos símbolos unicode con la
señal de peligro (⚠) a ver cómo se renderiza :-)

Saludos,




Buenas tardes.

Leí este primer mensa hace 5 días.
Y me abstuve de cualquier actualización en esta semana.
A pesar que mi sistema es
$ cat /etc/debian_version
12.4

$ uname -a
Linux  6.5.0-0.deb12.4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.5.10-1~bpo12+1 (2023-11-23) x86_64 GNU/Linux



Yo estoy usando el siguiente sistema:

$ cat /etc/debian_version
12.4

Y el siguiente kernel:

$ uname -a
Linux pc-home 6.1.0-16-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.67-1 
(2023-12-12) x86_64 GNU/Linux


No he presentado problemas


Hoy estuve leyendo esto:
https://www.somoslibres.org/index.php/12-nieuws/debian/12413-debian-12-4-disponible-con-docenas-de-correcciones 



Corrección de errores de EXT4

La versión 12.4 de Debian aborda un aviso de error crítico, #1057843, 
relativo a problemas con kernel-image-6.1.0-14 (6.1.64-1) relacionados 
con la corrupción de datos del sistema de archivos ext4. Para 
solucionarlo, Debian ha lanzado kernel-image-6.1.0-15 (6.1.66) en esta 
actualización, asegurando una funcionalidad ext4 más estable.
El fallo era grave, y el equipo pidió que se pospusieran las 
actualizaciones con anterioridad. Sin embargo, ahora puede seguir 
adelante y actualizar sus sistemas Debian.


JAP

Re: Como hacer una partición no destructiva?

[Roberto José Blandino Cisneros]

El 19/1/24 a las 13:02, Jude_xiomi Sago escribió:

El vie, 19 ene 2024 a las 13:50, Jude_xiomi Sago
() escribió:

Hola, buen día!

El jue, 18 ene 2024 a la(s) 3:22 p.m., Camaleón (noela...@gmail.com) escribió:

El 2024-01-18 a las 08:36 -0500, Jude_xiomi Sago escribió:


El jue, 18 ene 2024 a las 8:32, Jude_xiomi Sago
() escribió:

El 2024-01-17 a las 14:44 -0500, Jude_xiomi Sago escribió:
Identificador del disco: 0xcbe73cf0


Disposit.  Inicio  Comienzo Final  Sectores Tamaño Id Tipo
/dev/sda1  *   2046 107438079 107436034  51,2G  5 Extendida
/dev/sda2 107438080 976773167 869335088 414,5G  7 HPFS/NTFS/exFAT
/dev/sda5  2048  20269055  20267008   9,7G 83 Linux
/dev/sda6  20271104  27674623   7403520   3,5G 83 Linux
/dev/sda7  27676672  31848447   4171776 2G 82 Linux swap / Solaris
/dev/sda8  31850496  33257471   1406976   687M 83 Linux
/dev/sda9  33259520 107438079  74178560  35,4G 83 Linux


sda1 es partición extendida y ahí no hay nada

Lo que me desconcierta es que ocupa 51,2 GiB :-?

Si!. Es desconcertante, pero esa fué la opción automática que me
propuso el instalador cuando se instaló bullseye en instalación limpia
(disco nuevo).
Lo cierto es debo actualizarme a la versión 12 y voy a intentar
solucionar el inconveniente de poco espacio para la raíz / .
Gracias por el interés...


Bueno antes de hacer, primero respaldar para luego deshacer.

Ya que la partición sda1 es una partición extendida, deberás reducir 
primero sda2, luego darle el espacio a sda1.


Ahora te enfrentarás con un problema que el espacio ganado de sda2 
cambiará el final "107438079" de sda1.


Ahora, si quieres agrandar sda5, si te fijas, esta partición que es la 
que quieres tocar, está hasta el principio de la partición extendida "sda1".


Deberás mover sda9, sda8, sda7 y sda6 todo a la derecha para darle 
espacio libre a sda5 y luego agrandar hasta ocupar este espacio disponible.


Con Gparted lo haces desde el modo gráfico, claro desde un liveCD.

Haz respaldo antes de probarlo hacer manualmente desde cli.


Da la impresión de que la partición sda1 es la extendida donde están
sda5 a sda9 que son las lógicas.
Si te fijas la suma de sus tamaños es igual a tamaño de sda1.


...
Saludos,

--
Camaleón


Saludos
--
Jorge A Secreto
Analista de Sistemas
MP 361

Gracias por el interés...

Re: Como hacer una partición no destructiva?

[Roberto José Blandino Cisneros]

El 19/1/24 a las 05:20, Jorge Abel Secreto escribió:

Hola, buen día!

El jue, 18 ene 2024 a la(s) 3:22 p.m., Camaleón (noela...@gmail.com) escribió:

El 2024-01-18 a las 08:36 -0500, Jude_xiomi Sago escribió:


El jue, 18 ene 2024 a las 8:32, Jude_xiomi Sago
() escribió:

El 2024-01-17 a las 14:44 -0500, Jude_xiomi Sago escribió:
Identificador del disco: 0xcbe73cf0


Disposit.  Inicio  Comienzo Final  Sectores Tamaño Id Tipo
/dev/sda1  *   2046 107438079 107436034  51,2G  5 Extendida
/dev/sda2 107438080 976773167 869335088 414,5G  7 HPFS/NTFS/exFAT
/dev/sda5  2048  20269055  20267008   9,7G 83 Linux
/dev/sda6  20271104  27674623   7403520   3,5G 83 Linux
/dev/sda7  27676672  31848447   4171776 2G 82 Linux swap / Solaris
/dev/sda8  31850496  33257471   1406976   687M 83 Linux
/dev/sda9  33259520 107438079  74178560  35,4G 83 Linux


sda1 es partición extendida y ahí no hay nada

Lo que me desconcierta es que ocupa 51,2 GiB :-?

Da la impresión de que la partición sda1 es la extendida donde están
sda5 a sda9 que son las lógicas.
Si te fijas la suma de sus tamaños es igual a tamaño de sda1.


No es que dé la impresión, así es, está usando un particionado MSDOS y 
no GPT, basta con leer el comienzo y el final de cada partición, si no 
usa EFI, que siga usando MSDOS, aunque GPT tiene grandes ventajas, entre 
las cuales ya prácticamente es que soporta más de 4 particiones primarias.


sda1
  |
  |-sda5
  |-sda6
  |-sda7
  |-sda8
  |-sda9




...
Saludos,

--
Camaleón


Saludos

Re: Como hacer una partición no destructiva?

[Roberto José Blandino Cisneros]

El 18/1/24 a las 07:36, Jude_xiomi Sago escribió:

El jue, 18 ene 2024 a las 8:32, Jude_xiomi Sago
() escribió:

El 2024-01-17 a las 14:44 -0500, Jude_xiomi Sago escribió:


Buenas tardes y Feliz año.

Igualmente :-)


Tengo un problemilla que me impide actualizarme a la versión 12 de debian.
Se trata de poco espacio para la partición raíz /
(
sudo fdisk -l /dev/sda
Disco /dev/sda: 465,76 GiB, 500107862016 bytes, 976773168 sectores
Modelo de disco: WDC WD5000AVDS-6
Unidades: sectores de 1 * 512 = 512 bytes
Tamaño de sector (lógico/físico): 512 bytes / 512 bytes
Tamaño de E/S (mínimo/óptimo): 512 bytes / 512 bytes
Tipo de etiqueta de disco: dos
Identificador del disco: 0xcbe73cf0

Disposit.  Inicio  Comienzo Final  Sectores Tamaño Id Tipo
/dev/sda1  *   2046 107438079 107436034  51,2G  5 Extendida
/dev/sda2 107438080 976773167 869335088 414,5G  7 HPFS/NTFS/exFAT
/dev/sda5  2048  20269055  20267008   9,7G 83 Linux
/dev/sda6  20271104  27674623   7403520   3,5G 83 Linux
/dev/sda7  27676672  31848447   4171776 2G 82 Linux swap / Solaris
/dev/sda8  31850496  33257471   1406976   687M 83 Linux
/dev/sda9  33259520 107438079  74178560  35,4G 83 Linux

Las entradas de la tabla de particiones no están en el orden del disco.
)
Como puede verse, /dev/sda2 que una partición de guardar diferentes
archivos tiene 414,5 Gigas, mientras que la partición raíz /dev/sda5 tiene
solamente 9,7 gigas y es insuficiente para cualquier nueva versión.
/dev/sda9 está funcionando como /home y me gustaría no tocarla.
He pensado borrar sda5, sda6, sda7,  sda8 y hacer una partición no
destructiva con /dev/sda2 y sacarle unos cuantos gigas para re-acomodar
otra vez la partición raiz con al menos unos 25 gigas.
Pregunta del millón:
Es posible?... y con que programa?... fdisk no me parece apto.

Yo noy soy muy dada a particionar porque al final siempre acabas con
escasez de espacio.

Eso sí, las copias de seguridad son sagradas :-)

Podrás unir las particiones que estén consecutivas, esto es, sda5,
sda6, sda7 y sda8 (ya que dices que sda9 no la quieres tocar) y podrás
sacar una nueva partición para la raíz.

¿Qué tienes en sda1 y sda2? ¿Un sistema con Windows o sólo datos?

El programa a usar sería parted (o Gparted) es el más completo para
esto, creo yo.

https://gparted.org/display-doc.php?name=help-manual=es

No necesitas partición para la memoria de intercambio (/swap), puedes
usar un archivo.

Saludos,

--
Camaleón

Gracias por tu ayuda.

sda1 es partición extendida y ahí no hay nada

sda6 es /var

sda7 es /swap

sda8 es /tmp


Nunca has intentado grabar nada de iso o mover cosas, ese tmp lo veo muy 
pequeño
esa partición es usada incluso por el instalador apt y por muchas otras 
tareas temporales
siempre es recomendable que sea del mismo tamaño y un poco mayor al de 
los discos
ISO ya que es usado para almacenar respaldos temporales o paquetes 
transitorios y a veces
el sistema usa el /tmp para desdoblarlos y luego manipularlos, te 
recomiendo un /tmp de

al menos 20G mínimo y no tendrás casi nunca problema alguno.

La swap, a menos que sea una laptop y necesites mandarla a hibernar, 
requeriras que

sea igual que la RAM para mandar a grabar todo lo que esta en RAM a la swap.



sda2 Es donde guardo lo que ya no cabe /home y tiene bastante espacio
de sobra como para sacarle un poquito y regalárselo a /raiz, pero como
tiene datos, no se si estarán regados (fragmentados). Alguna
aplicación que los organice al comienzo para quitarle un poco al final
sin perder o dañar archivos?… o el mismo gparted lo hace.

No tiene sentido tener una partición aparte del /home, pero bueno,
sobre los datos regados eso no debes preocuparte es irrelevante para ti,
a eso le corresponde el sistema de archivos que uses ext4, zfs, btrfs, etc.
Por lo tanto no deberías preocuparte si están o no regados, en caso que
hagas uso de gparted, el se encargaría de todo.

Cuando reduces o redimensionas una partición no pierdes datos, a menos
que en el mismo momento tu disco de un problema de hardware que con
casualidad sea en el momento que particionas, pero sería un evento aislado.



De nuevo gracias lista...

Re: Como hacer una partición no destructiva?

[Roberto José Blandino Cisneros]

El 17/1/24 a las 13:44, Jude_xiomi Sago escribió:

Buenas tardes y Feliz año.
Tengo un problemilla que me impide actualizarme a la versión 12 de debian.
Se trata de poco espacio para la partición raíz /
(
sudo fdisk -l /dev/sda
Disco /dev/sda: 465,76 GiB, 500107862016 bytes, 976773168 sectores
Modelo de disco: WDC WD5000AVDS-6
Unidades: sectores de 1 * 512 = 512 bytes
Tamaño de sector (lógico/físico): 512 bytes / 512 bytes
Tamaño de E/S (mínimo/óptimo): 512 bytes / 512 bytes
Tipo de etiqueta de disco: dos
Identificador del disco: 0xcbe73cf0

Disposit.  Inicio  Comienzo     Final  Sectores Tamaño Id Tipo
/dev/sda1  *           2046 107438079 107436034  51,2G  5 Extendida
/dev/sda2         107438080 976773167 869335088 414,5G  7 HPFS/NTFS/exFAT
/dev/sda5              2048  20269055  20267008   9,7G 83 Linux
/dev/sda6          20271104  27674623   7403520   3,5G 83 Linux
/dev/sda7          27676672  31848447   4171776     2G 82 Linux swap / 
Solaris

/dev/sda8          31850496  33257471   1406976   687M 83 Linux
/dev/sda9          33259520 107438079  74178560  35,4G 83 Linux

Las entradas de la tabla de particiones no están en el orden del disco.
)
Como puede verse, /dev/sda2 que una partición de guardar diferentes 
archivos tiene 414,5 Gigas, mientras que la partición raíz /dev/sda5 
tiene solamente 9,7 gigas y es insuficiente para cualquier nueva versión.

/dev/sda9 está funcionando como /home y me gustaría no tocarla.
He pensado borrar sda5, sda6, sda7,  sda8 y hacer una partición no 
destructiva con /dev/sda2 y sacarle unos cuantos gigas para 
re-acomodar otra vez la partición raiz con al menos unos 25 gigas.

Pregunta del millón:
Es posible?... y con que programa?... fdisk no me parece apto.



Si es posible, la forma fácil es usar un livecd, instalas el gparted y 
reordenas.


La forma larga, haz un backup, destruyes y restauras hasta tener las 
particiones al tamaño deseado.


¿Nunca haz pensado en LVM, antes no me gustaba pero luego empecé a 
encontrar el placer en LVM, más cuando se trata de redimensionar y a 
veces en caliente?




Gracias por alguna solución.

Re : [HS] aide à la traduction

[k6dedijon]

Bonjour Norbert,
Lorsque tu veux traduire un texte, tu le sélectionne, puis le copie et enfin tu 
le mets dans la case de la fenêtre d'un moteur de traduction comme :
https://www.deepl.com/translator 
ou 
https://www.bing.com/Translator

Voilà
Cassis



- Mail d'origine -
De: Norbert Ponce 
À: debian-user-french@lists.debian.org
Envoyé: Wed, 31 Jan 2024 15:02:58 +0100 (CET)
Objet: [HS] aide à la traduction

Bonjour,
J'ai reçu plusieurs messages comme celui que je vous transmets. Je ne 
maîtrise aucunement l'anglais.
Quelqu'un pourrait-il m'expliquer de quoi il s'agit et ce qu'il faut que 
je fasse.
Merci


 Message transféré 
Sujet : lists.debian.org has received bounces from 
ponce.norb...@orange.fr
Date :  Sun, 28 Jan 2024 10:45:27 + (UTC)
De :Debian Listmaster Team 
Répondre à :listmas...@lists.debian.org
Pour :  ponce.norb...@orange.fr



Dear subscriber,

We've encountered some problems while sending listmail to your
emailaddress ponce.norb...@orange.fr.

In the last seven days we've seen bounces for the following list:
* debian-user-french
1 bounce out of 39 mails in 7 days (2%, kick-score is 80%)
(https://lists.debian.org/bounces/MzZq8GgorlrkIynI7O8JoA)

(The link above points to a copy of the latest bounce
and will be valid for seven days.)

If the bounce-rate passes the kick-score, our bounce-detection will forcibly
remove your subscription.

Bounces happen from time to time when spam slips through our filters but are
rejected by your mail provider. If you are your own mail provider and use
'Before-Queue Content filtering', you should whitelist bendel.debian.org 
from
Content filtering.

However: You can safely ignore this message (and you will not be 
unsubscribed
:-) ) if your bounce rate remains low.

For more information see https://wiki.debian.org/Teams/ListMaster/FAQ

You are welcome to contact listmas...@lists.debian.org if you think this
message was sent in error.

Sincerely,
The Listmaster Team

-- 
http://lists.debian.org

Re: Cifrado de disco sin contraseña

[Roberto José Blandino Cisneros]

El 31/1/24 a las 13:41, Josu Lazkano escribió:

Buenas,

Llevo tiempo cifrando las particiones de Debian mediante LUKS, 
funciona muy bien. Pide una contraseña en el arranque y se accede al 
sistema.

Nunca he realizado cifrado de particiones, la verdad que no.


Pero he visto que en algunos entornos corporativos, los equipos 
Windows se pueden cifrar con Bitlocker y no pide contraseña, se 
descifra al hacer un login correcto en dominio.


Pero algo que podría ser equivalente es revisar si tu máquina soporta 
TPM y por ahí podes irte, pero sería desbloquear la partición desde el 
boot, al final lo cual no tendría mucho sentido y no sería recomendado.


*** La otra posibilidad sería hacer uso del PAM, háchale un ojo a este 
link: "https://wiki.archlinux.org/title/Dm-crypt/Mounting_at_login; 
puedes tomarlo de referencia, creo que es lo que buscas.


Pero siempre que sea un ordenador personal, en caso de ser multiusuario 
se requiere confiabilidad en este caso ya que para desbloquer se 
requiere siempre la misma contraseña.


Entiendo que Windows hace algo similar, a menos que particiones el home 
para cada usuario y que cada usuario haga uso de su mismo password para 
cifrar y descifrar su propio /home/$user.




¿Sabeis si es posible hacer algo parecido en Debian? Que el disco esté 
cifrado y al hacer un login válido se descifre?


Se agradece cualquier sugerencia o comentario.

Un saludo.

--
Josu Lazkano

Re: chrony date months off

[gene heskett]

On 1/31/24 21:50, Max Nikulin wrote:

On 31/01/2024 20:24, didar wrote:

On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
How do I setup /etc/chrony/chrony.conf so it slams the system clock 
to the

current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate command that would do that.


You can use "rdate" (openrdate) as quick fix like `ntpdate'.
Is there a real reason to install an extra package if chrony provides a 
tool similar to ntpdate?


If I recall it right, the reason why chrony appeared here was just

$ man timesyncd
No manual entry for timesyncd

If it is that box with armbian modified by a Chinese 3d printer vendor 
then I am surprised that, intended for boards without RTC, it does not 
have proper NTP setup out of the box. Despite I expect arbitrary 
peculiarities in this kind of a Linux distribution, I still believe that 
NTP troubles were caused by user actions.


I'd argue that in the bigger picture, the edge distributions, some of 
which are one man operations or very close to it, like armbian, know 
these are often used in offline environments where it is not that 
important. But the minute you plug in the cat-# it is a different story. 
We are doing things with baby arm's that would normally take a 6 core i5 
to do, but doing it 1/4 as fast and on only 5% of the power.  That fast 
enough to get the job done, but lack of attention to what s/b just works 
stuff says bad code is still bad code. I'm finally understanding things 
the man pages will never tell you, about interdependentcy's. Once you 
begin to understand how timedatectl actually works, it all falls into 
place and just works.


My goal in much of this is to reduce my visibility on the net, so I now 
have only a one machine loading at pool.debian.org, instead of 5, soon 
to be 7. This machine has the power to be a server, so it now has a 
dhcpd server, specially configured to answer only one mac address, just 
to give an X-Max3 printer its hostname and net address.  I am also an 
ntp server, stratum 2, for the use of the rest of the machines on my 
local net. Yet each and every one has full net access.  With dd-wrt 
standing guard. I have only one registered address you can ping.  My 
original 20 gigabyte web page is down, left with the death of those 2 
seacrate 2T's in less than 30 days service about 2 days apart. But when 
it comes back it will be to support a woodworkers big bench vice I have 
designed, the screw is about 50mm by 500mm in hard maple, buttress 
thread, the reminder of it is printed in PETG for its resilience. 
Stronger grip than anything you can get on ebay. With one bigger 
printer, it takes about a day on the milling machine for the screw, but 
2+ weeks for the rest of the parts for a single screw.  That's why the 
push to build a (presently 3 bigger printers, was 4 till I lost the 
printheads umbilical cable on a creality e5-s1 and it is not a service 
part) farm.


Take care & stay well Max.

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

Re: Paquetes fuera de Distro

[Roberto José Blandino Cisneros]

El 20/1/24 a las 11:19, JA CM escribió:
Hace poco actualicé a Debian 12 y ahora me salta una actualización de 
VisualCode desde el propio programa, pero no desde los repositorios. 
No es que necesite actualizar de la 1.85.1 a la 1.85.2 pero me planteo 
la siguiente pregunta.
Si quisiera actualizar ese programa según la página del propio 
programa y sus propios lanzamientos ¿cómo podría hacerlo? ¿dpkg? ¿apt? 
Synaptic? ¿cómo afectaría eso a futuras actualizaciones del SO?
¿Seríais tan amables de facilitarme links para aprender acerca de las 
actualizaciones de paquetes fuera de las fuentes de la distribución y 
sus consecuencias?


Si son paquetes fuera de distro, sigue las indicaciones del autor del 
paquete. La actualización se hace fuera de distro, igual que el dbeaver, 
necesitas bajarlo desde su página oficial si usas el programa fuera de 
distro, si usas el compilado propio de la distro, tendrás que aguantar 
siempre el mensaje de que hay una nueva versión disponible.

Muchas gracias y un saludo


Saludos.

Re: Sistema sin acceso.

[Roberto José Blandino Cisneros]

El 14/1/24 a las 17:14, JavierDebian escribió:



El 14/1/24 a las 12:30, JA CM escribió:
Buenos días me encuentro ante un problema fruto de una actualización 
en un portátil, desde debian 8 a debian 12. Inicialmente no fue mal, 
pude arrancar pero no se actualizaron gran cantidad de paquetes, 
aunque sí el núcleo y arrancó bien.
Esta mañana he añadido al sources.list la opción non-free-firmware y 
he vuelto a actualizar con


|apt full-upgrade|

Durante el proceso me pide seleccionar un gestor de pantalla y le 
respondí gdm que era el que tenía, posteriormente salió del proceso 
con errores. Al reiniciar el sistema fue cuando se presentó el fatal 
problema: al arrancar el sistema gráfico parpadea entre una ventana 
negra y una ventana con la imagen del logo de NVIDIA, justo lo que 
hacía al cargar el gestor de ventanas, pero no llega a hacerlo. El 
caso es que intento cambiar con alt+2 por ejemplo a un arranque de 
consola y aunque cambia y parece preparado, al login no reconoce ni 
al usuario root ni al que uso habitualmente, es decir no me llega a 
pedir ni la contraseña.
Mi portátil tiene una tarjeta gráfica Geforce de la serie 300 que van 
con el driver nveau de nvidia y me da la sensación que ha metido los 
drivers para series mayores que trae Debian 12.
El caso es que no puedo acceder de ninguna manera. Tengo otros 
nucleos 3.x e incluso en recovery mode pero llego al mismo sitio.

Agradecería vuestros consejos y los links correspondientes en tal caso.

Un saludo y gracias por adelantado.



¿De 8 a 12?
Hay que esperar que explique como hizo ese salto tan grande XD. Yo he 
escalado desde la 7 a la 12 pero pasando por la 8, por la 9 por la 10 y 
por la 11 hasta llegar a la 12 y voy haciendo imágenes o respaldo en 
caso que algo se líe, pero nunca he usado los respaldos, pero el hecho 
que no existan presedentes no significa que no deba uno estar listo para 
revertir.


¿Así, sin anestesia?
¿En un sistema de entorno gráfico?

Para empezar a hablar, saltaste de init a systemd, así, a lo kamikaze.

Si claro de un panzazo, eso debe doler.


Mi humilde recomendación: Instalá el sistema desde cero.
Podría ser, pero si un "--fix-missing" lo arregla todo, basta que pruebe 
hacer el inicio en modo "single", al final al parecer solo es el driver 
de la tarjeta gráfica la que se ha liado.
La mitad de los directorios y archivos de configuración están y tienen 
formatos TOTALMENTE distintos.


Ya trae problemas actualizar de 10 a 12; es más, TODA la bibligrafía 
recomienda actualizar paso a paso.

Así es, muy de acuerdo. No hay que olvidar nunca el RTFM.


Saludos.

JAP

Re: Sistema sin acceso.

[Roberto José Blandino Cisneros]

El 14/1/24 a las 09:30, JA CM escribió:
Buenos días me encuentro ante un problema fruto de una actualización 
en un portátil, desde debian 8 a debian 12. Inicialmente no fue mal, 
pude arrancar pero no se actualizaron gran cantidad de paquetes, 
aunque sí el núcleo y arrancó bien.
Esta mañana he añadido al sources.list la opción non-free-firmware y 
he vuelto a actualizar con

|apt full-upgrade|


|Siempre toda actualización se debe realizar los tres pasos siguientes:
|

|    # apt update && apt upgrade -y && apt dist-upgrade -y|

|Nunca he tenido problema sin embargo si posees drivers o controladores 
compilados, cada vez que el kernel se actualice debes realizar la 
compilación para ese controlador, en este caso estas haciendo uso de los 
paquetes que vienen en el sistema.

|

Durante el proceso me pide seleccionar un gestor de pantalla y le 
respondí gdm que era el que tenía, posteriormente salió del proceso 
con errores. Al reiniciar el sistema fue cuando se presentó el fatal 
problema: al arrancar el sistema gráfico parpadea entre una ventana 
negra y una ventana con la imagen del logo de NVIDIA, justo lo que 
hacía al cargar el gestor de ventanas, pero no llega a hacerlo. El 
caso es que intento cambiar con alt+2 por ejemplo a un arranque de 
consola y aunque cambia y parece preparado, al login no reconoce ni al 
usuario root ni al que uso habitualmente, es decir no me llega a pedir 
ni la contraseña.
Mi portátil tiene una tarjeta gráfica Geforce de la serie 300 que van 
con el driver nveau de nvidia y me da la sensación que ha metido los 
drivers para series mayores que trae Debian 12.
El caso es que no puedo acceder de ninguna manera. Tengo otros nucleos 
3.x e incluso en recovery mode pero llego al mismo sitio.

Agradecería vuestros consejos y los links correspondientes en tal caso.

Mi consejo es que hagas arranque del sistema en modo "single-user" esto 
lo haces desde el grub:


    * Oprime "e"

    * Agrega "single" en la linea "ro quiet", modifica "ro" por "rw" 
para permitir la escritura


    * Oprime F10

    * En caso de ser necesario ejecuta "mount / -rw -o remount"

    * Luego prueba setear el modo multiusuario:

# systemctl set-default multi-user.target

Si te lo permite, reinicia y ahora no modifiques el grub deberias entrar 
solo en modo consola y prueba reparar lo dañado:


# apt upgrade --fix-missing

# dpkg --configure -a

# apt-get install -f

    * Luego prueba recompilar el controlador en modo "single" user

    * Prueba instalar el paquete "nvidia-detect"


Para restaurar y probar el controlador seteas nuevamente el ambiente 
gráfico:


# systemctl set-default graphical


Ahora bien, te recomiendo que revises bien los logs puede que tu sistema 
solo esté roto y funcione haciendo una instalación "--fix-missing" y si 
eso lo solventa no sigas probando más, en caso de no ser así sería 
probar compilar los controladores para tu tarjeta y así, avanza 
revisando tu caso, los pasos pueden variar, en mi caso siempre compilo 
los controladores para mi kernel por lo que en cada actualización cuando 
se me olvida ya se que debo entrar en modo single user para recompilar 
el controlador en el nuevo kernel y luego restaurar modo grafico ya que 
si no hago esto, el sistema sin el controlador compilado me da pantalla 
negra.




Un saludo y gracias por adelantado.


Saludos, espero soluciones el problema.

Re: Generar un fstab borrado por accidente

[Roberto José Blandino Cisneros]

El 5/1/24 a las 14:21, judedi sago escribió:

Buenas noches ...
Como Generar un fstab borrado por accidente.


Puedes sacarlo haciendo un cat al /etc/mtab

Re: Q: Gnome network odd

[David Wright]

On Tue 30 Jan 2024 at 07:05:55 (+), Tixy wrote:
> On Mon, 2024-01-29 at 23:49 -0600, David Wright wrote:
> > I would tend to think that:
> > 
> > . The debian-installer installs ifupdown by default when you don't
> >   install a Desktop Manager like Gnome,
> > 
> > . The debian-installer installs NetworkManager by default if you do
> >   install a Desktop Manager like Gnome,
> > 
> > . It shouldn't do both.
> > 
> 
> My experience, admittedly from a few releases ago, is that ifupdown is
> always installed but that the installer doesn't populate it's config
> files with the found network interfaces, only the loopback interface.

AIUI that would be normal behaviour when the DE installs its own
choice of package to handle the network.

But it's also what happens when you install over wifi and don't
select a DE: the wifi configuration is removed as the last step
in the installation process. It's a (mis)feature/bug that's been
discussed for years.

> I also have a more vague memory that you could put config into
> /etc/network/interfaces then in some circumstance NetworkManager would
> not try and manage that interface, and in others it would take over.
> (Perhaps selected by allow hotplug option in the ifupdown config?)

That seems unlikely. Perhaps you're thinking of NM's ifupdown plugin
that allows you to use the configuration in /e/n/i. I'm assuming the
OP has not installed that in their sleep. Max's request for printing
the configuration could confirm that.

Cheers,
David.

Re: chrony date months off

[Max Nikulin]

On 31/01/2024 20:24, didar wrote:

On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:

How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate command that would do that.


You can use "rdate" (openrdate) as quick fix like `ntpdate'.
Is there a real reason to install an extra package if chrony provides a 
tool similar to ntpdate?


If I recall it right, the reason why chrony appeared here was just

$ man timesyncd
No manual entry for timesyncd

If it is that box with armbian modified by a Chinese 3d printer vendor 
then I am surprised that, intended for boards without RTC, it does not 
have proper NTP setup out of the box. Despite I expect arbitrary 
peculiarities in this kind of a Linux distribution, I still believe that 
NTP troubles were caused by user actions.

Re: Probelms with apparmor

[Gareth Evans]

On Wed 31/01/2024 at 23:04, Gareth Evans  wrote:
> On Wed 31/01/2024 at 22:11, Steven Truppe  wrote:
>> Hey,
>>
>>
>> i've the follwoing trouble: when i try to run certain apps it takes
>> forever tostart. i can get rid of the troble by typing $service apparmor
>> reload but that's not a partmanent soutoin.
>>
>> can someone pleae help me out here ?
>>
>>
>> best regards!
>
> I accidentally replied to the OP, rather than the list, with the below:
>
> Which apps?  
>
> Is there any relevant output at the point at which a delay occurs, and 
> perhaps just afterwards, if you start an affected program from the 
> terminal?
>
> I wonder if aa-complain may be of use to you, but first things first...
>
> Thanks,
> Gareth

Also, anything relevant in /var/log/syslog or 

# journalctl --system ?

G

Re: Probelms with apparmor

[Gareth Evans]

On Wed 31/01/2024 at 22:11, Steven Truppe  wrote:
> Hey,
>
>
> i've the follwoing trouble: when i try to run certain apps it takes
> forever tostart. i can get rid of the troble by typing $service apparmor
> reload but that's not a partmanent soutoin.
>
> can someone pleae help me out here ?
>
>
> best regards!

I accidentally replied to the OP, rather than the list, with the below:

Which apps?  

Is there any relevant output at the point at which a delay occurs, and perhaps 
just afterwards, if you start an affected program from the terminal?

I wonder if aa-complain may be of use to you, but first things first...

Thanks,
Gareth

Re: Automatically installing GRUB on multiple drives

[hw]

On Wed, 2024-01-31 at 06:33 +0100, to...@tuxteam.de wrote:
> On Tue, Jan 30, 2024 at 09:47:35PM +0100, hw wrote:
> > On Mon, 2024-01-29 at 18:41 +0100, to...@tuxteam.de wrote:
> > > On Mon, Jan 29, 2024 at 05:52:38PM +0100, hw wrote:
> > > 
> > > [...]
> > > 
> > > > Ok in that case, hardware RAID is a requirement for machines with UEFI
> > > > BIOS since otherwise their reliability is insufficient.
> > > 
> > > The price you pay for hardware RAID is that you need a compatible 
> > > controller
> > > if you take your disks elsewhere (e.g. because your controller dies).
> > 
> > How often do you take the system disks from one machine to another,
> > and how often will the RAID controller fail?
> > 
> > > With (Linux) software RAID you just need another Linux...
> > 
> > How's that supposed to help?  The machine still won't boot if the disk
> > with the UEFI partition has failed.
> 
> We are talking about getting out of a catastrophic event. In such cases,
> booting is the smallest of problems: use your favourite rescue medium
> with a kernel which understands your RAID (and possibly other details
> of your storage setup, file systems, LUKS, whatever).

Try to do that with a remote machine.

> [...]
> 
> > Maybe the problem needs to be fixed in all the UEFI BIOSs.  I don't
> > think it'll happen, though.
> 
> This still makes sense if you want a hands-off recovery (think data
> centre far away). Still you won't recover from a broken motherboard.

It would make sense that all the UEFI BIOSs would be fixed so that
they do not create this problem in the first place like they
shouldn't.

You seem to forget the point that one reason for using redundant
storage, like some kind of RAID, to boot from, is that I don't want to
have booting issues, especially not with remote machines.

Unfortunately UEFI BIOSs make that difficult unless you use hardware
raid.

And I don't want to have that problem with local machines either
because it's a really nasty problem.  How do you even restore the UEFI
partition when the disk it's on has failed and you don't have a copy?

Re: Automatically installing GRUB on multiple drives

[Nicolas George]

hw (12024-01-31):
> Well, I doubt it.

Well, doubt it all you want. In the meantime, we will continue to use
it.

Did not read the rest, not interested in red herring nightmare
scenarios.

-- 
  Nicolas George

Probelms with apparmor

[Steven Truppe]

    Hey,


i've the follwoing trouble: when i try to run certain apps it takes
forever tostart. i can get rid of the troble by typing $service apparmor
reload but that's not a partmanent soutoin.

can someone pleae help me out here ?


best regards!

Re: Automatically installing GRUB on multiple drives

[hw]

On Tue, 2024-01-30 at 21:35 +0100, Nicolas George wrote:
> hw (12024-01-30):
> > Yes, and how much effort and how reliable is doing that?
> 
> Very little effort and probably more reliable than hardware RAID with
> closed-source hardware.

Well, I doubt it.  After all you need to copy a whole partition and
must make sure that it doesn't fail through distribution upgrades and
all kinds of possible changes and even when someone shuts down or
reboots the computer or pulls the plug while the copying is still in
progress.  You also must make sure that the boot manager is installed
on multiple disks.

And when you're going to do it?  When shutting the machine down?
Might not happen and when it does happen, maybe you don't want to wait
on it.

When rebooting it?  Perhaps you don't want to overwrite the copy at
that time, or perhaps it's too late then because there were software
updates before you rebooted and one of the disks failed when
rebooting.

Do you suggest to install backup batteries or capacitors to keep the
machine running until the copying process has completed when the power
goes out?

Or do you want to do it all manually at a time convenient for you?
What if you forgot to do it?


I'm not so silly that you could convince me that you can do it more
reliably than the hardware RAID does it whith a bunch of scripts you
put together yourself, especially not by implying that the hardware
raid which has been tested in many datacenters with who knows how many
hundreds of thousands of machines over many years uses closed source
software which has been maintained and therefore must be unreliable.

The lowest listed MTBF of hardware RAID is over 26 hours
(i. e. about 30 years) on [1].  Can you show that you can do it more
reliably with your bunch of scripts?


[1]: 
https://www.intel.com/content/www/us/en/support/articles/07641/server-products/sasraid.html

Re: Debian/Xen on ARM: How to identify source of an unhandled SMC call during boot?

[Tixy]

On Wed, 2024-01-31 at 21:59 +0100, hw wrote:
> On Wed, 2024-01-31 at 08:02 +0100, Paul Leiber wrote:
> > Am 25.01.2024 um 22:28 schrieb Paul Leiber:
> > [...]
> > > Some people on xen-devel pointed out to me two unhandled SMC calls in 
> > > the boot logs which could be the root of the problem. I am now trying to 
> > > find out where these calls come from to get closer to the root cause. 
> > > The suspected calls are the following ones:
> > > 
> > > (XEN) d0v0 Unhandled SMC/HVC: 0x8450
> > > (XEN) d0v0 Unhandled SMC/HVC: 0x8600ff01
> > > 
> > > These calls happen during the Dom0 boot process, so it's something from 
> > > inside Linux and nothing Xen related, I've been told. The current 
> > > working hypothesis is that the calls are trying to find some module not 
> > > emulated by Xen and are therefore failing, leading to Linux waiting for 
> > > the reply, and subsequently to the Xen watchdog triggering and rebooting.
> > > 
> > >  From what I could find out in ARM documentation, the unhandled SMC 
> > > calls probably have the following purpose:
> > > 
> > > 0x8450 = TRNG_VERSION, returns the implemented TRNG (True Random 
> > > Number Generator) ABI version [2]
> > > 0x8600ff01 = Call UID Query for Vendor Specific Hypervisor Service, 
> > > Returns a unique identifier of the service provider [3]
> > > 
> > > The more likely cause is the second call to the address 0x8600ff01.
> > > 
> > > Now I simply have no idea how to find out where in the Linux boot 
> > > process these calls are made. I tried poking into the Linux sources a 
> > > bit, and I couldn't find an exact match for these call addresses, so I 
> > > assume these addresses are assembled from different parts. There are 
> > > some matches for "0x8600" and for "ff01", but I couldn't identify if 
> > > these matches are relevant.
> > > 
> > > I tried to find out if strace could help, but from what I understand, 
> > > this is related to commands coming from userspace, so I am not sure that 
> > > strace helps during the boot process.
> > > 
> > > I'd appreciate it if somebody more knowledgeable would point me in the 
> > > right direction. If more information is needed, I can provide it.
> 
> I would search for the message 'Unhandled SMC/HVC' itself, or even for
> 'Unhandled', not for the address.  The address is probably determined
> at runtime and not hardcoded.

I sure those hex values aren't 'addresses' but the ID's for the secure
monitor calls Paul already identified.

Looking at the Linux sources I found the header for constructing these
monitor calls: include/linux/arm-smccc.h

So it might be worth looking at the files that include that. There are
various drivers for firmware, and a watchdog driver amongst other
things... drivers/watchdog/arm_smc_wdt.c

-- 
Tixy

Re: Debian/Xen on ARM: How to identify source of an unhandled SMC call during boot?

[Paul Leiber]

Am 31.01.2024 um 19:07 schrieb Andrew M.A. Cater:

On Wed, Jan 31, 2024 at 08:02:47AM +0100, Paul Leiber wrote:

Am 25.01.2024 um 22:28 schrieb Paul Leiber:


Paul

[1]
https://lists.xenproject.org/archives/html/xen-devel/2023-10/msg00796.html
[2] https://developer.arm.com/documentation/den0098/latest/
[3] https://documentation-service.arm.com/static/628b755ce3c4322a76af56de?token=



Hm, no reply so far. Is this maybe the wrong list? Should I post this rather
somewhere else?

Paul



debian-arm / OFTC IRC #debian-arm or #debian-raspberrypi

Xen in Debian is team maintained, I think, but many people have moved
away from Xen in favour of other virtualisation/paravirtualisation
solutions and containers.

All the very best, as ever,

Andy
(amaca...@debian.org)


Thank you for the reply, Andy. I'll try my luck there.

Paul

Re: Automatically installing GRUB on multiple drives

[hw]

On Wed, 2024-01-31 at 15:16 +, Andy Smith wrote:
> Hi,
> 
> On Tue, Jan 30, 2024 at 09:50:23PM +0100, hw wrote:
> > On Mon, 2024-01-29 at 23:53 +, Andy Smith wrote:
> > > I think you should read it again until you find the part where it
> > > clearly states what the problem is with using MD RAID for this. If
> > > you still can't find that part, there is likely to be a problem I
> > > can't assist with.
> > 
> > That there may be a problem doesn't automatically mean that you need a
> > bunch of scripts.
> 
> This is getting quite tedious.
> 
> Multiple people have said that there is a concern that UEFI firmware
> might write to an ESP, which would invalidate the use of software
> RAID for the ESP.
> 
> Multiple people have suggested instead syncing ESP partitions in
> userland. If you're going to do that then you'll need a script to do
> it.
> 
> I don't understand what you find so difficult to grasp about this.

You kept only saying 'read the link'.  Well, read the link!  It points
out 4 choices and none of them says 'you need a bunch of scripts'.

> If it's that you have some other proposal for solving this, it would
> be helpful for you to say so

I already said my solution is using hardware raid or fixing the
problem in all the UEFI BIOSs.

I'd also say that the BIOS must never write to the storage, be it to
an UEFI partition or anywhere else.  But that's a different topic.

> [...]
> If your suggested solution is "use hardware RAID", no need to repeat
> that one though: I see you said it in a few other messages, and that
> suggestions has been received. Assume the conversation continues
> amongst people who don't like that suggestion.

Well, too late, I already said it again since you asked.  Do you have
a better solution?  It's ok not to like this solution, but do you have
a better one?

> Otherwise, I don't think anyone knows what you have spent several
> messages trying to say. All we got was, "you don't need scripts".

What do you expect when you keep repeating 'read the link'.

Re: chrony date months off

[Steve McIntyre]

Darac Marjal  wrote:
>
>The script works like this: if the root device is specified on the 
>kernel command line AND the word "fixrtc" is  specified, then get the 
>time that the root file system was last mounted. The script then uses 
>"date" to set the clock to that date stamp.
>
>I assume that the idea is that, rather than having the clock start at 
>1970, it's better to start it at, say, yesterday. You've still got quite 
>a lot of slewing to do if you connect to NTP, but at least there's a 
>chance that you can verify certificates etc.

I also wrote fake-hwclock (packaged in Debian) for this kind of reason.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...

Re: chrony date months off

[hw]

On Wed, 2024-01-31 at 12:56 -0500, gene heskett wrote:
> [...]
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: No suitable source for initstepslew
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec 30 03:15:44 bpi51e5p systemd[1]: chrony.service: New main PID 1936 
> does not exist or is a zombie.
> Dec 30 03:15:44 bpi51e5p systemd[1]: chrony.service: Failed with result 
> 'protocol'.

Perhaps uncomment one/some of the pool address(es) in its config to
allow chrony to find a suitable server.

Re: Can't list root directory

[hw]

On Wed, 2024-01-31 at 09:27 -0500, Gary Dale wrote:
> On 2024-01-30 15:54, hw wrote:
> > On Mon, 2024-01-29 at 11:42 -0500, Gary Dale wrote:
> > > I'm running Debian/Trixie on an AMD64 workstation. I've lost the ability
> > > to see the root directory even when I am logged in as root (su -).
> > > 
> > > This has been happening intermittently for several months. I initially
> > > thought it might be related to failing NVME drive that was part of a
> > > RAID1 array that is mounted as "/" but I replaced the device and the
> > > problem is still happening.
> > > [...]
> > What happens when you put the device you replaced back?
> > 
> How could putting a known-failing device back in help? The problem 
> existed before I replaced it and continues to exist after the replacement.

It sounded like you were able to list the root directory (at least
sometimes) before you did the replacement.  Manually failing the
device (perhaps after adding it back first) could make a difference.

I've seen such indefinite hangs only when an NFS share has become
unreachable after it had been mounted.  You could use clonezilla to
make a copy and then perhaps convert the file system to btrfs.

Do you still have the problem when you remove one of the NVME storage
things?  Perhaps you have the equivivalent of a bad SATA cable or the
mainboard doesn't like it when you access two of those at the same
time, or something like that.  Even simple network cables can behave
very strangely, and NVME may be a bit more complicated than that.

Running fsck on every boot to work around an issue like this is
certainly a bad idea.  Doesn't fsck report anything?  If it really
makes a difference in itself rather than creating some side effect
that leads to the root directory being readable, it should report
something.  Perhaps you need to increase its verbosity.

If there's no report then it would look like a side effect and raise
the question what side effect it might be.  Does fsck run before the
RAID has been brought up or after?  Is the RAID up when booting is
completed?  What does mdadm say about the device(s)?  Can you still
list the root directory when you manually fail either drive?  What
exactly are the circumstances under which you can and not list the
root directory?

You need to do some investigating and ask questions like those ...

SOLVED:Re: chrony date months off

[gene heskett]

On 1/31/24 13:19, Greg Wooledge wrote:

On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]

# Stop bad estimates upsetting machine clock.
maxupdateskew 10.0
initstepslew 30 192.168.71.3
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can’t be used along with the 'rtcfile'
directive.
rtcsync


I'll comment that line

# Step the system clock instead of slewing it if the adjustment is larger
than
# one second, but only in the first three clock updates.
makestep 1 3000
I had tried 30, and it did it about that many time ack the tcpdump log 
I'm tracking.  And I'll put the 300 back in, that ack the tcpdump 
monitor seemed to effective. but I've not found in the docs, anything 
that will modify how far the step will change it, The first arg is one 
second.


chrony seems to  be the fave method for the arm64's but I have had 
better luck using ntpsec without the security on all other wintel 
machines.  Its ntpsec I'm using on this machine to be a stratum 2 server 
for the rest of my local net.  So that's what all the other local 
machines see.  timedatectl bombs when asked to set-time, regardless of 
how many space separated arguments is says too many arguments. Aha! the 
time argument needs single quotes around it!  The help screen is wrong 
but the man page says " ".  So I have it now set for about 4 hours ago.
Now about 5 seconds off, but its not querying my server.  More man page 
perusal. I am getting the impression that timedatctl ultimately uses he 
first time service it can find, and while I have the clock sey pretty 
close, it nat offer ntp until there is an available ntp client, and I 
used apt to purge both chrony and ntpsec. So I;ll reinstall ntpsec. Done


Then I went clear around the mulberry tree and copied (because my sshnet 
mounts of all these machine is as a user) the 
/sshnet/go704/etc/ntpsec/ntp.conf to my home dir on that box, then fired 
up a user mc and copied that file from /sshnet/go704/home/gene to 
/sshnet/bpi51/home/gene.
went to a different workspace, fired up a sudo mc, copied that file to 
that machines /etc/ntpsec dir, then fixed the perms back to 0600.


Then restarted ntpsec by stopping it, then starting it again so it would 
read the new file. Then:


gene@bpi51e5p:~$ timedatectl status
   Local time: Wed 2024-01-31 15:40:13 EST
   Universal time: Wed 2024-01-31 20:40:13 UTC
 RTC time: Wed 2024-01-31 20:40:13
Time zone: America/New_York (EST, -0500)
System clock synchronized: yes
  NTP service: n/a
  RTC in local TZ: no

And my tcpdump trace here?:
15:51:01.235371 IP bpi51e5p.coyote.den.ntp > coyote.coyote.den.ntp: 
NTPv4, Client, length 48
15:51:01.235523 IP coyote.coyote.den.ntp > bpi51e5p.coyote.den.ntp: 
NTPv4, Server, length 48
15:52:06.236633 IP bpi51e5p.coyote.den.ntp > coyote.coyote.den.ntp: 
NTPv4, Client, length 48
15:52:06.236701 IP coyote.coyote.den.ntp > bpi51e5p.coyote.den.ntp: 
NTPv4, Server, length 48


IOW, its working.  And I found another off by about an hour, so I copied 
that same file it it, problem solved.


Now, I still have more cats to skin but solving those two problems will 
help.  Now I can get back to the real problem. Lack of docs to make a 
TMC-2209, a very common motor driver in the stepstick category, work in 
the uart interface mode in a BTT octopus Pro controller cards driver 
sockets 2, 3 & 4.  Add about 12 jumpers and put them back in 
step/dir/enable mode is the next test. That's going to take some coffee 
I haven't made yet today.


Thanks for the nudge to make me think, Greg, take care & stay well.

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

Re: Debian/Xen on ARM: How to identify source of an unhandled SMC call during boot?

[hw]

On Wed, 2024-01-31 at 08:02 +0100, Paul Leiber wrote:
> Am 25.01.2024 um 22:28 schrieb Paul Leiber:
> > Dear Debian user list members,
> > 
> > I am trying to run network related stuff (Samba, Zabbix) on a Raspberry 
> > Pi 4B in a virtualized environment using Debian Bookworm and Xen. I am 
> > running into reproducible complete system crashes/reboots due to a Xen 
> > watchdog triggering under certain, seemingly strange conditions (the 

Raspberry Pis have a watchdog?

Maybe disable the watchdog and see what happens?

> > number of VLANs involved seems to play a role, running tcpdump on 
> > certain interfaces prevents this issue, ...). If you are interested in 
> > the long version, you can find it here [1].
> > 
> > Some people on xen-devel pointed out to me two unhandled SMC calls in 
> > the boot logs which could be the root of the problem. I am now trying to 
> > find out where these calls come from to get closer to the root cause. 
> > The suspected calls are the following ones:
> > 
> > (XEN) d0v0 Unhandled SMC/HVC: 0x8450
> > (XEN) d0v0 Unhandled SMC/HVC: 0x8600ff01
> > 
> > These calls happen during the Dom0 boot process, so it's something from 
> > inside Linux and nothing Xen related, I've been told. The current 
> > working hypothesis is that the calls are trying to find some module not 
> > emulated by Xen and are therefore failing, leading to Linux waiting for 
> > the reply, and subsequently to the Xen watchdog triggering and rebooting.
> > 
> >  From what I could find out in ARM documentation, the unhandled SMC 
> > calls probably have the following purpose:
> > 
> > 0x8450 = TRNG_VERSION, returns the implemented TRNG (True Random 
> > Number Generator) ABI version [2]
> > 0x8600ff01 = Call UID Query for Vendor Specific Hypervisor Service, 
> > Returns a unique identifier of the service provider [3]
> > 
> > The more likely cause is the second call to the address 0x8600ff01.
> > 
> > Now I simply have no idea how to find out where in the Linux boot 
> > process these calls are made. I tried poking into the Linux sources a 
> > bit, and I couldn't find an exact match for these call addresses, so I 
> > assume these addresses are assembled from different parts. There are 
> > some matches for "0x8600" and for "ff01", but I couldn't identify if 
> > these matches are relevant.
> > 
> > I tried to find out if strace could help, but from what I understand, 
> > this is related to commands coming from userspace, so I am not sure that 
> > strace helps during the boot process.
> > 
> > I'd appreciate it if somebody more knowledgeable would point me in the 
> > right direction. If more information is needed, I can provide it.

I would search for the message 'Unhandled SMC/HVC' itself, or even for
'Unhandled', not for the address.  The address is probably determined
at runtime and not hardcoded.

Do you get better results with qemu/kvm?  Xen is more like 'hmm' than
anything else.

problèmes de copie sur un montage smb, crash kernel

[testeur]

Bonjour,
J'ai un problème pour faire une copie simple de fichiers (cp hosts 
hosts.txt) au sein d'un partage SMB (monté par autofs). ça m'indique 
"Processus arrêté", puis après un nouvel essai ça reste bloqué/freezé, 
je n'ai plus la main sur la console (ctl+C, D, Z n'ont aucune action). 
Quand je créé un fichier, pas de souci, quand j'édite un fichier pas de 
souci, le seul problème est de copier. La suppression ni le 
renommage/déplacement n'est problématique. le processus est indiqué 
ainsi : xxx 25304 24752 0 21:35 pts/2 00:00:00 cp hosts hosts.txt le 
kill du processus ne fonctionne pas. Les droits sur les fichiers : 
-rwxr-xr-x 1 xxx yyy 0 31 janv. 21:34 hosts.txt -rwxr-xr-x 1 xxx yyy 0 
28 janv. 18:13 hosts voici les droits du montage : ├─/mnt/xxx 
/etc/autoxxx.smb autofs 
rw,relatime,fd=12,pgrp=1561,timeout=30,minproto=5,maxproto=5,indirect,pipe_ino=22915 
│ └─/mnt/xxx/conf //xx.xx.xx.xx/xxx/conf cifs 
rw,relatime,vers=3.1.1,cache=strict,username=xxx,uid=1000,noforceuid,gid=1000,noforcegid,addr=xx.xx.xx.xx,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1 
le noyau actuel de debian 12 : Linux vfpm 6.1.0-17-amd64 #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux


Dans syslog, j'obtiens des erreurs au niveau du kernel.

2024-01-29T21:20:24.524146+01:00 vfpm kernel: [ 7967.200355] BUG: kernel 
NULL pointer dereference, address: 
2024-01-29T21:20:24.524163+01:00 vfpm kernel: [ 7967.200364] #PF: 
supervisor read access in kernel mode
2024-01-29T21:20:24.524167+01:00 vfpm kernel: [ 7967.200367] #PF: 
error_code(0x) - not-present page

2024-01-29T21:20:24.524167+01:00 vfpm kernel: [ 7967.200370] PGD 0 P4D 0
2024-01-29T21:20:24.524168+01:00 vfpm kernel: [ 7967.200374] Oops:  
[#1] PREEMPT SMP PTI
2024-01-29T21:20:24.524169+01:00 vfpm kernel: [ 7967.200378] CPU: 7 PID: 
9346 Comm: cp Tainted: P  IOE  6.1.0-17-amd64 #1  Debian 
6.1.69-1
2024-01-29T21:20:24.524170+01:00 vfpm kernel: [ 7967.200383] Hardware 
name: Hewlett-Packard HP Z400 Workstation/0B4Ch, BIOS 786G3 v03.15 
10/29/2010
2024-01-29T21:20:24.524171+01:00 vfpm kernel: [ 7967.200385] RIP: 
0010:cifs_flush_folio+0x3f/0x100 [cifs]
2024-01-29T21:20:24.524172+01:00 vfpm kernel: [ 7967.200471] Code: d2 41 
54 49 89 cc 31 c9 55 48 89 f5 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 e8 
8d 8a 49 c8 48 3d 00 f0 ff ff 0f 87 a5 00 00 00 <48> 8b 10 48 89 c3 b8 
00 10 00 00 f7 c2 00 00 01 00 74 07 0f b6 4b
2024-01-29T21:20:24.524173+01:00 vfpm kernel: [ 7967.200475] RSP: 
0018:a454888d7c98 EFLAGS: 00010207
2024-01-29T21:20:24.524175+01:00 vfpm kernel: [ 7967.200478] RAX: 
 RBX:  RCX: 
2024-01-29T21:20:24.524188+01:00 vfpm kernel: [ 7967.200481] RDX: 
 RSI:  RDI: 98c949229840
2024-01-29T21:20:24.524190+01:00 vfpm kernel: [ 7967.200483] RBP: 
 R08: 0001 R09: 
2024-01-29T21:20:24.524191+01:00 vfpm kernel: [ 7967.200485] R10: 
 R11:  R12: a454888d7d08
2024-01-29T21:20:24.524192+01:00 vfpm kernel: [ 7967.200487] R13: 
a454888d7d00 R14: 98ca472d3228 R15: 0001
2024-01-29T21:20:24.524193+01:00 vfpm kernel: [ 7967.200490] FS: 
7f69d9003500() GS:98cad7bc() knlGS:
2024-01-29T21:20:24.524194+01:00 vfpm kernel: [ 7967.200493] CS: 0010 
DS:  ES:  CR0: 80050033
2024-01-29T21:20:24.524195+01:00 vfpm kernel: [ 7967.200496] CR2: 
 CR3: 000104be6000 CR4: 06e0

2024-01-29T21:20:24.524196+01:00 vfpm kernel: [ 7967.200498] Call Trace:
2024-01-29T21:20:24.524197+01:00 vfpm kernel: [ 7967.200502] 
2024-01-29T21:20:24.524198+01:00 vfpm kernel: [ 7967.200506]  ? 
__die_body.cold+0x1a/0x1f
2024-01-29T21:20:24.524200+01:00 vfpm kernel: [ 7967.200515]  ? 
page_fault_oops+0xd2/0x2b0
2024-01-29T21:20:24.524201+01:00 vfpm kernel: [ 7967.200524]  ? 
exc_page_fault+0x70/0x170
2024-01-29T21:20:24.524202+01:00 vfpm kernel: [ 7967.200531]  ? 
asm_exc_page_fault+0x22/0x30
2024-01-29T21:20:24.524202+01:00 vfpm kernel: [ 7967.200541]  ? 
cifs_flush_folio+0x3f/0x100 [cifs]
2024-01-29T21:20:24.524203+01:00 vfpm kernel: [ 7967.200607]  ? 
cifs_flush_folio+0x33/0x100 [cifs]
2024-01-29T21:20:24.524204+01:00 vfpm kernel: [ 7967.200662] 
cifs_remap_file_range+0x16d/0x680 [cifs]
2024-01-29T21:20:24.524205+01:00 vfpm kernel: [ 7967.200743] 
do_clone_file_range+0xe9/0x230
2024-01-29T21:20:24.524206+01:00 vfpm kernel: [ 7967.200751] 
vfs_clone_file_range+0x37/0x140
2024-01-29T21:20:24.524207+01:00 vfpm kernel: [ 7967.200756] 
ioctl_file_clone+0x49/0xb0
2024-01-29T21:20:24.524208+01:00 vfpm kernel: [ 7967.200763] 
do_vfs_ioctl+0x77/0x910
2024-01-29T21:20:24.524208+01:00 vfpm kernel: [ 7967.200769] 
__x64_sys_ioctl+0x6e/0xd0
2024-01-29T21:20:24.524209+01:00 vfpm kernel: [ 7967.200775] 

Re: AW: AW: su su- sudo dont work

[Andrew M.A. Cater]

On Wed, Jan 31, 2024 at 01:58:41PM +, Schwibinger Michael wrote:
> Good afternoon
> I think
> maybe Im sure
> it is because of rescue mode.
> 
Hi Sophie,

Once again: we need to you to show us what commands you run.

We need to see error messages.

if you cannot run sudo or su, we need you to run the id command
as previously suggested.

We have literally nothing of use from you to help any of us problem
solve. This is throwing good effort away in persuading you to help us.

Also - please address requests first to the list and not to individuals -
it makes it a lot easier to follow on the list.

> Normal booting did not have this problem.
> 
> Anybody familiar with panic?
> 
> Regards
> Thank You
> Sophie
> 
Andy
> 
> 
> Von: Andrew M.A. Cater 
> Gesendet: Donnerstag, 25. Januar 2024 18:40
> An: debian-user@lists.debian.org 
> Betreff: Re: AW: su su- sudo dont work
> 
> On Thu, Jan 25, 2024 at 03:53:10PM +, Schwibinger Michael wrote:
> > Good afternoon
> > Why do I have to open a group?
> >
> 
> This is to *tell* us information about why you're having problems with su
> and sudo
> 
> Running the
> 
> id
> 
> command should give you information like
> 
> uid=1000(amacater) gid=1000(amacater) groups=1000(amacater),27(sudo)
> 
> which shows you that my user - amacater - is the first user on the
> machine (because Debian starts user id numbers at 1000 for ordinary
> users) and that I'm a member of group sudo - so can use sudo instead of su.
> 
> /etc/sudoers will show you what privileges the sudo user has.
> Here are the last lines of the file on my machine (which has not been
> modified from Debian defaults)
> 
> # User privilege specification
> rootALL=(ALL:ALL) ALL
> 
> # Allow members of group sudo to execute any command
> %sudo   ALL=(ALL:ALL) ALL
> 
> # See sudoers(5) for more information on "@include" directives:
> 
> @includedir /etc/sudoers.d
> (END)
> 
> If you are _not_ a user of group sudo for whatever reason - and want to
> use sudo - then you will need root privileges and the root password
> (once) to add your user name to the group.
> 
> For example: adduser sophie sudo
> 
> I hope this helps
> 
> > 2 years ago
> > sudo was no problem.
> >
> 
> As yet, we have *no idea* what you have done in the last two years to
> break your Debian system - or even to know which kernel you boot or
> how you "rescue" your system when you log onto it every day.
> 
> Please give us information in order that the readers on this list can
> use their knowledge to help you.
> 
> With every good wish, as ever,
> 
> Andy
> (amaca...@debian.org)
> > Regards
> >
> > Sophie
> >
> > Thank You
> > 
> > Von: Timothy M Butterworth 
> > Gesendet: Montag, 22. Januar 2024 00:07
> > An: Schwibinger Michael 
> > Cc: Greg Wooledge ; debian-user@lists.debian.org 
> > 
> > Betreff: Re: su su- sudo dont work
> >
> >
> >
> > On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
> > mailto:h...@hotmail.com>> wrote:
> > Thank You
> > Example
> > I say
> >
> > sudo apt-get install firefox
> > Reaction LINUX
> > This is not allowed we send a message to the admin.
> >
> > This error message means that your account is not in the sudo group.
> >
> > Run the command "groups" and look for the group sudo.
> > groups
> >
> > Here is the command to add a user account to the sudo group. You will need 
> > to run it as root.
> > usermod -a -G sudo 
> >
> > I do open root terminal
> > there its working.
> > Regards
> > Sophie
> >
> > 
> > Von: Greg Wooledge mailto:g...@wooledge.org>>
> > Gesendet: Samstag, 20. Januar 2024 14:14
> > An: debian-user@lists.debian.org 
> > mailto:debian-user@lists.debian.org>>
> > Betreff: Re: su su- sudo dont work
> >
> > On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > > Good afternoon.
> > > Root terminal is fine.
> > > What do I do wrong?
> > > What did I destroy?
> > >
> > > PC does have only one user=admin.
> > >
> > > Regards Sophie
> > > Is it the rescue mode?
> >
> > Explain, please.
> >
> > Your Subject: header says "su su- sudo dont work".  What does this MEAN?
> >
> > Please show us your attempts to USE each of these commands, and the
> > results that you got.  This means, run the commands in a terminal
> > window, and then PASTE the contents of that terminal window into the
> > body of your next email.  Show us the shell prompt, the command as you
> > typed it, and the full output.
> >
> > In other words, show us WHAT IS WRONG, or at least what appears wrong.
> >
> > In addition, please give basic background information -- what version
> > of Debian you are running, what desktop environment if any, how you
> > logged in (*especially* if it isn't just a "standard graphical login
> > for your desktop environment"), and anything else you can think of
> > that might be relevant.
> >
> > How does "rescue mode" factor into the problem?
> >
> > When 

Cifrado de disco sin contraseña

[Josu Lazkano]

Buenas,

Llevo tiempo cifrando las particiones de Debian mediante LUKS, funciona muy
bien. Pide una contraseña en el arranque y se accede al sistema.

Pero he visto que en algunos entornos corporativos, los equipos Windows se
pueden cifrar con Bitlocker y no pide contraseña, se descifra al hacer un
login correcto en dominio.

¿Sabeis si es posible hacer algo parecido en Debian? Que el disco esté
cifrado y al hacer un login válido se descifre?

Se agradece cualquier sugerencia o comentario.

Un saludo.

-- 
Josu Lazkano

Re: chrony date months off

[Darac Marjal]

On 31/01/2024 12:12, Max Nikulin wrote:

On 31/01/2024 17:54, to...@tuxteam.de wrote:

I think you want "maxstep". It's in the man page chrony.conf(5).

But if the time is "months off" perhaps you've got another problem
to fix first?


I think, the problem is no RTC on some *pi board, certainly chrony out 
of box setup is not ready to such environment and its solution is not 
maxstep.


Gene, are you going to complain again that some package has no man pages?

For Raspberry Pi's, Ubuntu offer a script similar to the following 
https://github.com/Jolicloud/initramfs-tools/blob/master/scripts/local-premount/fixrtc 
(I couldn't find an equivalent to https://sources.debian.net for Ubuntu, 
but the script is simple enough that I doubt if it's very different).


The script works like this: if the root device is specified on the 
kernel command line AND the word "fixrtc" is  specified, then get the 
time that the root file system was last mounted. The script then uses 
"date" to set the clock to that date stamp.


I assume that the idea is that, rather than having the clock start at 
1970, it's better to start it at, say, yesterday. You've still got quite 
a lot of slewing to do if you connect to NTP, but at least there's a 
chance that you can verify certificates etc.




OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: chrony date months off

[Greg Wooledge]

On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]
> # Stop bad estimates upsetting machine clock.
> maxupdateskew 10.0
> initstepslew 30 192.168.71.3
> # This directive enables kernel synchronisation (every 11 minutes) of the
> # real-time clock. Note that it can’t be used along with the 'rtcfile'
> directive.
> rtcsync
> 
> # Step the system clock instead of slewing it if the adjustment is larger
> than
> # one second, but only in the first three clock updates.
> makestep 1 3000

I've never used chrony, so all I know about it is what I've gleaned
from skimming the chrony.conf page, from Google search results, and
from things that people have said here.

With that in mind, I don't know what happens if you've got both
initstepslew *and* makestep in the same conf file.  I would imagine
you only want one of them.

> Dec 30 03:15:32 bpi51e5p chronyd[1936]: Using right/UTC timezone to obtain
> leap second data
> Dec 30 03:15:32 bpi51e5p chronyd[1936]: Loaded seccomp filter (level 1)
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: No suitable source for initstepslew
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3

That IP address clearly came from your initstepslew line.  Is there an
NTP service running on that host?  If so, is it synchronized?  And does
it permit client requests (from bpi51e5p)?

> Dec 30 03:15:44 bpi51e5p systemd[1]: chrony.service: New main PID 1936 does
> not exist or is a zombie.
> Dec 30 03:15:44 bpi51e5p systemd[1]: chrony.service: Failed with result
> 'protocol'.
> Dec 30 03:15:44 bpi51e5p systemd[1]: Failed to start chrony, an NTP
> client/server.

This appears to be important.  It's failing to start, which means it's
not setting the clock, or doing anything else.  You'll need to figure
out why it's not starting.  Perhaps it's *just* the fact that it can't
contact an NTP service at 192.168.71.3.  Or maybe there's more to the
story.  I don't know.

Re: Debian/Xen on ARM: How to identify source of an unhandled SMC call during boot?

[Andrew M.A. Cater]

On Wed, Jan 31, 2024 at 08:02:47AM +0100, Paul Leiber wrote:
> Am 25.01.2024 um 22:28 schrieb Paul Leiber:
> > 
> > Paul
> > 
> > [1]
> > https://lists.xenproject.org/archives/html/xen-devel/2023-10/msg00796.html
> > [2] https://developer.arm.com/documentation/den0098/latest/
> > [3] 
> > https://documentation-service.arm.com/static/628b755ce3c4322a76af56de?token=
> > 
> 
> Hm, no reply so far. Is this maybe the wrong list? Should I post this rather
> somewhere else?
> 
> Paul
>

debian-arm / OFTC IRC #debian-arm or #debian-raspberrypi

Xen in Debian is team maintained, I think, but many people have moved
away from Xen in favour of other virtualisation/paravirtualisation
solutions and containers.

All the very best, as ever,

Andy
(amaca...@debian.org) 

Re: chrony date months off

[gene heskett]

On 1/31/24 10:44, Greg Wooledge wrote:

On Wed, Jan 31, 2024 at 10:25:40AM -0500, gene heskett wrote:

On 1/31/24 08:53, John Hasler wrote:

Gene writes:

How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?


initstepslew

man chrony.conf


deprecated in favor of makestep, and did not work, John.


*sigh*

How many times do we have to say it?  When something goes wrong, don't
simply say "it didn't work".  Give the *details*.

What changes did you make to files?  What do the files look like now?

gene@bpi51e5p:/etc/chrony$ cat chrony.conf
# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usable directives.

# Include configuration files found in /etc/chrony/conf.d.
confdir /etc/chrony/conf.d

# This will use (up to):
# - 4 sources from ntp.ubuntu.com which some are ipv6 enabled
# - 2 sources from 2.ubuntu.pool.ntp.org which is ipv6 enabled as well
# - 1 source from [01].ubuntu.pool.ntp.org each (ipv4 only atm)
# This means by default, up to 6 dual-stack and up to 2 additional IPv4-only
# sources will be used.
# At the same time it retains some protection against one of the entries 
being

# down (compare to just using one of the lines). See (LP: #1754358) for the
# discussion.
#
# About using servers from the NTP Pool Project in general see (LP: 
#104525).

# Approved by Ubuntu Technical Board on 2011-02-08.
# See http://www.pool.ntp.org/join.html for more information.
#pool ntp.ubuntu.comiburst maxsources 4
#pool 0.ubuntu.pool.ntp.org iburst maxsources 1
#pool 1.ubuntu.pool.ntp.org iburst maxsources 1
#pool 2.ubuntu.pool.ntp.org iburst maxsources 2

# Use time sources from DHCP.
sourcedir /run/chrony-dhcp
sourcedir /etc/chrony/sources.d

# This directive specify the location of the file containing ID/key 
pairs for

# NTP authentication.
keyfile /etc/chrony/chrony.keys

# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift

# Save NTS keys and cookies.
ntsdumpdir /var/lib/chrony

# Uncomment the following line to turn logging on.
#log tracking measurements statistics

# Log files location.
logdir /var/log/chrony

# Stop bad estimates upsetting machine clock.
maxupdateskew 10.0
initstepslew 30 192.168.71.3
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can’t be used along with the 'rtcfile' 
directive.

rtcsync

# Step the system clock instead of slewing it if the adjustment is 
larger than

# one second, but only in the first three clock updates.
makestep 1 3000

# Get TAI-UTC offset and leap seconds from the system tz database.
# This directive must be commented out when using time sources serving
# leap-smeared time.
leapsectz right/UTC
gene@bpi51e5p:/etc/chrony$

Now, the file in /etc/chrony/sources.d:
gene@bpi51e5p:/etc/chrony/sources.d$ cat local-ntp-server.sources
server 192.168.71.3 iburst
gene@bpi51e5p:/etc/chrony/sources.d$



What commands did you run?


6 of one half a dozen of the other
gene@bpi51e5p:/etc/init.d$ sudo ./chrony status
[sudo] password for gene:
× chrony.service - chrony, an NTP client/server
 Loaded: loaded (/lib/systemd/system/chrony.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: protocol) since Sat 2023-12-30 03:15:44 
EST; 2h 12min ago

   Docs: man:chronyd(8)
 man:chronyc(1)
 man:chrony.conf(5)
Process: 1908 ExecStart=/usr/lib/systemd/scripts/chronyd-starter.sh 
$DAEMON_OPTS (code=exited, status=0/SUCCESS)

CPU: 158ms

Dec 30 03:15:31 bpi51e5p chronyd[1936]: chronyd version 4.2 starting 
(+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGN…6 -DEBUG)
Dec 30 03:15:31 bpi51e5p chronyd[1936]: Frequency -20.055 +/- 0.010 ppm 
read from /var/lib/chrony/chrony.drift
Dec 30 03:15:32 bpi51e5p chronyd[1936]: Using right/UTC timezone to 
obtain leap second data

Dec 30 03:15:32 bpi51e5p chronyd[1936]: Loaded seccomp filter (level 1)
Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
Dec 30 03:15:42 bpi51e5p chronyd[1936]: No suitable source for initstepslew
Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
Dec 30 03:15:44 bpi51e5p systemd[1]: chrony.service: New main PID 1936 
does not exist or is a zombie.
Dec 30 03:15:44 bpi51e5p systemd[1]: chrony.service: Failed with result 
'protocol'.
Dec 30 03:15:44 bpi51e5p systemd[1]: Failed to start chrony, an NTP 
client/server.

Hint: Some lines were ellipsized, use -l to show in full.
gene@bpi51e5p:/etc/init.d$

or

gene@bpi51e5p:/etc/init.d$ sudo systemctl status chrony.service
× chrony.service - chrony, an NTP client/server
 Loaded: loaded (/lib/systemd/system/chrony.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: protocol) since Sat 2023-12-30 03:15:44 
EST; 2h 13min ago

   Docs: man:chronyd(8)
 man:chronyc(1)

Re: Can't list root directory

[Max Nikulin]

On 29/01/2024 23:42, Gary Dale wrote:

"ls -l /" just hangs


It may dereference symlinks, call stat, etc. to colorize output. May it 
happen that you have automount points or something related to network 
mounts?


Does "echo /*" hangs?

Even bash prompt may do some funny stuff. I would try it from "dash".

Can you install strace? E.g. copy files while booted from a live media.

Re: Tirar dessa lista

[Sinval Júnior]

Rodrigo,  tente este link 1.


[1]
https://permita.me/?q=Cancelamento+de+inscri%C3%A7%C3%A3o+das+listas+de+discuss%C3%A3o+debian+portugues


Ao encaminhar esta mensagem, por favor:
1 - Apague meu endereço eletrônico;
2 - Encaminhe como Cópia Oculta (Cco ou BCc) aos seus destinatários.
Dificulte assim a disseminação de vírus, spams e banners.

#=+
#!/usr/bin/env python
nome = 'Sinval Júnior'
email = 'sinvalju arroba gmail ponto com'
print nome
print email
#==+


Em seg., 22 de jan. de 2024 às 17:32, Rodrigo S.Pereira 
escreveu:

> Por gentileza podem me retirar desta lista ?
>
> Obrigado desde já.
>

Re: chrony date months off

[Greg Wooledge]

On Wed, Jan 31, 2024 at 10:25:40AM -0500, gene heskett wrote:
> On 1/31/24 08:53, John Hasler wrote:
> > Gene writes:
> > > How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> > > the current time on the first cycle as its rebooting?
> > 
> > initstepslew
> > 
> > man chrony.conf
> 
> deprecated in favor of makestep, and did not work, John.

*sigh*

How many times do we have to say it?  When something goes wrong, don't
simply say "it didn't work".  Give the *details*.

What changes did you make to files?  What do the files look like now?

What commands did you run?

What output did you get?

What output did you *expect* to get?

What other relevant details can you supply?  (The identities and
configurations of the NTP servers that chrony is expected to use, for
example.)

Re: chrony date months off

[gene heskett]

On 1/31/24 08:53, John Hasler wrote:

Gene writes:

How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?


initstepslew

man chrony.conf


deprecated in favor of makestep, and did not work, John.

Thanks, John

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

Re: [HS] aide à la traduction

[Michel Verdier]

Le 31 janvier 2024 Sébastien NOBILI a écrit :

> Le système de gestion des listes a reçus de "bounces" de votre part.
> C'est ce qui arrive lorsque votre serveur mail rejette un e-mail.
> Ça peut arriver lorsque du spam est véhiculé via lia liste.

Il faut préciser que c'est le serveur recevant en premier les mails, donc
ici un serveur chez orange. Ca arrive avec tous les fournisseurs.

Re: Automatically installing GRUB on multiple drives

[Andy Smith]

Hi,

On Tue, Jan 30, 2024 at 09:50:23PM +0100, hw wrote:
> On Mon, 2024-01-29 at 23:53 +, Andy Smith wrote:
> > I think you should read it again until you find the part where it
> > clearly states what the problem is with using MD RAID for this. If
> > you still can't find that part, there is likely to be a problem I
> > can't assist with.
> 
> That there may be a problem doesn't automatically mean that you need a
> bunch of scripts.

This is getting quite tedious.

Multiple people have said that there is a concern that UEFI firmware
might write to an ESP, which would invalidate the use of software
RAID for the ESP.

Multiple people have suggested instead syncing ESP partitions in
userland. If you're going to do that then you'll need a script to do
it.

I don't understand what you find so difficult to grasp about this.
If it's that you have some other proposal for solving this, it would
be helpful for you to say so, instead of just repeating "why do you
need scripts, you don't need scripts", because if you just repeat
that, all I can do is repeat what I've already said until I become
bored and stop.

If your suggested solution is "use hardware RAID", no need to repeat
that one though: I see you said it in a few other messages, and that
suggestions has been received. Assume the conversation continues
amongst people who don't like that suggestion.

Otherwise, I don't think anyone knows what you have spent several
messages trying to say. All we got was, "you don't need scripts".

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: chrony date months off

[John Hasler]

Max Nikulin wrote:
> I think, the problem is no RTC on some *pi board, certainly chrony out of
> box setup is not ready to such environment and its solution is not
> maxstep.

That's what makestep (initstepslew now being deprecated) is for.
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: Can't list root directory

[The Wanderer]

On 2024-01-29 at 11:42, Gary Dale wrote:

> I'm running Debian/Trixie on an AMD64 workstation. I've lost the
> ability to see the root directory even when I am logged in as root
> (su -).
> 
> This has been happening intermittently for several months. I
> initially thought it might be related to failing NVME drive that was
> part of a RAID1 array that is mounted as "/" but I replaced the
> device and the problem is still happening.
> 
> I had been able to fix it by booting to SystemRescue and running an
> fsck on the device but it didn't work this time. The device checks
> out OK (even when using fsck -/dev/mdx -f) but I still can't list the
> root. "ls -l /" just hangs, as do any attempts to see the root
> directory in a graphical file manager. In dolphin this means there is
> nothing in the folders - and since that is the default starting point
> I have to manually enter a folder name (e.g. /home/me) in the
> location bar to be able to see anything - but even then the folders
> panel remains empty.
> 
> Even running commands like df -h hang because they can't access the
> root folder. However the system is otherwise running normally.

I'm not sure it'll help lead to anything, but out of curiosity and/or as
a possible diagnostic: when the problem is manifesting, what happens if
you run 'stat /'? Does it report data (similar to what you'd get from
'stat' on another directory), or does it hang, or give errors, or...?

My thought is that this will give information about the filesystem
object that is the root directory, without trying to also access
information about the *contents* of that directory. If the one succeeds
where the other fails, that might help narrow down where the actual
issue is.

-- 
   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: Can't list root directory

[Gary Dale]

On 2024-01-29 12:55, Hans wrote:

Hi Gary,

before loosing any data, I suggest, to boot from a liuvefile linux. Please use
a modern livefile like Knoppix or Kali-Linux.

If it is not a BIOS problem, you should see the device again and are able to
mount it. If /root is on a seperated partition, you can do some filesystem
checks, like e2fsck or else.

Ans: Most important, with a livefile system you can mount an external harddrive
and backup all files. Thus , even when the /dev/nvme*** is died or partly
broken, you can maybe restore /root on another partition.

Second: Please check ACL, although I do not believe the reason for these, it
is worth to look at this. Maybe you or someone else has chenged it accidently.

Third idea: Is the harddrive full? In the past I has the problem, not to be
able to do anything. The reason: My harddrive was completely full (some
temporary file was the reason). Deleting this big file was the trick.

Just some ideas, maybe it could help.

Good luck!

Best

Hans


There is no problem seeing the root folder when I boot from a live distro.

fsck never finds any significant issue.

An ACL issue would be permanent. This comes and goes.

I actually doubled the size of the root device when I put in the new 
NVME drive. When I set up the RAID array, I'd bought a 500G second drive 
to mirror the 256G original drive. When I replaced the 256G drive, I was 
able to expand the array to 500G (less a small amount for the EFI 
partition). The partition has lots of free space.


As I said, running an fsck seems to fix the issue temporarily. I now run 
an fsck on every boot.

Re: chrony date months off

[gene heskett]

On 1/31/24 07:13, Max Nikulin wrote:

On 31/01/2024 17:54, to...@tuxteam.de wrote:

I think you want "maxstep". It's in the man page chrony.conf(5).

But if the time is "months off" perhaps you've got another problem
to fix first?
Well, I do have other probs with that machine, mostly with the physicsl 
config of the BTT Octopus Pro 3dprinter control card its running, but 
that is not os related, it just a detail I have fixed on all the other 
machines.


I think, the problem is no RTC on some *pi board, certainly chrony out 
of box setup is not ready to such environment and its solution is not 
maxstep.


Gene, are you going to complain again that some package has no man pages?


Mope.  Thanks Max

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

Re: Can't list root directory

[Gary Dale]

On 2024-01-29 11:42, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 workstation. I've lost the 
ability to see the root directory even when I am logged in as root (su 
-).


This has been happening intermittently for several months. I initially 
thought it might be related to failing NVME drive that was part of a 
RAID1 array that is mounted as "/" but I replaced the device and the 
problem is still happening.


I had been able to fix it by booting to SystemRescue and running an 
fsck on the device but it didn't work this time. The device checks out 
OK (even when using fsck -/dev/mdx -f) but I still can't list the 
root. "ls -l /" just hangs, as do any attempts to see the root 
directory in a graphical file manager. In dolphin this means there is 
nothing in the folders - and since that is the default starting point 
I have to manually enter a folder name (e.g. /home/me) in the location 
bar to be able to see anything - but even then the folders panel 
remains empty.


Even running commands like df -h hang because they can't access the 
root folder. However the system is otherwise running normally.


Strangely, in the past simply booting to a rescue shell then exiting 
would also work. I'd usually try to do an fsck on the raid device but 
that would always fail because it was mounted.


The only thing I noticed that was unusual was I rebooted after 
installing the latest Trixie updates this morning. That took about 10 
minutes to shut down - 6 of which were spent waiting for a drkonqi 
process to finish. There was also a systemd message really late in the 
shutdown about /dev/md0 but that's not the root device.


I'm used to Linux taking its time to shutdown lately so I don't think 
this was related. The systemd shutdown just seems to be easily delayed.


Any ideas on how I can restore my ability to see the root directory?

OK, got it working again. I used tune2fs to do an fsck on every boot. 
This being an NVME device, it's barely noticeable.

Re: Can't list root directory

[Gary Dale]

On 2024-01-30 15:54, hw wrote:

On Mon, 2024-01-29 at 11:42 -0500, Gary Dale wrote:

I'm running Debian/Trixie on an AMD64 workstation. I've lost the ability
to see the root directory even when I am logged in as root (su -).

This has been happening intermittently for several months. I initially
thought it might be related to failing NVME drive that was part of a
RAID1 array that is mounted as "/" but I replaced the device and the
problem is still happening.
[...]

What happens when you put the device you replaced back?

How could putting a known-failing device back in help? The problem 
existed before I replaced it and continues to exist after the replacement.

Re: [HS] aide à la traduction

[Sébastien NOBILI]

Bonjour,

Ce message est "fréquent" quand on est abonné aux listes Debian.

Il dit deux choses :

Le 2024-01-31 15:02, Norbert Ponce a écrit :

In the last seven days we've seen bounces for the following list:
* debian-user-french


Le système de gestion des listes a reçus de "bounces" de votre part.
C'est ce qui arrive lorsque votre serveur mail rejette un e-mail.
Ça peut arriver lorsque du spam est véhiculé via lia liste.

L'info réellement importante est là :


1 bounce out of 39 mails in 7 days (2%, kick-score is 80%)
(https://lists.debian.org/bounces/MzZq8GgorlrkIynI7O8JoA)


1 "bounce" sur 39 mails, soit 2% du trafic total.
Tant qu'on reste en dessous de 80%, pas de problème (et c'est
toujours le cas quand il s'agit de "bounce" à cause de messages
douteux véhiculés via la liste).

Si votre score dépasse 80% (ce qui sera le cas si votre serveur
mail dysfonctionne), alors vous serez désabonné de la liste.

Sébastien

Re: chrony date months off

[Greg Wooledge]

On Wed, Jan 31, 2024 at 07:53:01AM -0600, John Hasler wrote:
> Gene writes:
> > How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> > the current time on the first cycle as its rebooting?
> 
> initstepslew
> 
> man chrony.conf

Debian 12 has chrony 4.3, and in *that* version of the man page, it
says initstepslew is deprecated in favor of makestep.

https://chrony-project.org/doc/4.3/chrony.conf.html#makestep

[HS] aide à la traduction

[Norbert Ponce]

Bonjour,
J'ai reçu plusieurs messages comme celui que je vous transmets. Je ne 
maîtrise aucunement l'anglais.
Quelqu'un pourrait-il m'expliquer de quoi il s'agit et ce qu'il faut que 
je fasse.

Merci


 Message transféré 
Sujet : lists.debian.org has received bounces from 
ponce.norb...@orange.fr
Date :  Sun, 28 Jan 2024 10:45:27 + (UTC)
De :Debian Listmaster Team 
Répondre à :listmas...@lists.debian.org
Pour :  ponce.norb...@orange.fr



Dear subscriber,

We've encountered some problems while sending listmail to your
emailaddress ponce.norb...@orange.fr.

In the last seven days we've seen bounces for the following list:
* debian-user-french
1 bounce out of 39 mails in 7 days (2%, kick-score is 80%)
(https://lists.debian.org/bounces/MzZq8GgorlrkIynI7O8JoA)

(The link above points to a copy of the latest bounce
and will be valid for seven days.)

If the bounce-rate passes the kick-score, our bounce-detection will forcibly
remove your subscription.

Bounces happen from time to time when spam slips through our filters but are
rejected by your mail provider. If you are your own mail provider and use
'Before-Queue Content filtering', you should whitelist bendel.debian.org 
from

Content filtering.

However: You can safely ignore this message (and you will not be 
unsubscribed

:-) ) if your bounce rate remains low.

For more information see https://wiki.debian.org/Teams/ListMaster/FAQ

You are welcome to contact listmas...@lists.debian.org if you think this
message was sent in error.

Sincerely,
The Listmaster Team

--
http://lists.debian.org

AW: AW: su su- sudo dont work

[Schwibinger Michael]

Good afternoon
I think
maybe Im sure
it is because of rescue mode.

Normal booting did not have this problem.

Anybody familiar with panic?

Regards
Thank You
Sophie



Von: Andrew M.A. Cater 
Gesendet: Donnerstag, 25. Januar 2024 18:40
An: debian-user@lists.debian.org 
Betreff: Re: AW: su su- sudo dont work

On Thu, Jan 25, 2024 at 03:53:10PM +, Schwibinger Michael wrote:
> Good afternoon
> Why do I have to open a group?
>

This is to *tell* us information about why you're having problems with su
and sudo

Running the

id

command should give you information like

uid=1000(amacater) gid=1000(amacater) groups=1000(amacater),27(sudo)

which shows you that my user - amacater - is the first user on the
machine (because Debian starts user id numbers at 1000 for ordinary
users) and that I'm a member of group sudo - so can use sudo instead of su.

/etc/sudoers will show you what privileges the sudo user has.
Here are the last lines of the file on my machine (which has not been
modified from Debian defaults)

# User privilege specification
rootALL=(ALL:ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "@include" directives:

@includedir /etc/sudoers.d
(END)

If you are _not_ a user of group sudo for whatever reason - and want to
use sudo - then you will need root privileges and the root password
(once) to add your user name to the group.

For example: adduser sophie sudo

I hope this helps

> 2 years ago
> sudo was no problem.
>

As yet, we have *no idea* what you have done in the last two years to
break your Debian system - or even to know which kernel you boot or
how you "rescue" your system when you log onto it every day.

Please give us information in order that the readers on this list can
use their knowledge to help you.

With every good wish, as ever,

Andy
(amaca...@debian.org)
> Regards
>
> Sophie
>
> Thank You
> 
> Von: Timothy M Butterworth 
> Gesendet: Montag, 22. Januar 2024 00:07
> An: Schwibinger Michael 
> Cc: Greg Wooledge ; debian-user@lists.debian.org 
> 
> Betreff: Re: su su- sudo dont work
>
>
>
> On Sun, Jan 21, 2024 at 4:07 PM Schwibinger Michael 
> mailto:h...@hotmail.com>> wrote:
> Thank You
> Example
> I say
>
> sudo apt-get install firefox
> Reaction LINUX
> This is not allowed we send a message to the admin.
>
> This error message means that your account is not in the sudo group.
>
> Run the command "groups" and look for the group sudo.
> groups
>
> Here is the command to add a user account to the sudo group. You will need to 
> run it as root.
> usermod -a -G sudo 
>
> I do open root terminal
> there its working.
> Regards
> Sophie
>
> 
> Von: Greg Wooledge mailto:g...@wooledge.org>>
> Gesendet: Samstag, 20. Januar 2024 14:14
> An: debian-user@lists.debian.org 
> mailto:debian-user@lists.debian.org>>
> Betreff: Re: su su- sudo dont work
>
> On Sat, Jan 20, 2024 at 01:26:06PM +, Schwibinger Michael wrote:
> > Good afternoon.
> > Root terminal is fine.
> > What do I do wrong?
> > What did I destroy?
> >
> > PC does have only one user=admin.
> >
> > Regards Sophie
> > Is it the rescue mode?
>
> Explain, please.
>
> Your Subject: header says "su su- sudo dont work".  What does this MEAN?
>
> Please show us your attempts to USE each of these commands, and the
> results that you got.  This means, run the commands in a terminal
> window, and then PASTE the contents of that terminal window into the
> body of your next email.  Show us the shell prompt, the command as you
> typed it, and the full output.
>
> In other words, show us WHAT IS WRONG, or at least what appears wrong.
>
> In addition, please give basic background information -- what version
> of Debian you are running, what desktop environment if any, how you
> logged in (*especially* if it isn't just a "standard graphical login
> for your desktop environment"), and anything else you can think of
> that might be relevant.
>
> How does "rescue mode" factor into the problem?
>
> When you installed Debian, did you give a root password, or did you
> leave it blank?
>
> Finally, it would be helpful for you to run the "id" command (with no
> arguments), in the same terminal session as your failed su or sudo
> command(s), and include that command and its output in your paste.
>
>
>
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀

Re: chrony date months off

[John Hasler]

Gene writes:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> the current time on the first cycle as its rebooting?

initstepslew

man chrony.conf
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: chrony date months off

[didar]

On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
> current time on the first cycle as its rebooting?
> There was 20 yeas back, an ntpdate command that would do that.
> Now it appears to conflict with the other client/servers

You can use "rdate" (openrdate) as quick fix like `ntpdate'. I resort to using
it inside my virtual machines on my laptop when it wakes up from hibernation.

I use chrony on my production MTAs on the internet though.

-- 
Regards,
Didar

Worlds are conquered, galaxies destroyed -- but a woman is always a woman.
-- Kirk, "The Conscience of the King", stardate 2818.9

Generated by Signify v1.14 (http://www.debian.org/)

Re: chrony date months off

[Max Nikulin]

On 31/01/2024 17:54, to...@tuxteam.de wrote:

I think you want "maxstep". It's in the man page chrony.conf(5).

But if the time is "months off" perhaps you've got another problem
to fix first?


I think, the problem is no RTC on some *pi board, certainly chrony out 
of box setup is not ready to such environment and its solution is not 
maxstep.


Gene, are you going to complain again that some package has no man pages?

Re: os-prober detects in wrong order and GRUB doesn't have enough options

[Greg Wooledge]

On Wed, Jan 31, 2024 at 05:29:56AM -, David Chmelik wrote:
> Earlier this or last year I tried to use Devuan to report os-prober 
> detects in wrong order.  It may detect current OS partition first, but if 
> you have more than 10, then it continues from 10, and (if this is all you 
> have) goes to the last in the tens but then continues somewhere in single-
> digit partitions,

Sounds like someone's doing an alphanumeric sort on numbers.

unicorn:~$ printf '%s\n' 1 2 3 11 12 13 | sort
1
11
12
13
2
3

It could be a result of filename globbing, e.g. /dev/sda[0-9]* which
would give that kind of ordering.

In any case, this isn't a Devuan mailing list.  If you've reported a
bug to Debian, then you should have the bug number, and the URL to
its web page.  If you've reported it to Devuan, then we can't help.

Re: chrony date months off

[tomas]

On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
> current time on the first cycle as its rebooting?
> There was 20 yeas back, an ntpdate command that would do that.
> Now it appears to conflict with the other client/servers

I think you want "maxstep". It's in the man page chrony.conf(5).

But if the time is "months off" perhaps you've got another problem
to fix first?

You wouldn't want chrony to slam your clock just because its only
reachable server runs amok. Just sayin'.

Cheers
-- 
t


signature.asc
Description: PGP signature

chrony date months off

[gene heskett]

How do I setup /etc/chrony/chrony.conf so it slams the system clock to 
the current time on the first cycle as its rebooting?

There was 20 yeas back, an ntpdate command that would do that.
Now it appears to conflict with the other client/servers

Thanks

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