Re: Change suspend type from kde menu

2024-01-06 Thread Max Nikulin

On 06/01/2024 22:19, Max Nikulin wrote:

On 06/01/2024 19:44, Valerio Vanni wrote:

systemd-run --unit=kaffeine-resumed --uid="$kafuid" --gid="$kafgid" \
   env XDG_RUNTIME_DIR=/run/user/"$kafuid" $kafdis 
XDG_CURRENT_DESKTOP=KDE \

   /usr/bin/kaffeine --lastchannel > /dev/null 2>&1


Instead the application should be in app.slice that is a child of 
user@1000.service. Inspect output of systemd-cgls.


It seems neither su nor sudo add process to the user context (proper 
cgroup, XDG session), so attempts to talk to the systemd user session 
through D-Bus fail.


setpriv --reuid 1000 --regid 1000 --init-groups --reset-env -- \
   env XDG_RUNTIME_DIR="/run/user/1000" \
   systemd-run --user --slice=app.slice -- \
   xterm

I have realized that earlier I forgot to add --user to systemd-run. To 
my surprise, it does not work if I set 
BUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus" instead of 
XDG_RUNTIME_DIR. I expected that the former is required for systemd-run.


This command works from a root shell prompt, I hope it should work 
during resume as well.




Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdandtimezone]

2024-01-06 Thread gene heskett

On 1/6/24 17:06, Nate Bargmann wrote:

* On 2024 06 Jan 14:34 -0600, gene heskett wrote:

On 1/6/24 14:33, John Hasler wrote:

Try manpages.org .


That is downright tasty stuff, bookmarked, thank you John.


For us Debian users a better choice would seem to be:

https://manpages.debian.org/


The pages at manpages.org are better colored and a larger, much easier 
to read font. Content I believe, was the same on the file I cheked.




The only thing is that I don't see a category for oldstable and
oldoldstable, etc.

- Nate



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



xfce screen detachment

2024-01-06 Thread Russell L. Harris

system:  amd64 desktop, debian 12, xfce, NEC MultiSync EA192M monitor

I don't know precisely how to describe the problem, other than
"detachment".  About every week or so, when using the rodent, the
entire screen -- borders and all -- moves with respect to the monitor
screen as I move the mouse.   


The only recovery method I have discovered is to reboot.

My hands and finders no longer are working well, so I likely clicked
on something or pressed a key to cause the problem.

RLH



Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

2024-01-06 Thread Gaëtan Perrier
Finalement le seul fait d'avoir intercalé le gs105e entre la LB6 et le reste 
semble résoudre le problème sans passer par les vlan ...

Gaëtan 

Le 6 janvier 2024 22:44:59 GMT+01:00, "Gaëtan Perrier"  
a écrit :
>Bonjour,
>
>Je fais un gros HS mais je suis sûr qu'il y a des personnes compétentes
>sur la liste. ;)
>
>Mon problème est le suivant. Chez les parents d'un ami qui a des
>chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
>réseaux:
>- un réseau pour les proprio avec du Wifi et des périph filaires,
>- un réseau pour les clients uniquement en Wifi.
>
>On veut que les clients ne puissent pas accéder au réseau proprio.
>
>Actuellement on est installé le matériel suivant:
>- Livebox 6 Pro,
>- un switch GS105Ev2 derrière,
>- 3 AP Netgear WAX214
>- divers périph reliés en eth (RPI, PC, NAS,etc.)
>
>La LB6 est le routeur.
>
>Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour les
>clients.
>Le proprio est sur 192.168.1.* et le client configuré comme "invité"
>est sûr 192.168.200.*
>
>
>Le problème c'est que depuis le Wifi client (192.168.200.*) on voit les
>les RPI, PC, NAS, etc sur 192.168.1.* 
>
>Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre en
>place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur le
>GS105E et sur les AP.
>Mais là je perds la connexion et plus rien ne passe ...
>
>Qu'elle est la bonne solution ?
>
>Merci d'avance pour votre aide.
>
>Gaëtan
>

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone]

2024-01-06 Thread Greg Wooledge
On Sat, Jan 06, 2024 at 03:49:05PM -0600, Nate Bargmann wrote:
> For us Debian users a better choice would seem to be:
> 
> https://manpages.debian.org/
> 
> The only thing is that I don't see a category for oldstable and
> oldoldstable, etc.

It's by release code name, e.g. "buster" instead of "oldoldstable".

 (which is easy to remember
and to type manually) takes you to a disambiguation page that links to
 and so on.

If you skip the release name and just go to
 it takes a guess and redirects you
to 
which is not the GNU awk page, but hey, it's *one* awk page.

I have no idea why some conflicts result in a disambiguation page, and
others result in a guess.

 takes you to
 which is
more likely what you wanted.

If you want an older release's man page, you can edit the URL and
replace "bookworm" with "bullseye" or whatever.

So, there's a certain intuitiveness to the URL bar interface, but also
some surprises, when multiple source packages all provide a man page
with the same name.



Re: reinstallation and restore after catastrophic mistake or failure; was: 1 Currently unreadable (pending) sectors How worried should I be?

2024-01-06 Thread David Christensen

On 1/6/24 04:36, Michael Kjörling wrote:

On 6 Jan 2024 00:37 -0800, from dpchr...@holgerdanske.com (David Christensen):

I suggest taking an image (backup) with dd(1), Clonezilla, etc., when you're
done.  This will allow you to restore the image later -- to roll-back a
change you do not like, to recovery from a disaster, to clone the image to
another device, to facilitate experiments, (such as doing a secure erase to
see if it resolves the SSD pending sector issue), etc..

If you also keep your system configuration files in a version control
system, restoring an image is faster than wipe/ fresh install/ configure/
restore data.


I would go even farther. Backups should be designed such that
recovering from a catastrophic storage failure, such as getting hit by
ransomware, unintentionally doing a destructive badblocks write test
or the sudden failure of a storage device, is possible by at most
something very similar to:

* Boot some kind of live environment



I wanted more tools than what the Debian installer rescue shell provides 
(e.g. BusyBox) and I am too lazy to learn yet another live system (e.g. 
Knoppix), so I installed Debian with Xfce onto two USB drives -- one 
with BIOS/MBR and the other with secure UEFI/GPT.  They are both 
complete installs, so they are familiar and I can add whatever I want.




* Set up file systems on the storage device to be restored onto
   (partitioning, setting up LUKS containers, formatting, whatever else
   might be called for)
* Within the live environment, install and configure the software
   needed to access the backup (if any) (this may include things like
   cryptographic keys, access passphrases and the likes)
* Perform the restoration from the most recent backup (this is the
   part that likely will take a significant amount of time)



I keep my Debian instances small, simple, and self-contained (1 GB ext4 
boot, 1 GB dm-crypt swap, and 12 GB LUKS ext4 root on one 16+ GB 2.5" 
SATA SSD).  dd(1) meets all of my imaging needs.  It's fast and requires 
minimal storage -- less than 10 minutes using an old-school USB 2.0 HDD; 
each 100 GB holds 6+ images.  (`apt-get autoremove`, `apt-get 
autoclean`, fstrim(8), and/or gzip(1) can reduce time and storage 
requirements.)



If my OS instances were larger, more complex, shared disk space, etc. -- 
e.g. multi-boot Windows, Debian, etc., with a shared data partition -- 
e.g. what the OP likely had -- I would think about a tool such as 
Clonezilla.  Then I would get a big USB 3.0+ HDD/RAID, boot one of my 
Debian USB instances, look at the partition table, and take dd(1) images 
in chunks -- block 0 to the last block before ESP, the ESP, then each 
partition or contiguous span of related partitions, and finally the 
secondary GPT header.




* Update the restored copies of /etc/fstab, /etc/crypttab and any
   other files that directly reference the partitions or file systems
   by some kind of ID (UUID, /dev/disk/by-*/*, ...)
* Reinstall the boot loader



When I take a dd(1) image of an MBR disk, I copy from block 0 through 
the end of the root partition.  So:


1.  UUID's are preserved.

2.  All boot loader stages are preserved.


When I take an dd(1) image of a GPT disk with lots of zeros (fresh wipe 
and install), I copy the whole thing.  Again, UUID's and boot loader 
stages are preserved.



Using live media for UUID and/or boot loader surgery is non-trivial, as 
discussed in more than a few posts to this list.  But, such may be 
required after restoring an image onto a different disk and/or hardware 
arrangement.




* Reboot
* Reinstall the boot loader again from within the restored environment
   to ensure that everything relating to it is in sync



For the simple case of restoring an image onto the exact same hardware, 
a restored MBR image just works.  Same for GPT.  If a GPT disk was 
zeroed or secure erased, a secondary GPT header will need to be needed 
written.  I believe GRUB, Linux, or something on Debian did this 
automagically for me the last time I tried.




Such recovery should _not_ need to involve significant reconfiguration
of anything. Any such requirements will massively increase your time
to recovery, as I think we're seeing an example of here. And yes,
pretty much all of this could be scripted, but I strongly suspect that
few people need to do a bare-metal restore of their most recent backup
often enough for _that_ to be worth the effort to create and maintain.



AIUI the OP accidentally zeroed a Windows/ Debian multi-boot disk in a 
relatively new computer.  Rebuilding from scratch is going to involve 
more than twice the effort of rebuilding one OS from scratch, but 
hopefully there was no live data lost.



I have a half dozen computers in my SOHO network.  I trash my daily 
driver at least once a year and my workhorse more often than that.



I started with disaster preparedness/ recovery using 
lowest-common-denominator tools -- tar(1), gzip(1), rsync(1), dd(1), 
etc..  I am a 

Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

2024-01-06 Thread Gaëtan Perrier
Le samedi 06 janvier 2024 à 23:49 +0100, MERLIN Philippe a écrit :
> Le samedi 6 janvier 2024, 23:24:09 CET Jérémy Prego a écrit :
> > Bonjour,
> > 
> > j'apporte pas forcément une réponse, mais j'ai des questions
> > 
> > Par hasard, quel est le mask réseau configuré que  ça soit sur le
> > 192.168.1.* et / ou le 192.168.200.* ?
> > 
> > Quel périphérique distribue les ip en 192.168.200.* ?
> > 
> > Concernant la perte du réseau quand des vlans
> > sont configurés, c'est normal, si la livebox ne fait pas de vlan,
> > qu'elle ne récupère pas le traffic qui vient du vlan en question.
> > 
> > Jerem
> > 
> > Le 06/01/2024 à 22:44, Gaëtan Perrier a écrit :
> > > Bonjour,
> > > 
> > > Je fais un gros HS mais je suis sûr qu'il y a des personnes
> > > compétentes
> > > sur la liste. ;)
> > > 
> > > Mon problème est le suivant. Chez les parents d'un ami qui a des
> > > chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
> > > réseaux:
> > > - un réseau pour les proprio avec du Wifi et des périph filaires,
> > > - un réseau pour les clients uniquement en Wifi.
> > > 
> > > On veut que les clients ne puissent pas accéder au réseau
> > > proprio.
> > > 
> > > Actuellement on est installé le matériel suivant:
> > > - Livebox 6 Pro,
> > > - un switch GS105Ev2 derrière,
> > > - 3 AP Netgear WAX214
> > > - divers périph reliés en eth (RPI, PC, NAS,etc.)
> > > 
> > > La LB6 est le routeur.
> > > 
> > > Sur les WAX214 2 SSID sont configurés: un pour les proprio,un
> > > pour les
> > > clients.
> > > Le proprio est sur 192.168.1.* et le client configuré comme
> > > "invité"
> > > est sûr 192.168.200.*
> > > 
> > > 
> > > Le problème c'est que depuis le Wifi client (192.168.200.*) on
> > > voit les
> > > les RPI, PC, NAS, etc sur 192.168.1.*
> > > 
> > > Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de
> > > mettre en
> > > place des VLAN en activant la fonctionnalité 802.1Q-based VLANs
> > > sur le
> > > GS105E et sur les AP.
> > > Mais là je perds la connexion et plus rien ne passe ...
> > > 
> > > Qu'elle est la bonne solution ?
> > > 
> > > Merci d'avance pour votre aide.
> > > 
> > > Gaëtan
> Pourquoi faire compliqué quand on peut faire simple.
> On ajoute un routeur Wifi connecté en éthernet à ta Livebox qui
> gérera que les 
> clients le coût du routeur est très faible.
> Pour tes parents le réseau Wifi de la Livebox.
> Philippe Merlin

Non ça ne répond pas au besoin. Il y a 400m2 à couvrir avec les deux
réseaux. D'où les 3 AP (reliés en filaire).

Gaëtan



Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

2024-01-06 Thread MERLIN Philippe
Le samedi 6 janvier 2024, 23:24:09 CET Jérémy Prego a écrit :
> Bonjour,
> 
> j'apporte pas forcément une réponse, mais j'ai des questions
> 
> Par hasard, quel est le mask réseau configuré que  ça soit sur le
> 192.168.1.* et / ou le 192.168.200.* ?
> 
> Quel périphérique distribue les ip en 192.168.200.* ?
> 
> Concernant la perte du réseau quand des vlans
> sont configurés, c'est normal, si la livebox ne fait pas de vlan,
> qu'elle ne récupère pas le traffic qui vient du vlan en question.
> 
> Jerem
> 
> Le 06/01/2024 à 22:44, Gaëtan Perrier a écrit :
> > Bonjour,
> > 
> > Je fais un gros HS mais je suis sûr qu'il y a des personnes compétentes
> > sur la liste. ;)
> > 
> > Mon problème est le suivant. Chez les parents d'un ami qui a des
> > chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
> > réseaux:
> > - un réseau pour les proprio avec du Wifi et des périph filaires,
> > - un réseau pour les clients uniquement en Wifi.
> > 
> > On veut que les clients ne puissent pas accéder au réseau proprio.
> > 
> > Actuellement on est installé le matériel suivant:
> > - Livebox 6 Pro,
> > - un switch GS105Ev2 derrière,
> > - 3 AP Netgear WAX214
> > - divers périph reliés en eth (RPI, PC, NAS,etc.)
> > 
> > La LB6 est le routeur.
> > 
> > Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour les
> > clients.
> > Le proprio est sur 192.168.1.* et le client configuré comme "invité"
> > est sûr 192.168.200.*
> > 
> > 
> > Le problème c'est que depuis le Wifi client (192.168.200.*) on voit les
> > les RPI, PC, NAS, etc sur 192.168.1.*
> > 
> > Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre en
> > place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur le
> > GS105E et sur les AP.
> > Mais là je perds la connexion et plus rien ne passe ...
> > 
> > Qu'elle est la bonne solution ?
> > 
> > Merci d'avance pour votre aide.
> > 
> > Gaëtan
Pourquoi faire compliqué quand on peut faire simple.
On ajoute un routeur Wifi connecté en éthernet à ta Livebox qui gérera que les 
clients le coût du routeur est très faible.
Pour tes parents le réseau Wifi de la Livebox.
Philippe Merlin





manpages package [WAS Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread Andrew M.A. Cater
On Sat, Jan 06, 2024 at 01:17:13PM -0600, John Hasler wrote:
> Try manpages.org .
> -- 
> John Hasler 
> j...@sugarbit.com
> Elmwood, WI USA
>

If you're on a Debian system, this should already be installed but otherwise

apt-get install manpages

Also - manpages.debian.org gives you a searchable interface to all the
Debian manpages.

All the best

Andy
(amaca...@debian.org)
 



Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

2024-01-06 Thread Gaëtan Perrier
Le samedi 06 janvier 2024 à 23:24 +0100, Jérémy Prego a écrit :
> Bonjour,
> 
> j'apporte pas forcément une réponse, mais j'ai des questions
> 
> Par hasard, quel est le mask réseau configuré que  ça soit sur le 
> 192.168.1.* et / ou le 192.168.200.* ?

255.255.255.0 pour les deux.

> 
> Quel périphérique distribue les ip en 192.168.200.* ?

L'AP WAX214

> Concernant la perte du réseau quand des vlans
> sont configurés, c'est normal, si la livebox ne fait pas de vlan, 
> qu'elle ne récupère pas le traffic qui vient du vlan en question.

Ça veut dire qu'il faudrait mettre un routeur VLAN derrière la LB6 ?
Est-ce qu'il faut aussi que tous les switchs intermédiaires soient VLAN
compatibles ?

Existe-t'il une solution pour isoler les deux réseaux sans VLAN ?

Gaëtan 


> 
> Jerem
> Le 06/01/2024 à 22:44, Gaëtan Perrier a écrit :
> > Bonjour,
> > 
> > Je fais un gros HS mais je suis sûr qu'il y a des personnes
> > compétentes
> > sur la liste. ;)
> > 
> > Mon problème est le suivant. Chez les parents d'un ami qui a des
> > chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
> > réseaux:
> > - un réseau pour les proprio avec du Wifi et des périph filaires,
> > - un réseau pour les clients uniquement en Wifi.
> > 
> > On veut que les clients ne puissent pas accéder au réseau proprio.
> > 
> > Actuellement on est installé le matériel suivant:
> > - Livebox 6 Pro,
> > - un switch GS105Ev2 derrière,
> > - 3 AP Netgear WAX214
> > - divers périph reliés en eth (RPI, PC, NAS,etc.)
> > 
> > La LB6 est le routeur.
> > 
> > Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour
> > les
> > clients.
> > Le proprio est sur 192.168.1.* et le client configuré comme
> > "invité"
> > est sûr 192.168.200.*
> > 
> > 
> > Le problème c'est que depuis le Wifi client (192.168.200.*) on voit
> > les
> > les RPI, PC, NAS, etc sur 192.168.1.*
> > 
> > Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre
> > en
> > place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur
> > le
> > GS105E et sur les AP.
> > Mais là je perds la connexion et plus rien ne passe ...
> > 
> > Qu'elle est la bonne solution ?
> > 
> > Merci d'avance pour votre aide.
> > 
> > Gaëtan
> > 
> 



Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

2024-01-06 Thread Jérémy Prego

Bonjour,

j'apporte pas forcément une réponse, mais j'ai des questions

Par hasard, quel est le mask réseau configuré que  ça soit sur le 
192.168.1.* et / ou le 192.168.200.* ?


Quel périphérique distribue les ip en 192.168.200.* ?

Concernant la perte du réseau quand des vlans
sont configurés, c'est normal, si la livebox ne fait pas de vlan, 
qu'elle ne récupère pas le traffic qui vient du vlan en question.


Jerem
Le 06/01/2024 à 22:44, Gaëtan Perrier a écrit :

Bonjour,

Je fais un gros HS mais je suis sûr qu'il y a des personnes compétentes
sur la liste. ;)

Mon problème est le suivant. Chez les parents d'un ami qui a des
chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
réseaux:
- un réseau pour les proprio avec du Wifi et des périph filaires,
- un réseau pour les clients uniquement en Wifi.

On veut que les clients ne puissent pas accéder au réseau proprio.

Actuellement on est installé le matériel suivant:
- Livebox 6 Pro,
- un switch GS105Ev2 derrière,
- 3 AP Netgear WAX214
- divers périph reliés en eth (RPI, PC, NAS,etc.)

La LB6 est le routeur.

Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour les
clients.
Le proprio est sur 192.168.1.* et le client configuré comme "invité"
est sûr 192.168.200.*


Le problème c'est que depuis le Wifi client (192.168.200.*) on voit les
les RPI, PC, NAS, etc sur 192.168.1.*

Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre en
place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur le
GS105E et sur les AP.
Mais là je perds la connexion et plus rien ne passe ...

Qu'elle est la bonne solution ?

Merci d'avance pour votre aide.

Gaëtan





Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone]

2024-01-06 Thread Nate Bargmann
* On 2024 06 Jan 14:34 -0600, gene heskett wrote:
> On 1/6/24 14:33, John Hasler wrote:
> > Try manpages.org .
> 
> That is downright tasty stuff, bookmarked, thank you John.

For us Debian users a better choice would seem to be:

https://manpages.debian.org/

The only thing is that I don't see a category for oldstable and
oldoldstable, etc.

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature


[HS][HELP] Livebox 6, AP WIFI & VLAN

2024-01-06 Thread Gaëtan Perrier
Bonjour,

Je fais un gros HS mais je suis sûr qu'il y a des personnes compétentes
sur la liste. ;)

Mon problème est le suivant. Chez les parents d'un ami qui a des
chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
réseaux:
- un réseau pour les proprio avec du Wifi et des périph filaires,
- un réseau pour les clients uniquement en Wifi.

On veut que les clients ne puissent pas accéder au réseau proprio.

Actuellement on est installé le matériel suivant:
- Livebox 6 Pro,
- un switch GS105Ev2 derrière,
- 3 AP Netgear WAX214
- divers périph reliés en eth (RPI, PC, NAS,etc.)

La LB6 est le routeur.

Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour les
clients.
Le proprio est sur 192.168.1.* et le client configuré comme "invité"
est sûr 192.168.200.*


Le problème c'est que depuis le Wifi client (192.168.200.*) on voit les
les RPI, PC, NAS, etc sur 192.168.1.* 

Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre en
place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur le
GS105E et sur les AP.
Mais là je perds la connexion et plus rien ne passe ...

Qu'elle est la bonne solution ?

Merci d'avance pour votre aide.

Gaëtan



Re: Us ha fallat l'actualització d'ahir de Debian 12.2 a Debian 12.4 ?

2024-01-06 Thread Àlex




El 16/12/23 a les 8:36, Griera ha escrit:

Hola:

Aquest matí s'ha actualitzat a linux-image-6.1.0-16-amd64 (6.1.67-1).

Salut!





Trobo que el que ara haurien d'actualitzar són els mitjans 
d'instal.lació, de Debian 12.4 a 12.5


Amb la imatge actual de Debian estable, 12.4, no puc fer servir wifi a 
les instal.lacions, ja que ve amb el nucli 6.1.0-15.


Sabeu si puc encara descarregar la imatge anterior 12.2 ?   No la trobo





Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone]

2024-01-06 Thread gene heskett

On 1/6/24 14:33, John Hasler wrote:

Try manpages.org .


That is downright tasty stuff, bookmarked, thank you John.

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



Re: was: Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread gene heskett

On 1/6/24 12:07, Max Nikulin wrote:

On 06/01/2024 18:40, gene heskett wrote:
Put all system clocks on UTC, and then /etc/timezone is the actual 
string specifying the local offset. No doubt some user confusion, but 
overall a lot simpler.


I still do not see any connection with splitting a part of files and 
links into another package tzdata-legacy. Kernel anyway keeps time in 
UTC, RTC nowadays is mostly in UTC as well.


Notice that /etc/timezone is a legacy Debian-specific way, most of 
applications use the /etc/localtime symlink.


I do not think there are strong reasons for tzdata-legacy, but I do not 
see a reason for rant as well.


Or, if someone know how to make systemd's timesyncd actually work, 
I've not been able to do that on 7 machines here, that would be 
appreciated too.  Lack of documentation (man pages) for that puppy is 
a major blockaid here on bookworm.


Even if you do not use search engines for some reason, have you tried to 
ask at least systemd itself?


     systemctl help systemd-timesyncd


Does not exist as I manually deleted it and installed ntpsec when I 
could not find any docs to help make it work.  I needed a timeserver 
that did not depend on debians pool and ntpsec answered the call.
I set it up as a stratum 2 server, referencing the debian pool and just 
now got done re-configuring ntp.conf on the rest of my machines that are 
currently booted, to use this machine as a server.


If debian is going to supply systemd's timesyncd as a client, I expected 
a bookworm install to just work. It did not and without docs I have to 
pester the list, which has gotten me a bad rep because the lack of docs 
for this stuff has me in a screw google frame of mind by the time I get 
around to asking the list.  Lately, everytime I go anywhere near google 
or a gmail link I get attacked by a virus that calls itself norton 
antivirus. That is an oxymoron, like military intelligence.



.


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



Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread John Hasler
Try manpages.org .
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA



systemd-boot not asking password, not resuming from hibernate

2024-01-06 Thread Richard Rosner
I just tried out systemd-boot. What I noticed, it doesn't ask for my 
decryption password to decrypt both my LUKS2 encrypted root and swap 
partition. This kinda defeats the purpose of encrypted drives. How do I 
have systemd-boot forget and never again remember my credentials?


For the installation, I just installed systemd-boot. Afterward I had to 
uncomment the timeout option in /boot/efi/loader/loader.conf so I would 
get the selection screen, but I didn't make any other modifications. So 
what exactly is missing?


Adding to that, resume from hibernate doesn't seem to work. Resume is 
included in the options line in the /boot/efi/loader/entries files, it's 
also enabled in initramfs-tools, yet after powering on after 
hibernating, I'm not greeted with where I left off.


PS: by any chance does anybody know if systemd-boot supports Argon2 KDF 
for LUKS2? I only know that Grub2 doesn't (yet), but it's difficult to 
find the specific documentation on systemd-boot.


SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread gene heskett

On 1/6/24 09:25, John Hasler wrote:

The documentation for Chrony is:

chrony.conf (5)  - chronyd configuration file
chronyc (1)  - command-line interface for chrony daemon
chronyd (8)  - chrony daemon

Also see /usr/share/doc/chrony .

Don't use "pool" to sync to a single source.  Use  "server".
does this also work for ntpsec?  Yes it does, thank you for the hint, 
John. now that printer is hitting only my server instead of pestering 
the debian pool.


man chrony.conf


is on the missing list for armbian buster, John. And is not debians 
problem. Which is what is running this 3d printer. Do you know the name 
of the man page package that would install those man pages?  chrony 
isn't the only man pages missing.







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



Re: Debian on Asus X205TA [Was: Re: Installing Debian on an old Asus EEE PC]

2024-01-06 Thread Steve McIntyre
m...@dorfdsl.de wrote:
>Am 06.01.2024 um 10:46:56 Uhr schrieb Leandro Noferini:
>
>> In my Asus EEEPC (X205TA) the bios/uefi is 32 bit but the processor is
>> 64 so you need only the grub 32 bit but the remaining of the operative
>> system, including kernel, is 64 bit.
>
>There was another thread (maybe on debian-users-german?) discussing
>that and Debian 12 doesn't ship multiarch installers, so it will be a
>bit harder to make it work with 32 bit UEFI.

The amd64 installation media now includes the bits needed to start the
installer on mixed-mode UEFI systems like the Bay Trail platform in
the X205TA. I still have an old mixed-moded Apple Imac that works that
way as a test machine.

-- 
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: was: Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread Max Nikulin

On 06/01/2024 18:40, gene heskett wrote:
Put all system clocks on UTC, and then /etc/timezone is the actual 
string specifying the local offset. No doubt some user confusion, but 
overall a lot simpler.


I still do not see any connection with splitting a part of files and 
links into another package tzdata-legacy. Kernel anyway keeps time in 
UTC, RTC nowadays is mostly in UTC as well.


Notice that /etc/timezone is a legacy Debian-specific way, most of 
applications use the /etc/localtime symlink.


I do not think there are strong reasons for tzdata-legacy, but I do not 
see a reason for rant as well.


Or, if someone know how to make systemd's timesyncd actually work, I've 
not been able to do that on 7 machines here, that would be appreciated 
too.  Lack of documentation (man pages) for that puppy is a major 
blockaid here on bookworm.


Even if you do not use search engines for some reason, have you tried to 
ask at least systemd itself?


systemctl help systemd-timesyncd



Re: Change suspend type from kde menu

2024-01-06 Thread Max Nikulin

On 06/01/2024 00:07, Valerio Vanni wrote:


Now I'm looking: services are

├─/MainApplication
├─/Player
├─/Television
├─/TrackList
└─/org
   └─/org/kde
     └─/org/kde/kaffeine

I tried to introspect the more likely, MainApplication and Television



.RemoveProgram  method    u -    -


Do you have any idea what it should do?

I would expect something like "Stop" either from /Player or from 
org.mpris.kaffeine. I have not tried MPRIS D-Bus interface in action though.



If it's started with "-lastchannel" no, you have to close it.
But then you have also to request it to play again.


Is there an action that releases the device? "ls -l /proc/PID/fd" to 
check.


What should I find here?


If no file descriptor is resolved to /dev/ (or maybe /sys) then likely 
the kernel module may be removed without killing the application. 
Compare opened file descriptors when video is playing and when it is 
stopped.





Re: Re: Debian in HPC

2024-01-06 Thread Andrew M.A. Cater
Michael: This discussion has also been taking place periodically in
the main Beowulf lists over at Beowulf.org (https://www.beowulf.org)

See, for example, their archives from May-November 2023 for the thread.

For anyone interested in HPC, I commend the Beowulf list - very small
numbers of extremely motivated, extremely competent people.

Disclaimer: I'm also an occasional contributor to discussions there -
and I first suggested that they use Debian rather than a Red Hat base
in about 1998 when Red Hat launched Extreme Linux :)

All the very best, as ever,

Andy
(amaca...@debian.org)



Re: Change suspend type from kde menu

2024-01-06 Thread Max Nikulin

On 06/01/2024 19:44, Valerio Vanni wrote:

systemd-run --unit=kaffeine-resumed --uid="$kafuid" --gid="$kafgid" \
   env XDG_RUNTIME_DIR=/run/user/"$kafuid" $kafdis 
XDG_CURRENT_DESKTOP=KDE \

   /usr/bin/kaffeine --lastchannel > /dev/null 2>&1


I have not figured out how to do it, but systemd-run should not use 
--uid since this way it makes the application a part of system.slice. 
Instead the application should be in app.slice that is a child of 
user@1000.service. Inspect output of systemd-cgls.


So systemd-run should talk to the systemd --user instance. I have tried 
to set


XDG_RUNTIME_DIR="/run/user/1000" 
BUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"


in setpriv ... env, but systemd requires authentication.

It seems neither su nor sudo add process to the user context (proper 
cgroup, XDG session), so attempts to talk to the systemd user session 
through D-Bus fail.


I tried command from a ssh session root@... Behavior may be different 
from suspend/resume tasks since the session is associated with a pty.




Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread Greg Wooledge
On Sat, Jan 06, 2024 at 02:57:53AM -0600, Nate Bargmann wrote:
> I really don't get the fascination with some city hundreds of miles
> distant defining the time zone.  Why Chicago for US/Central?  There are
> any number of cities in US/Central that could be referenced, but no,
> pick the most notorious one--rolls eyes.

 is the only page I've
ever found that EXPLAINS things properly.  I strongly recommend it.

Among other things, it says:

 * Use the most populous among locations in a region, e.g., prefer
   Asia/Shanghai to Asia/Beijing. Among locations with similar populations,
   pick the best-known location, e.g., prefer Europe/Rome to Europe/Milan.

So, it's based on population and fame.



Re: was: Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread John Hasler
The documentation for Chrony is:

chrony.conf (5)  - chronyd configuration file
chronyc (1)  - command-line interface for chrony daemon
chronyd (8)  - chrony daemon

Also see /usr/share/doc/chrony .

Don't use "pool" to sync to a single source.  Use  "server".

man chrony.conf


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



Status of ISC Stork (monitoring daemon to ISC Kea) in Debian

2024-01-06 Thread Ralph Aichinger
Hi everybody!

Normally I am quite good at finding out if and why not something is
packaged in Debian, but I have not found any information about ISC
Stork, basically an optional accessory to ISC Kea. 

While migrating to Kea from ISC dhcpd, I noticed that this component is
not packaged Or have I overlooked it? Now I am not sure it is useful at
all to me, but out of curiosity, is it a licensing thing? Is it not
that useful in practice?
License seems to be a rather standard MPL.

Anybody using Kea DHCP with opinion on Stork? Is it worth the bother to
install the version from upstream manually?

Liebe Grüße,
Ralph Aichinger



Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-06 Thread Albretch Mueller
 Sorry, but I don't think I am making much sense out those reported errors.
 I may not even have an NVMe card in my computer as the manufacturer claims.
 lbrtchx



Re: Change suspend type from kde menu

2024-01-06 Thread Valerio Vanni

Il 06/01/2024 01:04, Greg Wooledge ha scritto:

On Fri, Jan 05, 2024 at 11:37:41PM +0100, Valerio Vanni wrote:

This way works, I don't know if it has security flaws.

systemd-run --unit=kaffeine-resumed setpriv --reuid "$kafuid" --regid
"$kafgid" --init-groups  --reset-env \
   env XDG_RUNTIME_DIR=/run/user/"$kafuid" $kafdis
XDG_CURRENT_DESKTOP=KDE \
   /usr/bin/kaffeine --lastchannel > /dev/null 2>&1



systemd-run(1) appears to have its own --uid and --gid options.  If
you can live without supplementary groups and the variables that are
set by --reset-env, you can probably drop the setpriv part and just use
systemd-run's --uid and --gid.

On the other hand, if it ain't broke


I tried the options when I tried systemd-run, but it didn't work.
I only added them, but now I see that you have to choose: or them or 
setpriv.


Now it's:

systemd-run --unit=kaffeine-resumed --uid="$kafuid" --gid="$kafgid" \
  env XDG_RUNTIME_DIR=/run/user/"$kafuid" $kafdis 
XDG_CURRENT_DESKTOP=KDE \

  /usr/bin/kaffeine --lastchannel > /dev/null 2>&1

Outcome is the same.

The only difference is that a line is added to syslog about unit creation:
Started kaffeine-resumed.service - /usr/bin/env 
XDG_RUNTIME_DIR=/run/user/1000 DISPLAY=:0 XDG_CURRENT_DESKTOP=KDE 
/usr/bin/kaffeine --lastchannel.




Re: reinstallation and restore after catastrophic mistake or failure; was: 1 Currently unreadable (pending) sectors How worried should I be?

2024-01-06 Thread Michael Kjörling
On 6 Jan 2024 00:37 -0800, from dpchr...@holgerdanske.com (David Christensen):
> I suggest taking an image (backup) with dd(1), Clonezilla, etc., when you're
> done.  This will allow you to restore the image later -- to roll-back a
> change you do not like, to recovery from a disaster, to clone the image to
> another device, to facilitate experiments, (such as doing a secure erase to
> see if it resolves the SSD pending sector issue), etc..
> 
> If you also keep your system configuration files in a version control
> system, restoring an image is faster than wipe/ fresh install/ configure/
> restore data.

I would go even farther. Backups should be designed such that
recovering from a catastrophic storage failure, such as getting hit by
ransomware, unintentionally doing a destructive badblocks write test
or the sudden failure of a storage device, is possible by at most
something very similar to:

* Boot some kind of live environment
* Set up file systems on the storage device to be restored onto
  (partitioning, setting up LUKS containers, formatting, whatever else
  might be called for)
* Within the live environment, install and configure the software
  needed to access the backup (if any) (this may include things like
  cryptographic keys, access passphrases and the likes)
* Perform the restoration from the most recent backup (this is the
  part that likely will take a significant amount of time)
* Update the restored copies of /etc/fstab, /etc/crypttab and any
  other files that directly reference the partitions or file systems
  by some kind of ID (UUID, /dev/disk/by-*/*, ...)
* Reinstall the boot loader
* Reboot
* Reinstall the boot loader again from within the restored environment
  to ensure that everything relating to it is in sync

Such recovery should _not_ need to involve significant reconfiguration
of anything. Any such requirements will massively increase your time
to recovery, as I think we're seeing an example of here. And yes,
pretty much all of this could be scripted, but I strongly suspect that
few people need to do a bare-metal restore of their most recent backup
often enough for _that_ to be worth the effort to create and maintain.

Which is not to say that keeping configuration files
version-controlled cannot provide benefits anyway; but given a proper,
frequent backup regime, the benefits even of that are reduced.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”



Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread gene heskett

On 1/6/24 04:15, Nate Bargmann wrote:

* On 2024 06 Jan 01:00 -0600, Max Nikulin wrote:

US/Eastern & Co has been moved to tzdata-legacy as well. Currently used
identifiers are based on cities: America/New_York.


Ugghhh!

I guess I'll be going to the legacy package then until
$WHOEVER_IS_IN_CHARGE issues a decree that it too shall be eliminated.
I really don't get the fascination with some city hundreds of miles
distant defining the time zone.  Why Chicago for US/Central?  There are
any number of cities in US/Central that could be referenced, but no,
pick the most notorious one--rolls eyes.

I could even accept America/Central without complaint.  Yeah, US is a
directory and Central is a symlink to ../America/Chicago that could be
manually added to a system if need be.

Ambles off shaking fist at a cloud...

You got company on that trail.


- Nate



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



was: Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread gene heskett

On 1/6/24 01:18, Max Nikulin wrote:

On 06/01/2024 12:18, gene heskett wrote:

On 1/5/24 23:29, Greg Wooledge wrote:

On Fri, Jan 05, 2024 at 09:01:29PM -0500, Charles Kroeger wrote:

tzdata (2023d-1) unstable; urgency=medium

 upstream backward file) were moved to tzdata-legacy. This 
includes the



What's wrong with NTP, too simple?


NTP and tzdata have nothing to do with each other.


I see no relation to NTP as well. Somebody decided that 
/usr/share/zoneinfo is full of garbage and needs clean up:


https://lists.ubuntu.com/archives/ubuntu-devel/2023-January/042405.html

Some people prefer to not have tzdata at all:

https://fedoraproject.org/wiki/Changes/AllowRemovalOfTzdata

I do not live in one of those special locations so I assume it won't 
affect me, but there is a small percentage here and in many other 
country's that live in locations that don't follow DST for some reason. 


DST is unrelated as well.

The change affects those who rely on POSIX-like EST5EDT timezones or on 
obsolete ones like Europe/Kyiv (recently renamed from Europe/Kiev). 
Those who provides various calendar services have significant 
probability to face user issues.


Doesn't this change affect trixie while bookworm will stick to current 
package style?



.
Well, since /usr/share/zoneinfo/UTC is a link to 
/usr/share/zoneinfo/Etc/UTC now, it would save about 4 megabytes worth 
of duplicates and links that is an organizational mess for the 
maintainer now. On the face of it. 25 years overdue? Put all system 
clocks on UTC, and then /etc/timezone is the actual string specifying 
the local offset. No doubt some user confusion, but overall a lot simpler.


Related subject:
Since I have several machines on my local network here, I've just been 
thru hell trying to get them all on the same page, and with debian 
version of ntpsec being happy with a single pool entry pointing to the 
ntpsec on this machine, it foiled my plans to reduce the load on the 
debian server pool by making this machine a stratum 2 server as some, 
not all, of the armbian boxes fail to sync at all with only one pool entry.


Or I'm still doing it wrong, always a possibility. If someone knows how 
to reliably sync to a single pool entry, I'm all ears.


Or, if someone know how to make systemd's timesyncd actually work, I've 
not been able to do that on 7 machines here, that would be appreciated 
too.  Lack of documentation (man pages) for that puppy is a major 
blockaid here on bookworm.  To me, its a potential solution in search of 
a problem that with chrony or ntpsec working, doesn't exist. chrony also 
claims to be an ntp server lookalike, again lack of docs to make it work 
are the problem. If docs on chrony exist, where the heck are they?  And 
what file utility do we have to read them with that actually works?.

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



Re: Generar un fstab borrado por accidente

2024-01-06 Thread Angel Abad
On Fri, Jan 05, 2024 at 03:21:26PM -0500, judedi sago wrote:
> Buenas noches ...
> Como Generar un fstab borrado por accidente.

Buenas, igual puedes usar la herramienta de arch linux genfstab[1], que te 
genera
un fstab con los volumenes montados en ese momento, puedes encontrarlo en el
paquete debian arch-install-scripts[2]

[1] https://wiki.archlinux.org/title/Genfstab
[2] https://packages.debian.org/bookworm/arch-install-scripts

Un saludo!


signature.asc
Description: PGP signature


Re: Debian on Asus X205TA [Was: Re: Installing Debian on an old Asus EEE PC]

2024-01-06 Thread Andrew M.A. Cater
On Sat, Jan 06, 2024 at 10:46:56AM +0100, Leandro Noferini wrote:
> Hans  writes:
> 
> [...]
> 
> > Most important: It can run all debian things (and more), but note, the
> > EEEPC is 32-bit, so you need the 32-bit version of debian.
> 
> In my Asus EEEPC (X205TA) the bios/uefi is 32 bit but the processor is
> 64 so you need only the grub 32 bit but the remaining of the operative
> system, including kernel, is 64 bit.
> 
> An example of guide: https://wiki.archlinux.org/title/ASUS_x205ta
> 
> --
> Ciao
> leandro
>

Debian's amd64 install media should deal with this properly now.

The appropriate files are there to do this - whereas once upon a time
it would have been multi-arch.

Fixed by Steve McIntyre a while ago.

Andy 



Re: NFS: IPV6

2024-01-06 Thread Leandro Noferini
Pocket  writes:

[...]

> I am in the process of re-configuring NFS for V4 only.

Could it be there is some misunderstanding?

IPV4 and IPV6 are quite different concepts from NFSv4: I think this
works either on IPV4 and IPV6.

--
Ciao
leandro



Re: Debian on Asus X205TA [Was: Re: Installing Debian on an old Asus EEE PC]

2024-01-06 Thread Marco Moock
Am 06.01.2024 um 10:46:56 Uhr schrieb Leandro Noferini:

> In my Asus EEEPC (X205TA) the bios/uefi is 32 bit but the processor is
> 64 so you need only the grub 32 bit but the remaining of the operative
> system, including kernel, is 64 bit.

There was another thread (maybe on debian-users-german?) discussing
that and Debian 12 doesn't ship multiarch installers, so it will be a
bit harder to make it work with 32 bit UEFI.



Debian on Asus X205TA [Was: Re: Installing Debian on an old Asus EEE PC]

2024-01-06 Thread Leandro Noferini
Hans  writes:

[...]

> Most important: It can run all debian things (and more), but note, the
> EEEPC is 32-bit, so you need the 32-bit version of debian.

In my Asus EEEPC (X205TA) the bios/uefi is 32 bit but the processor is
64 so you need only the grub 32 bit but the remaining of the operative
system, including kernel, is 64 bit.

An example of guide: https://wiki.archlinux.org/title/ASUS_x205ta

--
Ciao
leandro



Re: tzdata-legacy [was: Re: systemd and timezone]

2024-01-06 Thread Nate Bargmann
* On 2024 06 Jan 01:00 -0600, Max Nikulin wrote:
> US/Eastern & Co has been moved to tzdata-legacy as well. Currently used
> identifiers are based on cities: America/New_York.

Ugghhh!

I guess I'll be going to the legacy package then until
$WHOEVER_IS_IN_CHARGE issues a decree that it too shall be eliminated.
I really don't get the fascination with some city hundreds of miles
distant defining the time zone.  Why Chicago for US/Central?  There are
any number of cities in US/Central that could be referenced, but no,
pick the most notorious one--rolls eyes.

I could even accept America/Central without complaint.  Yeah, US is a
directory and Central is a symlink to ../America/Chicago that could be
manually added to a system if need be.

Ambles off shaking fist at a cloud...

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature


Re: tecles mortes en aplicacions GTK

2024-01-06 Thread Narcis Garcia

El 5/1/24 a les 16:23, Carles Pina i Estany ha escrit:

Afegiria que, amb Bullseye, ho vaig intentar canviar perquè em
molestava. I llavors tenia problemes quan canviava entre teclat català i
britànic (i en aquella època feia una mica de rus i també el tenia, però
això no em cal ara :-) )


Compte que el teclat català no existeix; si un dia s'arriba a fabricar, 
tothom qui s'ha configurat un ordinador seleccionant el teclat com a 
«català» podrà tenir problemes perquè la simulació actual és espanyol.


--

Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should remove and omit any @, dot and mailto combinations against 
automated addresses collectors.




Re: 1 Currently unreadable (pending) sectors How worried should I be?

2024-01-06 Thread David Christensen

On 1/5/24 21:10, Charles Curley wrote:

On Fri, 5 Jan 2024 17:25:48 -0800
David Christensen  wrote:


I would be curious to know if a secure erase forces the pending
sector issue and, if so, what the result is.


An interesting thought. Alas, I am far enough along on re-installing
that I do not want to try it. Sorry.



I suggest taking an image (backup) with dd(1), Clonezilla, etc., when 
you're done.  This will allow you to restore the image later -- to 
roll-back a change you do not like, to recovery from a disaster, to 
clone the image to another device, to facilitate experiments, (such as 
doing a secure erase to see if it resolves the SSD pending sector 
issue), etc..



If you also keep your system configuration files in a version control 
system, restoring an image is faster than wipe/ fresh install/ 
configure/ restore data.



David




Re: dmesg reporting lots of errors apparently emanating from a Realtek RTL810xE PCI Express Fast Ethernet controller ...

2024-01-06 Thread Albretch Mueller
On 1/6/24, Jeffrey Walton  wrote:
> Before going down the rabbit hole, I would:
>
>   2. use a new [known good] ethernet cable

 I am not even using a cable!

>There is another discussion of PCI AER at
>.
>You might find something of interest in it.

 Thank you I spent some time going over their discussions which in two
cases were pretty similar to my problem and I decided to post my
problem:

 
https://forums.developer.nvidia.com/t/dmesg-reporting-lots-of-errors-apparently-relating-to-my-nvidia-card-and-realtek-rtl810xe-pci-express-fast-ethernet-controller/278001

 I will let you know how it went.

 lbrtchx