Re: partition reporting full, but not

[tomas]

On Wed, Feb 21, 2024 at 12:21:05PM +1100, Keith Bainbridge wrote:
> 
> On 21/2/24 10:47, Felix Miata wrote:
> > I didn't think so, which begs the question why OP Keith is using it. :p
> > -- 
> 
> I read somewhere about 2 years ago,  that it automagically de-duped data
> when it detected I was copying the same file to different directories [...]

I think the Wikipedia [1] is a good ref, at least at the level we are
discussing. 

Deduplication is mentioned there requiring userspace tools, so it seems
you'll have to run a process (as a daemon, from cron, whatever) to achieve
that.

It also mentions "reflinks", which is a kind of COW file copy (not to be
confused with a hardlink, which all civilised file systems have).

Cheers
[1] https://en.wikipedia.org/wiki/Btrfs#List_of_features
-- 
t


signature.asc
Description: PGP signature

Re: partition reporting full, but not

[Keith Bainbridge]

On 21/2/24 10:47, Felix Miata wrote:

I didn't think so, which begs the question why OP Keith is using it. :p
--


I read somewhere about 2 years ago,  that it automagically de-duped data 
when it detected I was copying the same file to different directories. 
It's not deliberate, but I have often found copies of my files amongst 
files I have backed up for my wife (where I have put copies of my 
important stuff occasionally.And more common if I rsync a usb to a 
new destination - the usb I use at a volunteer job with portable apps on 
a foreign PC.   I found what I think was that article the other week; 
and it now talks about a manual process to de-dupe the data. I don't 
believe I could have skipped the most important paragraph in the 
article. I prefer rdfind -makehardlinks.Writing to btrfs feels 
quicker than ext4


But why use btrfs on a system partition. I like to try new stuff. Like I 
get a nagging thought of trying arch linux regularly. I resist 
mostly..   I should use sid as my daily driver, but I'm not good at 
asking for help; and I get the feeling that some people here would want 
to tell me something like 'I made my bed, lay in it.'



 So I make do with using developer versions of firefox & thunderbird 
and beta libreOffice (24.02 I think) They are on a separate partition 
from my system.


--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
+61 (0)447 667 468

UTC + 10:00

Re: partition reporting full, but not

[Felix Miata]

Keith Bainbridge composed on 2024-02-21 11:57 (UTC+1100):
 
> Felix Miata wrote:

>> A current thread from elsewhere that should be helpful:
>> > really-the-solution/172576>
 
>>  btrfs filesystem usage /
>>  snapper list
>>  btrfs qgroup show /
 
> Thanks for the prompt, Felix
 
>>> sudo btrfs filesystem usage /
> [sudo] password for root:
> Overall:
>  Device size:   70.00GiB   = remember I expanded this 
> partition 
> yesterday 

How? Did you resize the filesystem too?

-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: partition reporting full, but not

[Keith Bainbridge]

On 21/2/24 11:38, Felix Miata wrote:

A current thread from elsewhere that should be helpful:



btrfs filesystem usage /
snapper list
btrfs qgroup show /


Thanks for the prompt, Felix

  >> sudo btrfs filesystem usage /
[sudo] password for root:
Overall:
Device size:		  70.00GiB   = remember I expanded this partition 
yesterday

Device allocated: 35.82GiB
Device unallocated:   34.18GiB
Device missing:  0.00B
Device slack:0.00B
Used: 34.30GiB
Free (estimated): 34.90GiB  (min: 17.81GiB)
Free (statfs, df):34.90GiB
Data ratio:   1.00
Metadata ratio:   2.00
Global reserve:   71.69MiB  (used: 0.00B)
Multiple profiles:  no

Data,single: Size:32.80GiB, Used:32.09GiB (97.82%)
   /dev/sda3  32.80GiB

Metadata,DUP: Size:1.50GiB, Used:1.11GiB (73.77%)
   /dev/sda3   3.00GiB

System,DUP: Size:8.00MiB, Used:16.00KiB (0.20%)
   /dev/sda3  16.00MiB

Unallocated:
   /dev/sda3  34.18GiB
keith@dell0 $

 Wed 21Feb2024@11:44:26
 :~

At least I can make sense from some of these output numbers

  >> sudo btrfs qgroup show /
ERROR: can't list qgroups: quotas not enabled
keith@dell0 $

 Wed 21Feb2024@11:47:13
 :~

installed snapper and
   >> sudo snapper list
The config 'root' does not exist. Likely snapper is not configured.
See 'man snapper' for further instructions.
keith@dell0 $

More to learn about, I see


--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
+61 (0)447 667 468

UTC + 10:00

Re: Determining which file is at a given LBA offset; was: HDD error: Current_Pending_Sector

[Default User]

On Tue, 2024-02-20 at 21:36 +, Michael Kjörling wrote:
> On 20 Feb 2024 12:51 -0500, from hunguponcont...@gmail.com (Default
> User):
> > But since the sector already can not be read, How can it be re-
> > written
> > to a "good" sector?
> 
> Generally, it can't. It will be remapped if necessary when something
> else is written to that sector.
> 
> 
> > If I knew which file (if any) is using the bad sector, I could try
> > just
> > deleting that file from the "bad" drive, then copy the same file
> > over
> > from the "Good" drive, at which time the bad sector "should" be
> > retired, and replaced by a good sector.
> 
> Assuming ext[234]fs, it looks like you can use tune2fs, udisks and
> debugfs to determine the pathname to the file at a given LBA offset.
> See
> http://www.randomnoun.com/wp/2013/09/12/determining-the-file-at-a-specific-vmdk-offset/
> 



Hi, Michael!

I forgot to say that the filesystem of the "bad" drive is a single
partition, formatted as ext4. And the sector and block sizes both seem
to be 512b.

Per sudo fdisk -l /dev/sdb:


Disk /dev/sdb: 3.64 TiB, 4000752599040 bytes, 7813969920 sectors
Disk model: My Passport 2627
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: ----

Device StartEndSectors  Size Type
/dev/sdb1   2048 7813967871 7813965824  3.6T Linux filesystem
-

Regarding: 
>. . . it looks like you can use tune2fs, udisks and
>debugfs to determine the pathname to the file at a given LBA offset.
>See 
>http://www.randomnoun.com/wp/2013/09/12/determining-the-file-at-a-specific-vmdk-offset/
>that could be a little above my current level of competence. But I
>will try to read up on it.

Note: I occurs to me that another idea would be to simply delete all
files from the "bad" drive, then rsync everything fresh from the "good"
drive back onto the "bad" drive.  

IIUC, that would the cause the "bad" sector to be retired, and replaced
by a "good" sector. 

That might be easier than everything else mentioned so far. 

Re: partition reporting full, but not

[Felix Miata]

to...@tuxteam.de composed on 2024-02-20 09:38 (UTC+0100):

> On Tue, Feb 20, 2024 at 02:42:18AM -0500, Felix Miata wrote:

>> Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):

>>> I just removed 3 snapshots from my daily driver with no change in used 
>>> space reported by df

>> df doesn't know how to calculate freespace on btrfs. You need to be typing

>>  btrfs filesystem df

>> if you have not aliased df to btrfs filesystem df.

> Still, Keith seems to have a real shortage of file system free space,
> otherwise Debian upgrades wouldn't fail.

> I don't know much about btrfs, but what would be really helpful (if
> you do, and it seems so) would be for you to fill us in on how to
> asses the space used up by old snapshots (what seems to be the main
> suspect currently).

A current thread from elsewhere that should be helpful:


btrfs filesystem usage /
snapper list
btrfs qgroup show /

Was requested by a btrfs expert.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: partition reporting full, but not

[Felix Miata]

Greg Wooledge composed on 2024-02-20 14:56 (UTC-0500):

> On Tue, Feb 20, 2024 at 02:47:26PM -0500, Felix Miata wrote:

>> Surely somewhere on debian.org such things must be addressed if Bookworm's 
>> default
>> has also been changed to btrfs.

> That has not happened.  The default file system is still ext4.

I didn't think so, which begs the question why OP Keith is using it. :p
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: HDD error: Current_Pending_Sector

[David]

On Tue, 20 Feb 2024 at 17:51, Default User  wrote:
>
> Hi guys!

Hi to all readers,

> Now it "works", BUT . . .  I ran:
>
> sudo smartctl --test=long /dev/sdb on it,
>
> and it reports a Current_Pending_Sector error, at LBA 325904690.

[...]

> According to sudo smartctl --test=long /dev/sdb,
> there is one Current_Pending_Sector error.
>
> I have done some research online, which seems to say that the error
> will remain until there is an an attempt to write to the bad sector
> (block).  Then it will be "re-mapped", and presumably taken out of
> service.
>
> But since the sector already can not be read, How can it be re-written
> to a "good" sector?
>
> If I knew which file (if any) is using the bad sector, I could try just
> deleting that file from the "bad" drive, then copy the same file over
> from the "Good" drive, at which time the bad sector "should" be
> retired, and replaced by a good sector.
>
> Or, as a more "brute force" solution, I could either simply format the
> bad drive, or do:

[...]

> Any suggestions?

Maybe this document will guide you to a preferred solution:
  https://www.smartmontools.org/wiki/BadBlockHowto

Re: Determining which file is at a given LBA offset; was: HDD error: Current_Pending_Sector

[Michael Kjörling]

On 20 Feb 2024 12:51 -0500, from hunguponcont...@gmail.com (Default User):
> But since the sector already can not be read, How can it be re-written
> to a "good" sector?

Generally, it can't. It will be remapped if necessary when something
else is written to that sector.


> If I knew which file (if any) is using the bad sector, I could try just
> deleting that file from the "bad" drive, then copy the same file over
> from the "Good" drive, at which time the bad sector "should" be
> retired, and replaced by a good sector.

Assuming ext[234]fs, it looks like you can use tune2fs, udisks and
debugfs to determine the pathname to the file at a given LBA offset.
See 
http://www.randomnoun.com/wp/2013/09/12/determining-the-file-at-a-specific-vmdk-offset/

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

Guacamole/freerdp2 issue

[Horváth Csaba]

Hi,

I was using Guacamole with VNC until i switched on my main computer to
Debian+Gnome (testing), which provides excellent RDP connection. The
RDP is working from Windows, and other Debian computers, but not from
Guacamole. Guacamole is running on my home server, and i also
installed a Debian test VM for Guacamole testing. These are a Trixie
and a Bookworm installations. On te home server Guacd is installed
from repo.

So the problem is, that if i try to connect to any Gnome RDP machine
(i have 3 of them) then i got disconnected. The security is set to
NLA, certificates ignored. I got asked for the credentials, and the
the connection stops. This happens with the guacd compiled from source
and installed from .deb package. The Guacamole can connect to SSH,
VNC, and to my Windows VM's via RDP. So Guacamole side is OK.

Did some research, and found that in the logs the problem is visible :
Graphics Pipeline issue. (See logs at the end)
"** (gnome-remote-desktop-daemon:3505237): WARNING **: 21:28:50.436:
[RDP] Client did not advertise support for the Graphics Pipeline,
closing connection"

I suspect a Freerdp2 issue. I tried to connect to the main computer
from a spare one, which is also running Debian Trixie, but with
Gnome-connections, and this is working. I also can connect to my main
one from Windows via RDP. Only not working connection is from
Guacamole to any gnome-rdp-server instance (so my 3 physical computer
with Debian, and Gnome :D ).

Can someone please help to determine where i need to report this, or
does anyone know a solution? I already have asked this on Guacamole
mail list and on the Gnome issue tracker, but nobody knows the
solution. (https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/183)

Thanks for any help :)

Cs.




Logs :
On the remote side (the gnome-rdp-server machine) :
[21:28:49:059] [3505237:3505454] [INFO][com.freerdp.core.connection] -
Client Security: NLA:1 TLS:1 RDP:0
[21:28:49:059] [3505237:3505454] [INFO][com.freerdp.core.connection] -
Server Security: NLA:1 TLS:0 RDP:0
[21:28:49:059] [3505237:3505454] [INFO][com.freerdp.core.connection] -
Negotiated Security: NLA:1 TLS:0 RDP:0
[21:28:49:079] [3505237:3505454] [WARN][com.winpr.negotiate] -
AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[21:28:49:180] [3505237:3505454] [WARN][com.winpr.negotiate] -
AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
[21:28:49:281] [3505237:3505454] [INFO][com.freerdp.core.connection] -
Accepted client: Guacamole RDP
[21:28:49:281] [3505237:3505454] [INFO][com.freerdp.core.connection] -
Accepted channels:
[21:28:49:281] [3505237:3505454] [INFO][com.freerdp.core.connection] -  cliprdr
[21:28:49:281] [3505237:3505454] [INFO][com.freerdp.core.connection] -  rdpdr
[21:28:49:281] [3505237:3505454] [INFO][com.freerdp.core.connection] -  rdpsnd
[21:28:49:281] [3505237:3505454] [INFO][com.freerdp.core.gcc] - Active
rdp encryption level: NONE
[21:28:49:281] [3505237:3505454] [INFO][com.freerdp.core.gcc] -
Selected rdp encryption method: NONE

** (gnome-remote-desktop-daemon:3505237): WARNING **: 21:28:50.436:
[RDP] Client did not advertise support for the Graphics Pipeline,
closing connection
[21:28:50:086] [3505237:3505454] [ERROR][com.freerdp.core.transport] -
transport_check_fds: transport->ReceiveCallback() - -1


On the guacd side (the home server, where the Guacamole is running) :
guacd[42304]: INFO: Guacamole proxy daemon (guacd) version 1.5.4 started
guacd[42304]: INFO: Listening on host 127.0.0.1, port 4822
guacd[42304]: INFO: Creating new client for protocol "rdp"
guacd[42304]: INFO: Connection ID is "$aad7cb82-9521-49eb-8ca1-596d26a3c61a"
guacd[42306]: INFO: Security mode: NLA
guacd[42306]: INFO: Resize method: none
guacd[42306]: INFO: No clipboard line-ending normalization specified.
Defaulting to preserving the format of all line endings.
guacd[42306]: INFO: User "@f7065a55-b9e4-4056-92ef-f1491c59d9d9"
joined connection "$aad7cb82-9521-49eb-8ca1-596d26a3c61a" (1 users now
present)
guacd[42306]: INFO: Loading keymap "base"
guacd[42306]: INFO: Loading keymap "en-us-qwerty"
guacd[42306]: INFO: RDP server closed/refused connection: Server
refused connection (wrong security type?)
guacd[42306]: INFO: User "@f7065a55-b9e4-4056-92ef-f1491c59d9d9"
disconnected (0 users remain)
guacd[42306]: INFO: Last user of connection
"$aad7cb82-9521-49eb-8ca1-596d26a3c61a" disconnected
guacd[42304]: INFO: Connection "$aad7cb82-9521-49eb-8ca1-596d26a3c61a" removed.



Freerdp2 packages installed on my home server, which i normally use as
remote gateway :
libfreerdp-client2-2/stable,now 2.10.0+dfsg1-1 amd64
libfreerdp-server2-2/stable,now 2.10.0+dfsg1-1 amd64
libfreerdp2-2/stable,now 2.10.0+dfsg1-1 amd64



Freerdp2 packages installed on my main computer  which i want to connect to
via Guacamole :
libfreerdp-client2-2/testing,testing,now 2.11.2+dfsg1-1+b1 amd64
libfreerdp-server2-2/testing,testing,now 2.11.2+dfsg1-1+b1 amd64
libfreerdp2-2/testing,testing,now 

Re: sshd Match regel

[Geert Stappers]

On Tue, Feb 20, 2024 at 08:06:22AM +0100, Gijs Hillenius wrote:
> On 19 February 2024 18:26 Rik Theys, wrote:
> 
> > Beste,
> >
> > On Mon, Feb 19, 2024 at 5:53 PM Gijs Hillenius  wrote:
> >
> >>
> >>
> >> Iets als, onderaan sshd_config dit:
> >>
> >> ,
> >> | Match User webcams
> >> | PubkeyAcceptedKeyTypes ssh-rsa,ssh-dss
> >> `
> >>
> >> ssh lijkt dat te willen snappen. Desondanks verschijnt dezelfde
> >> foutmelding in auth.log. De clients bevestigen: "unable to exchange
> >> encryption keys."
> >>
> >> Als ik op de server doe:
> >>
> >> ssh localhost -Q HostKeyAlgorithms
> >>
> >>
> >> daar zie ik toch ssh-dss en ssh-rsa staan.
> >>
> >> Maar ... niet de "oude"?
> >>
> >> Wie heeft een tip
> >>
> >>
> 
> > De -Q optie geeft een lijst van ondersteunde algorithms, daarom niet
> > degene die actief zijn? Ik zou eens proberen met een Match op het IP
> > adres ipv de gebruikersnaam. Mogelijk is de uitwisseling van de
> > gebruikersnaam pas na het tot stand komen van de encryptie?
> 
> Ow! dank voor het meedenken, dat helpt.
> 
> Idd, ik zie in de ssh logs niet die username.
> 
> Maar
> 
> ,
> | Match Address 192.168.123.42
> |   PubkeyAcceptedKeyTypes ssh-rsa,ssh-dss
> `
> 
> geeft helaas dezelfde melding in de log.
> 


   sudo /usr/sbin/sshd -d



Voor een beter bericht heb ik nu geen tijd.




Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Booten vanaf USB steeds trager

[Geert Stappers]

On Tue, Feb 20, 2024 at 09:31:02AM +0100, Paul van der Vlis wrote:
> Hallo,
> 
> Ik heb een setup waarbij ik boot vanaf USB met grub. Het valt me op dat dit
> steeds trager wordt, op dezelfde machine:
> 
> Debian10:  18 seconden
> Debian11:  60 seconden
> Debian12:  ruim 120 seconden
> 
> Wat vooral lang duurt is "loading initial ramdisk", het lichtje is dan reuze
> hard aan het knipperen. Het gaat verder allemaal wel goed.
> 
> Op een snellere machine is het wel wat sneller, maar het blijft onacceptabel
> traag.
> 
> Ik heb ook al de kernel-optie "debug" gegeven, dan maakt initramfs een log.
> Maar omdat er geen tijden bij staan zegt het me weinig over wat nu zo lang
> duurt. Dmesg geeft wel tijden, maar ik kom er niet uit.
> 
> Ik zie hetzelfde ook op andere machines. Overigens niet bij een Debian
> installer of livestick, dat gaat wel goed. Maar als ik echt Debian
> installeer op een USB device start het traag, dezelfde SSD aan SATA gaat wel
> goed. Ik heb al verschillende USB naar SATA kabels geprobeerd, maar dat
> lijkt ook niet het probleem.
> 
> Hebben jullie ideeën hoe ik dit booten vanaf USB sneller krijg?

Ja, ik heb wel een idee.
En dat idee wil ik ruilen voor de output van `ls -l /boot`
op de getestde versies.


 
> Groet,
> Paul


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: partition reporting full, but not

[Greg Wooledge]

On Tue, Feb 20, 2024 at 02:47:26PM -0500, Felix Miata wrote:
> Surely somewhere on debian.org such things must be addressed if Bookworm's 
> default
> has also been changed to btrfs.

That has not happened.  The default file system is still ext4.

Re: partition reporting full, but not

[Felix Miata]

to...@tuxteam.de composed on 2024-02-20 09:38 (UTC+0100):

> On Tue, Feb 20, 2024 at 02:42:18AM -0500, Felix Miata wrote:

>> Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):

>> > I just removed 3 snapshots from my daily driver with no change in used 
>> > space reported by df

>> df doesn't know how to calculate freespace on btrfs. You need to be typing

>>  btrfs filesystem df

>> if you have not aliased df to btrfs filesystem df.

> Still, Keith seems to have a real shortage of file system free space,
> otherwise Debian upgrades wouldn't fail.

> I don't know much about btrfs, but what would be really helpful (if
> you do, and it seems so) would be for you to fill us in on how to
> asses the space used up by old snapshots (what seems to be the main
> suspect currently).

My hands-on experience with btrfs is limited to one laptop my brother gave me 
with
openSUSE installed that I only boot 2-3 times per year. My mentioning of the 
btrfs
command in this thread is based upon years of frequenting openSUSE and Fedora
mailing lists and forums. openSUSE made btrfs its default filesystem somewhere
around 7-8 years ago. I think Fedora made btrfs default more recently. Google &
DDG should be able to provide much better help than I on how to interpret btrfs
command output. So should supp...@lists.opensuse.org and
https://forums.opensuse.org/c/english/install-boot-login/18 and the comparable
Fedora forums. My own Gnu/Linux installations, other than Knoppix, have always
been on extX.

I suggest Keith's 36G / partition size must be a marginal for btrfs use. IIRC, 
40G
may be the officially suggested minimum size for an openSUSE btrfs / filesystem
where /home/ is on a separate (xfs) filesystem. Keith has /home/ within /.

Surely somewhere on debian.org such things must be addressed if Bookworm's 
default
has also been changed to btrfs.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: Comment remplacer l'utilisateur root pour utiliser le service cron ?

[Bernard Bass]

L'utilisateur gestionnaire est créé.



Identifier l'utilisateur qui fait tourner le service cron :
ps -Af | grep cron
root 890   1  0 20:21 ?    00:00:00 /usr/sbin/cron -f -P

sudo systemctl stop cron

cd /usr/sbin/
ls -la
-rwxr-xr-x  1 root root 51792 mars  23  2022 cron

sudo bash
*chown gestionnaire:gestionnaire cron*
cd /usr/sbin/
ls -la
-rwxr-xr-x  1 *root gestionnaire*   51792 mars  23  2022 cron

sudo systemctl restart cron

ps -Af | grep cron
*root*    5315   1  0 20:38 ?    00:00:00 /usr/sbin/cron -f -P


C'est toujours l'utilisateur *root* qui *fait tourner le service cron*.
L'ID de l'utilisateur gestionnaire avec l'option d'*ID utilisateur non 
unique* est *0 (root)*.




Le 20/02/2024 à 12:26, Bernard Bass a écrit :
La question initiale : Comment remplacer l'utilisateur root pour 
utiliser le service cron ?


Devrait plutôt être : *Comment lancer le service cron/crontab avec 
l'utilisateur gestionnaire (root) ?*


J'ai créé l'utilisateur gestionnaire de la sorte :

Créer un utilisateur gestionnaire pour remplacer les actions de 
l'utilisateur root, pour lancer toutes les tâches cron.


Consulter les groupes de l'utilisateur root :
sudo bash
id
uid=0(root) gid=0(root) groupes=0(root)

groups
root

Créer l'utilisateur gestionnaire :
*sudo adduser gestionnaire*

Ajouter l'utilisateur gestionnaire au groupe des administrateurs 
système (root) à l'aide de la commande usermod :

# usermod -aG sudo gestionnaire
*sudo usermod -aG root gestionnaire*

Ajouter les droits root à l'utilisateur gestionnaire avec visudo :
*sudo visudo
root    ALL=(ALL:ALL) ALL
gestionnaire    ALL=(ALL:ALL) ALL
*
sudo bash
cat /etc/passwd | grep -i gestionnaire
gestionnaire:x:1001:1001:,,,:/home/gestionnaire:/bin/bash

sudo bash
Donner à l'utilisateur gestionnaire les privilèges root sans qu'il 
n'ait a utiliser sudo :
Changer l'ID de l'utilisateur gestionnaire avec l'option d'ID 
utilisateur non unique :

*usermod -o -u 0 gestionnaire*

Utiliser su pour s'identifier avec l'utilisateur gestionnaire et 
devenir root :

$ *su gestionnaire*
Mot de passe :
*root*@system:/home/utilisateur-courant#

cat /etc/passwd | grep -i gestionnaire
gestionnaire:x:0:1001:,,,:/home/gestionnaire:/bin/bash

La ligne peut être réécrite de la façon suivante :
sudo nano /etc/passwd
gestionnaire:x:0:1001:Gestionnaire:/home/gestionnaire:/bin/bash


Je n'ai pas trouvé comment relancer le service cron avec cet autre 
utilisateur gestionnaire.



*La solution fonctionnelle pour désactiver root semble être la 
suivante :*



1)
sudo passwd root # Créer un mot de passe.
sudo passwd -d root # Supprimer le mot de passe.


2)
* Désactiver l'utilisateur root à partir du shell.
Le moyen le plus simple de désactiver la connexion de l'utilisateur 
root est de changer son shell du répertoire /bin/bash à 
/sbin/nologin, dans le fichier /etc/passwd.


sudo nano /etc/passwd
root:x:0:0:root:/root:/sbin/nologin


3)
sudo passwd -S root
root NP 02/18/2024 0 9 7 -1 # L'utilisateur root utilise no password.


4)
su root
This account is currently not available.


5)
On ne peut donc pas accéder à root directement.
Le système cron avec la crontab -e root continue de fonctionner.
Le user root semble faire son travail sans erreur.



J'aurais préféré créer un utilisateur gestionnaire pour remplacer les 
actions de l'utilisateur root, capable de lancer toutes les tâches cron.

Si quelqu'un sait expliquer la méthode.
Merci.

Re: HDD error: Current_Pending_Sector

[David Christensen]

On 2/20/24 09:51, Default User wrote:

Hi guys!

I am running Debian 12 Stable, up to date, on a low-spec Dell Inspiron
15 3000 Model 3511. Firmware is also up to date.

I have a 4 Gb Western Digital external usb SATA HDD, Model WDC
WD40NDZW-11A8JS1.  It has only one partition, formatted as ext4. The
filesystem is labeled MSD00012.

Every night, I use rsync to copy all contents of a (theoretically)
identical drive, which has filesystem label MSD00014, to the drive with
MSD00012.

Two nights ago, I could not do the copy correctly.  Apparently, as a
safety measure, MSD00012 was automatically re-mounted as read only, due
to a filesystem error.

I used the gnome-disks utility to unmount and then remount it. It was
remounted as read-write.

Now it "works", BUT . . .  I ran:

sudo smartctl --test=long /dev/sdb on it,

and it reports a Current_Pending_Sector error, at LBA 325904690.


From sudo smartctl --all /dev/sdb > backup_drive_b_test.txt:




smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-18-amd64] (local
build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke,
www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Elements / My Passport (USB, AF)
Device Model: WDC WD40NDZW-11A8JS1
Serial Number:WD-
LU WWN Device Id: 5 0014ee 269112168
Firmware Version: 01.01A01
User Capacity:4,000,753,475,584 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate:5400 rpm
Form Factor:  2.5 inches
TRIM Command: Available, deterministic
Device is:In smartctl database 7.3/5319
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Tue Feb 20 11:32:04 2024 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection
activity
was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status:  ( 121) The previous self-test
completed having
the read element of the test
failed.
Total time to complete Offline
data collection:(12240) seconds.
Offline data collection
capabilities:(0x1b) SMART execute Offline
immediate.
Auto Offline data collection
on/off support.
Suspend Offline collection
upon new
command.
Offline surface scan
supported.
Self-test supported.
No Conveyance Self-test
supported.
No Selective Self-test
supported.
SMART capabilities:(0x0003) Saves SMART data before
entering
power-saving mode.
Supports SMART auto save
timer.
Error logging capability:(0x01) Error logging supported.
General Purpose Logging
supported.
Short self-test routine
recommended polling time:(   2) minutes.
Extended self-test routine
recommended polling time:(  24) minutes.
SCT capabilities:  (0x30b5) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
   1 Raw_Read_Error_Rate 0x002f   200   198   051Pre-fail
Always   -   41
   3 Spin_Up_Time0x0027   253   253   021Pre-fail
Always   -   4741
   4 Start_Stop_Count0x0032   099   099   000Old_age
Always   -   1175
   5 Reallocated_Sector_Ct   0x0033   200   200   140Pre-fail
Always   -   0
   7 Seek_Error_Rate 0x002e   200   200   000Old_age
Always   -   0
   9 Power_On_Hours  0x0032   099   099   000Old_age
Always   -   1311
  10 Spin_Retry_Count0x0032   100   100   000Old_age
Always   -   0
  11 Calibration_Retry_Count 0x0032   100   100   000Old_age
Always   -   0
  12 Power_Cycle_Count   0x0032   100   100   000Old_age
Always   -   693
192 Power-Off_Retract_Count 0x0032   200   200   000Old_age
Always   -   23
193 Load_Cycle_Count0x0032   199   199   000Old_age
Always   -   3045
194 Temperature_Celsius 0x0022   114   102   000Old_age

Re: Re: GRUB lost graphical terminal mode

[Borden]

>On 19 Feb 2024 22:44 +0100, from borde...@tutanota.com (Borden):
>>> Would you be willing to post your /boot/grub/grub.cfg for a setup
>>> where you get the blank screen GRUB?
>> 
>> Yeah, I probably should have opened with that. Sorry:
>> 
>> ```
>> # If you change this file, run 'update-grub' afterwards to update
>> # /boot/grub/grub.cfg.
>> # For full documentation of the options in this file, see:
>> #   info -f grub -n 'Simple configuration'
>> 
>> GRUB_DEFAULT=0
>[snipped remainder]
>
>If that's your /boot/grub/grub.cfg, it's a miracle that your GRUB
>installation is working at all and not dumping you to a grub> rescue
>prompt.

Right you are. I forget that there's a /boot/grub/grub.cfg file because I 
always edit /etc/default/grub . This is what you're looking for, I hope:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod btrfs
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  #Redacted UUID#
else
  search --no-floppy --fs-uuid --set=root #Redacted UUID#
fi
    font="/@rootfs/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_CA
  insmod gettext
fi
terminal_input gfxterm
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod btrfs
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  #Redacted UUID#
else
  search --no-floppy --fs-uuid --set=root #Redacted UUID#
fi
insmod png
if background_image 
/@rootfs/usr/share/desktop-base/emerald-theme/grub/grub-16x9.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_dark_theme ###
set menu_color_normal=white/black
set menu_color_highlight=yellow/black
set color_normal=white/black
set color_highlight=yellow/black
background_image
### END /etc/grub.d/06_dark_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 'gnulinux-simple-#Redacted UUID#' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod btrfs
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  #Redacted UUID#
else
  search --no-floppy --fs-uuid --set=root #Redacted UUID#
fi
echo'Loading Linux 6.6.15-amd64 ...'
linux   /@rootfs/boot/vmlinuz-6.6.15-amd64 root=UUID=#Redacted UUID# ro 
rootflags=subvol=@rootfs  
echo'Loading initial ramdisk ...'
initrd  /@rootfs/boot/initrd.img-6.6.15-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-#Redacted UUID#' {
menuentry 'Debian GNU/Linux, with Linux 6.6.15-amd64' --class debian --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-6.6.15-amd64-advanced-#Redacted UUID#' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod btrfs
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search 

HDD error: Current_Pending_Sector

[Default User]

Hi guys! 

I am running Debian 12 Stable, up to date, on a low-spec Dell Inspiron
15 3000 Model 3511. Firmware is also up to date.

I have a 4 Gb Western Digital external usb SATA HDD, Model WDC
WD40NDZW-11A8JS1.  It has only one partition, formatted as ext4. The
filesystem is labeled MSD00012. 

Every night, I use rsync to copy all contents of a (theoretically)
identical drive, which has filesystem label MSD00014, to the drive with
MSD00012. 

Two nights ago, I could not do the copy correctly.  Apparently, as a
safety measure, MSD00012 was automatically re-mounted as read only, due
to a filesystem error.  

I used the gnome-disks utility to unmount and then remount it. It was
remounted as read-write. 

Now it "works", BUT . . .  I ran: 

sudo smartctl --test=long /dev/sdb on it, 

and it reports a Current_Pending_Sector error, at LBA 325904690. 

>From sudo smartctl --all /dev/sdb > backup_drive_b_test.txt:



smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-18-amd64] (local
build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke,
www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Elements / My Passport (USB, AF)
Device Model: WDC WD40NDZW-11A8JS1
Serial Number:WD-
LU WWN Device Id: 5 0014ee 269112168
Firmware Version: 01.01A01
User Capacity:4,000,753,475,584 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate:5400 rpm
Form Factor:  2.5 inches
TRIM Command: Available, deterministic
Device is:In smartctl database 7.3/5319
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Tue Feb 20 11:32:04 2024 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection
activity
was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status:  ( 121) The previous self-test
completed having
the read element of the test
failed.
Total time to complete Offline 
data collection:(12240) seconds.
Offline data collection
capabilities:(0x1b) SMART execute Offline
immediate.
Auto Offline data collection
on/off support.
Suspend Offline collection
upon new
command.
Offline surface scan
supported.
Self-test supported.
No Conveyance Self-test
supported.
No Selective Self-test
supported.
SMART capabilities:(0x0003) Saves SMART data before
entering
power-saving mode.
Supports SMART auto save
timer.
Error logging capability:(0x01) Error logging supported.
General Purpose Logging
supported.
Short self-test routine 
recommended polling time:(   2) minutes.
Extended self-test routine
recommended polling time:(  24) minutes.
SCT capabilities:  (0x30b5) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE 
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x002f   200   198   051Pre-fail 
Always   -   41
  3 Spin_Up_Time0x0027   253   253   021Pre-fail 
Always   -   4741
  4 Start_Stop_Count0x0032   099   099   000Old_age  
Always   -   1175
  5 Reallocated_Sector_Ct   0x0033   200   200   140Pre-fail 
Always   -   0
  7 Seek_Error_Rate 0x002e   200   200   000Old_age  
Always   -   0
  9 Power_On_Hours  0x0032   099   099   000Old_age  
Always   -   1311
 10 Spin_Retry_Count0x0032   100   100   000Old_age  
Always   -   0
 11 Calibration_Retry_Count 0x0032   100   100   000Old_age  
Always   -   0
 12 Power_Cycle_Count   0x0032   100   100   000Old_age  
Always   -   693
192 Power-Off_Retract_Count 0x0032   200   200   000Old_age  
Always   -   23
193 Load_Cycle_Count0x0032   199   199   000Old_age  
Always   -   3045
194 Temperature_Celsius 0x0022   114   102   000Old_age  
Always   -  

Re: GRUB lost graphical terminal mode

[Charles Curley]

On Tue, 20 Feb 2024 08:04:47 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:

> On 19 Feb 2024 22:44 +0100, from borde...@tutanota.com (Borden):
> >> Would you be willing to post your /boot/grub/grub.cfg for a setup
> >> where you get the blank screen GRUB?  
> > 
> > Yeah, I probably should have opened with that. Sorry:
> > 
> > ```
> > # If you change this file, run 'update-grub' afterwards to update
> > # /boot/grub/grub.cfg.
> > # For full documentation of the options in this file, see:
> > #   info -f grub -n 'Simple configuration'
> > 
> > GRUB_DEFAULT=0  
> [snipped remainder]
> 
> If that's your /boot/grub/grub.cfg, it's a miracle that your GRUB
> installation is working at all and not dumping you to a grub> rescue
> prompt.
> 

That clearly isn't the OP's /boot/grub/grub.cfg, but
/etc/default/grub.

As the former is often rather lengthy, and the list does reject large
attachments, perhaps Borden  will put it up at
https://paste.debian.net or some other pastebin facility and provide
the URL.

-- 
Does anybody read signatures any more?

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

Re: partition reporting full, but not

[debian-user]

Felix Miata  wrote:
> Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):
> 
> > I just removed 3 snapshots from my daily driver with no change in
> > used space reported by df  
> 
> df doesn't know how to calculate freespace on btrfs. You need to be
> typing
> 
>   btrfs filesystem df

df [options] 
   Show a terse summary information about allocation of block
   group types of a given mount point. The original purpose of
   this command was a debugging helper. The output needs to be
   further interpreted and is not suitable for quick overview.


FWIW my root filesystem is btrfs and I use the normal df command all the
time without a problem. I've never used btrfs filesystem df

Re: Erreur nvidia suite upgrade noyau 6.1.0-18 : RÉSOLU

[ajh-valmer]

Ça a été bien long... :-)

J'ai rechargé les drivers Nvidia qui ont été corrigés.

Ensuite un simple :
# apt install linux-image-amd64 linux-headers-amd64
(pioché sur un forum),
plus de messages d'erreur, reboot,
j'ai bien le noyau 6.1.0-18 et mon système graphique opérationnel
comme avec le noyau 6.1.0-17.
Il faut remercier la communauté Debian qui a corrigé le conflit entre
les drivers non-free de Nvidia et le noyau  6.1.0-18.

Merci aussi à tous ceux qui m'ont aidé.

A. Valmer

Re: Erreur nvidia suite upgrade noyau 6.1.0-18

[ajh-valmer]

> Nicolas 
>> Pour passer par les backports j'ai ajouter cette ligne dans 
>> /etc/apt/sources.list
>> deb http://ftp.fr.debian.org/debian/ bookworm-backports main non-free 
>> contrib non-free-firmware

On Tuesday 20 February 2024 10:31:39 Patrick ZAJDA wrote:
> Intéressant que tu dises que ça n'est que pour Sid alors qu'à la fin du 
> bug que tu indiques, c'est clairement dit que c'est dispo pour stable...
> Et je suis sous Bookworm, pas de Sid du tout chez moi ; mon kernel est 
> bien 6.1.0-18. Peut-être que tu devrais revérifier tes listes sources 
> (sources.list et autres dans sources.list.d) et si tu ne ferais pas du 
> pining qui bloquerait quelque chose...
> Utilises-tu apt-listbugs ? J'ai eu quelques surprises par le passé 
> niveau pining :

Je ne sais pas utiliser "apt-listbugs" et c'est quoi "pining" ou "pinning" ?

> > Pour la partie drivers Nvidia :
> > https://lists.debian.org/debian-stable-announce/2024/02/msg2.html
> > The following packages have been updated to correct the problem:
> > Source package Fixed version
> > nvidia-graphics-drivers525.147.05-7~deb12u1
> > nvidia-graphics-drivers-tesla  525.147.05-7~deb12u1
> > nvidia-graphics-drivers-tesla-470  470.223.02-4~deb12u1
> > nvidia-settings 525.147.05-1~deb12u1 :
# apt list --upgradable
me demande d'upgrader les drivers nvidia, ce que j'ai fait
sans incident.
Toujours impossible d'upgrader ma bookworm,
malgré une purge complète des éléments 6.1.0-18.
(je suis bloqué avec le noyau 6.1.0-17).
QUID ?

Bonne journée

Re: Timer doing apt update

[Max Nikulin]

On 20/02/2024 14:48, Erwan David wrote:

Le 20/02/2024 à 03:20, Max Nikulin a écrit :


busctl get-property \
  org.freedesktop.NetworkManager \
  /org/freedesktop/NetworkManager \
  org.freedesktop.NetworkManager Metered

It would also require to configure NetworkManager to set this correctly. 
Eg When I use USB tethering. (same NetworkManager connexion may be used 
at different places, without any way to simply detect this, when you do 
not use Wifi)


I am unsure if the following would be convenient. You may create a 
couple of connections with and without connection.metered set. Default 
is metered, but when you know that currently traffic is not expensive, 
you may manually switch to one marked as non-metered.

Re: Timer doing apt update

[Max Nikulin]

On 20/02/2024 19:44, Greg Wooledge wrote:

1) This apt-daily.timer stuff is quite complex and difficult to discover
and understand.


I am sorry that I confused enough people by my statements. I believed 
that by default this timer runs "apt update" every day while upgrades 
are not enabled out of the box. Perhaps I saw active updates on an 
Ubuntu box and maybe desktop environment stuff was involved.


So the apt package just installs timers and services, but configuration 
files to enable update and upgrade come from unattended-upgrades and 
maybe some other packages.


Unfortunately ExecCondition is allowed only in the [Service] section, so 
it is not possible to avoid starting of timers basing on result of a 
helper script that queries apt configuration.


In the absence of systemd likely cron jobs may be configured (apticron?).

Re: Timer doing apt update

[Andy Smith]

Hello,

On Tue, Feb 20, 2024 at 07:44:55AM -0500, Greg Wooledge wrote:
>This thing has no configuration file by default; you have to read the
>comments in the software itself to figure out what it does.

Or, say, the Debian Administrator's Handbook.

https://www.debian.org/doc/manuals/debian-handbook/sect.regular-upgrades.en.html

The configuration options are also described in the man page for
apt.conf.

https://manpages.debian.org/bookworm/apt/apt.conf.5.en.html#PERIODIC_AND_ARCHIVES_OPTIONS

Thanks,
Andy

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

Re: red SATA cables "notoriously bad"?

[gene heskett]

On 2/20/24 04:29, David Christensen wrote:

On 2/19/24 18:07, Felix Miata wrote:
My experience with that particular color cables matches Gene's. Cut 
one open, and
out comes a powdery substance instead of clean copper strands. I think 
most for
gen 1.0 SATA 2 decades ago, so there shouldn't be many still around 
bogging down

3.0 drives.



About 10 (?) years ago, I seem to recall trouble-shooting a SATA 
connection problem and coming to the conclusion that the (red) SATA 
cable was the problem.  I cannot recall if I had heard Gene's story at 
the time.  I believe I decided to cut off one end, taking a 50% chance 
of getting something I could use as a break-out/ pig tail.  To my 
surprise, there was no copper within the cable, just brownish dust! 
Unfortunately, I did not photograph the cable and it is long gone.



4 or more years ago, I was plagued with SATA III connection issues; 
likely due to old SATA I and SATA II cables and mobile racks.  I bought 
a bunch of black SATA cables marked "6 Gbps" with locking connectors and 
got rid of all of my existing cables (most of which were red).  I later 
retired all of my SATA I and SATA II mobile racks, moved most of my 
drives internal, and bought a few SATA III mobile racks for off-site 
backup drives.  My SATA connection problems are finally resolved.


How many more nearly identical story's can be teased out of this group 
of old hands at this game of making moving electrons do useful things?


David

.


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

OT (Muy, muy OT): Barra herramientas MS-Excel

[Javier ArgentinaBBAR]

Buenos días.

Sé que la lista no es un centro de ayuda gratuito de MS, pero ya no sé
dónde buscar.
Resumo mis padeceres:
En el trabajo se usa intensamente MS-Office, aunque yo soy el renegado
que sigo usando LibreOffice para Windows.
Me he chocado con que al editar y guardar de Calc archivos *.xlsx, se
"despelotan" los formatos y hasta los enlaces a archivos externos.
Por lo que me veo forzado a usar Excel cuando son cosas que van para
otras personas.
Hasta ahí, bien.

El problema, es la cinta de herramientas de porquería que tiene 3cms
de alto en la pantalla; la muestro y la oculto con el consabido
"Ctrl+F1", pero
...pero quiero recuperar mi vieja (soy viejo) y súper eficiente "Barra
de herramientas" estándar.
Esa porquería de cinta tiene no más de 6 o 7 comandos, en el espacio
que estoy acostumbrado a tener más de 30 con botones chiquitos.

La pregunta: ¿alguno conoce de algún "mod" que reemplace la maldita
cinta por la vieja y eficiente Barra de herramientas en Excel?

Muchas gracias.

JAP

Re: Timer doing apt update

[tomas]

On Tue, Feb 20, 2024 at 07:44:55AM -0500, Greg Wooledge wrote:

[...]

> For me, it's a combination of two things:
> 
> 1) This apt-daily.timer stuff is quite complex and difficult to discover
>and understand [...]

I gather this from the thread, yes. I just checked, and the scripts
come with apt -- but they are ineffective if one is "on" SysV init.

All is well. Phew ;-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Re : Comment remplacer l'utilisateur root pour utiliser le service cron ?

[Christophe Maquaire]

Le mardi 20 février 2024 à 11:19 +0100, Christophe Maquaire a écrit :
> 
> 
> Y'a même mieux ou pire, c'est selon:
> 
> https://www.freedesktop.org/software/systemd/man/latest/systemd.timer.html

Je continue le prosélytisme:
In French et illustré par
l'exemple:https://wiki.archlinux.org/title/Systemd_(Fran%C3%A7ais)/Timers_(Fran%C3%A7ais)

Christophe

Re: Timer doing apt update

[Greg Wooledge]

On Tue, Feb 20, 2024 at 11:39:56AM +, Andy Smith wrote:
> On Tue, Feb 20, 2024 at 10:17:17AM +0100, Michael wrote:
> > i very much dislike the fact that my systems do things i am not aware of.
> 
> I think one of the purposes of a Linux distribution is to pull
> together a collection of disparate software of their choosing and
> make default decisions for their users.
> 
> I find it hard to believe that you bother to delve into the
> behaviour of your system in most other ways, but suddenly you've
> become aware of a systemd timer and now it's a problem for you. None
> of this is hidden. You've been able to read this script and work out
> how it works.

For me, it's a combination of two things:

1) This apt-daily.timer stuff is quite complex and difficult to discover
   and understand.  Most subsystems have a single configuration file
   that controls what they do, and it's in some place that's relatively
   easy to find.

   This thing has no configuration file by default; you have to read the
   comments in the software itself to figure out what it does.

2) In the absence of a full understanding, it's easy to suspect that these
   timers will download package lists and/or packages from the Internet.
   That's what the names imply, after all.

   Here's what the end user (me) sees upon first inspection:

* apt-daily.timer is enabled (by default)
* apt-daily.timer runs twice a day
* apt-daily.service has Description=Daily apt download activities
* apt-daily.service runs "/usr/lib/apt/apt-helper wait-online"
  and then "/usr/lib/apt/apt.systemd.daily update"

   If the end user doesn't actually read through this 538 line shell
   script to analyze its behavior, this all *looks* very much like
   "run apt update twice a day".

   Likewise, there's a second timer:

* apt-daily-upgrade.timer is enabled (by default)
* apt-daily-upgrade.timer runs once a day
* apt-daily-upgrade.service has
  Description=Daily apt upgrade and clean activities
* apt-daily-upgrade.service runs "/usr/lib/apt/apt-helper wait-online"
  and then "/usr/lib/apt/apt.systemd.daily install"

   As with the other timer and service, this all looks very much like it
   will upgrade packages, once a day.

Re: Timer doing apt update

[Erwan David]

Le 20/02/2024 à 12:46, Andy Smith a écrit :

Hi,

On Tue, Feb 20, 2024 at 08:52:09AM +0100, Erwan David wrote:

I use KDE, and I do not know wether discover does an update by itself. I do
not thind any setting about this

I think it is very likely that KDE has an equivalent to GNOME, which
does the equivalent of "apt update" every day and then notifies you
about available package upgrades.

Thanks,
Andy

Yes, and it seems to be plasma-discover. But I do noit find how to 
configure it NOT to update package list automatically.


A systemctl --user list-units '*discover*'  gives
 UNIT    LOAD 
  ACTIVE SUB DESCRIPTION
 app-org.kde.discover-5f3c6a37712a431b929cbe82aa9555dc.scope loaded 
active running Discover - Logithèque
 app-org.kde.discover.notifier@autostart.service loaded 
active running Discover


a list-unit-files says the service is generated. I did nit find from 
what it os generated.


There is /etc/xdg/autostart/org.kde.discover.notifier.desktop


which ends in


Exec=/usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier
Icon=system-software-update
Type=Application
NoDisplay=true
X-KDE-autostart-phase=1
OnlyShowIn=KDE

DiscoverNotifier comes form the plasma-discover package

The pacakge contains a /usr/bin/plasma-discover-update binary, whose 
name appears in DiscoverNotifier binary...



I'll try looking this way.


I would have preferred being able to disable it (especially because it 
shows me a systray indication when there are upgradable packages) but if 
it is not possible I can remove it (it won't remove the meta-packages of 
the DE)

Re: Timer doing apt update

[Andy Smith]

Hi,

On Tue, Feb 20, 2024 at 08:52:09AM +0100, Erwan David wrote:
> I use KDE, and I do not know wether discover does an update by itself. I do
> not thind any setting about this

I think it is very likely that KDE has an equivalent to GNOME, which
does the equivalent of "apt update" every day and then notifies you
about available package upgrades.

Thanks,
Andy

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

Re: Timer doing apt update

[Andy Smith]

Hi,

On Tue, Feb 20, 2024 at 10:17:17AM +0100, Michael wrote:
> i very much dislike the fact that my systems do things i am not aware of.

I think one of the purposes of a Linux distribution is to pull
together a collection of disparate software of their choosing and
make default decisions for their users.

I find it hard to believe that you bother to delve into the
behaviour of your system in most other ways, but suddenly you've
become aware of a systemd timer and now it's a problem for you. None
of this is hidden. You've been able to read this script and work out
how it works.

Do you also build your own kernels so you can personally sign off on
every kernel config choice, or do you trust the Debian kernel team's
ideas about what should be built in, modularised or not available at
all?

For me it's a problem when things can't be customised. I expect
default choices to be made but I don't expect to agree with 100% of
them. That's OK.

Thanks,
Andy

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

Re: Booten vanaf USB steeds trager

[Richard Lucassen]

On Tue, 20 Feb 2024 09:31:02 +0100
Paul van der Vlis  wrote:

> Ik heb een setup waarbij ik boot vanaf USB met grub. Het valt me op
> dat dit steeds trager wordt, op dezelfde machine:
> 
> Debian10:  18 seconden
> Debian11:  60 seconden
> Debian12:  ruim 120 seconden

Ik heb ook zoiets gehad, tijdens het booten geeft-ie aan dat-ie de root
device niet kan vinden en dat duurt dan een tijdje. IIRC helpt een

update-initramfs -u 

dan, maar zeker weet ik dat niet ('t is alweer een tijdje terug). Met
een monitor erop kun je die meldingen zien. Ik sloop trouwens altijd de
"quiet" optie uit /etc/default/grub (en daarna update-grub). Heb je wel
"rootwait" als kerneloptie meegegeven? Volgens mij moet dat ook. Dit
staat in de cmdline.txt file op mijn Raspberry Pi:

console=serial0,115200 console=tty1 root=PARTUUID=3fc93f64-02
rootfstype=ext4 fsck.repair=yes rootwait

Ben geen guru op dat gebied trouwens. 

-- 
richard lucassen
http://contact.xaq.nl/

Re: utilisation de nis et nfs pour un réseau de 32 postes

[Pierre Malard]

Ou ahh ! NIS, ça ne me rajeuni pas ça ;-)
Et pourquoi pas un LDAP pour l’authentification ?

Pour ce qui du montage direct du répertoire partagé sur la home dir ce n’est 
pas judicieux car ça va ramer dur si on fait une utilisation gourmande en 
entrée sortie.
Si je me souviens de ce qu’on avait fait ici c’est d’utiliser PAM et autofs 
pour gérer les accès sur les postes avec :
Création de la home dir à la volée si besoin depuis un squelette qui contient 
un point de montage pour NFS
Montage du répertoire partagé de l’utilisateur dans $HOME/NFS

Comme ça l’utilisateur n’est pas ralenti dans ses compilations par exemple et 
peut accéder à ses données dans le répertoire ~/NFS


> Le 20 févr. 2024 à 08:34, olivier  a écrit :
> 
> Bonjour,
> 
> J'ai un réseau totalement avec débian 11 (que je compte mettre à jour avec la 
> version 12), constitué d'un serveur avec deux cartes réseau, l'une reliée à 
> l’extérieur par la fibre (DHCP) et l'autre carte (Adresse IP fixe 
> 192.168.200.0) reliée à un switch. Ce switch est relié à 32 postes (avec IP 
> fixe de 192.168.200.10 à 192.168.200.50, adresse de la passerelle 
> 192.168.200.0, masque de sous réseau 255.255.255.0).
> 
> Les 32 postes sont utilisés par une classe d'élèves. J'ai 200 élèves à gérer, 
> donc 200 profil différent.
> 
> Pour que chaque poste accède à internet, j'ai fais
> 
> iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> 
> Est ce judicieux ?
> 
> J'ai essayé avec NIS avec debian 11, l'authentification à l'air de bien 
> fonctionner. Pour l'authentification, NIS est il bien adapté pour ce genre de 
> configuration ?
> 
> Par contre au niveau de l'export (NFS), cela rame un peu (je me rend compte 
> que j'exporte l'ensemble du home serveur sur tous les clients et non celui 
> uniquement de l'utilisateur). Comment faire pour exporter sur la machine 
> cliente uniquement le profil de l'utilisateur et non tous les utilisateurs ?
> 
> Sur le serveur, j'ai mis à la fin dans le fichier /etc/exports
> 
> /home/NFS_Partage 192.168.200.1/24(rw,sync,no_subtree_check)
> mais j'hésite avec
> 
> /home/NFS_Partage 
> 192.168.0.0/24(rw,all_squash,anonuid=1000,anongid=1000,sync,no_subtree_check)
> 
> Sur le client, j'ai mis à la fin dans le fichier fstab
> 
> DomaineNFS:/home/NFS_Partage /home nfs defaults0 0
> 
> On m'a parlé de LDAP, mais je ne sais pas trop comment m'y prendre. Est il 
> préférable d'utiliser LDAP ou NIS pour l'authentification ? Existe il un 
> petit manuel simple pour créer 200 utilisateurs.
> 
> Mon réseau fonctionne, mais rame beaucoup au delà de 4 utilisateurs ? et je 
> n'arrive pas à trouver une solution.
> 
> Un grand merci pour votre aide.
> 
> Olivier
> 
> 
> 

-- 
Pierre Malard

  « La façon de donner vaut mieux que ce que l'on donne »
   Pierre Corneille (1606-1684) - Le menteur
   |\  _,,,---,,_
   /,`.-'`'-.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)   πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ 
(  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--



signature.asc
Description: Message signed with OpenPGP

Re: partition reporting full, but not

[Thomas Schmitt]

Hi,

> when cfdisk reports:
> Device  Start   End  Sectors   Size  Type
> /dev/sda2   1785522176  1786245119 722944  353M  EFI System
> /dev/sda3   1786245120  1933045759  146800640  70G   EFI System
> I don't understand the 'EFI System' note /dev/sda3 is /

The partition type does not necessarily match the type of filesystem
which is currently in that partition. It's just a field in the
partition table which must have some value.


Have a nice day :)

Thomas

Re: Re : Comment remplacer l'utilisateur root pour utiliser le service cron ?

[Christophe Maquaire]

Le mardi 20 février 2024 à 10:00 +0100, NoSpam a écrit :
> Bonjour
> 
> Le 20/02/2024 à 05:54, k6dedi...@free.fr a écrit :
> > Bonjour,
> > Je découvre ce fil de discussion.
> > Je ne comprends pas que l'on puisse encore travailler avec CRON.
> > Alors que ANACRON est indépendant de la période de fonctionnement
> > du PC.
> Si on se place d'un point de vue poste de travail. Pour les serveurs,
> aucun intérêt !
> 
Y'a même mieux ou pire, c'est selon:

https://www.freedesktop.org/software/systemd/man/latest/systemd.timer.html

Comme debian est passé à systemd, autant en profiter ou boire le calice
jusqu'à la lie, c'est encore selon.

Christophe

Re: Comment remplacer l'utilisateur root pour utiliser le service cron ?

[Bernard Bass]

La question initiale : Comment remplacer l'utilisateur root pour 
utiliser le service cron ?


Devrait plutôt être : *Comment lancer le service cron/crontab avec 
l'utilisateur gestionnaire (root) ?*


J'ai créé l'utilisateur gestionnaire de la sorte :

Créer un utilisateur gestionnaire pour remplacer les actions de 
l'utilisateur root, pour lancer toutes les tâches cron.


Consulter les groupes de l'utilisateur root :
sudo bash
id
uid=0(root) gid=0(root) groupes=0(root)

groups
root

Créer l'utilisateur gestionnaire :
*sudo adduser gestionnaire*

Ajouter l'utilisateur gestionnaire au groupe des administrateurs système 
(root) à l'aide de la commande usermod :

# usermod -aG sudo gestionnaire
*sudo usermod -aG root gestionnaire*

Ajouter les droits root à l'utilisateur gestionnaire avec visudo :
*sudo visudo
root    ALL=(ALL:ALL) ALL
gestionnaire    ALL=(ALL:ALL) ALL
*
sudo bash
cat /etc/passwd | grep -i gestionnaire
gestionnaire:x:1001:1001:,,,:/home/gestionnaire:/bin/bash

sudo bash
Donner à l'utilisateur gestionnaire les privilèges root sans qu'il n'ait 
a utiliser sudo :
Changer l'ID de l'utilisateur gestionnaire avec l'option d'ID 
utilisateur non unique :

*usermod -o -u 0 gestionnaire*

Utiliser su pour s'identifier avec l'utilisateur gestionnaire et devenir 
root :

$ *su gestionnaire*
Mot de passe :
*root*@system:/home/utilisateur-courant#

cat /etc/passwd | grep -i gestionnaire
gestionnaire:x:0:1001:,,,:/home/gestionnaire:/bin/bash

La ligne peut être réécrite de la façon suivante :
sudo nano /etc/passwd
gestionnaire:x:0:1001:Gestionnaire:/home/gestionnaire:/bin/bash


Je n'ai pas trouvé comment relancer le service cron avec cet autre 
utilisateur gestionnaire.




*La solution fonctionnelle pour désactiver root semble être la suivante :*


1)
sudo passwd root # Créer un mot de passe.
sudo passwd -d root # Supprimer le mot de passe.


2)
* Désactiver l'utilisateur root à partir du shell.
Le moyen le plus simple de désactiver la connexion de l'utilisateur 
root est de changer son shell du répertoire /bin/bash à /sbin/nologin, 
dans le fichier /etc/passwd.


sudo nano /etc/passwd
root:x:0:0:root:/root:/sbin/nologin


3)
sudo passwd -S root
root NP 02/18/2024 0 9 7 -1 # L'utilisateur root utilise no password.


4)
su root
This account is currently not available.


5)
On ne peut donc pas accéder à root directement.
Le système cron avec la crontab -e root continue de fonctionner.
Le user root semble faire son travail sans erreur.



J'aurais préféré créer un utilisateur gestionnaire pour remplacer les 
actions de l'utilisateur root, capable de lancer toutes les tâches cron.

Si quelqu'un sait expliquer la méthode.
Merci.

Re: partition reporting full, but not

[tomas]

On Tue, Feb 20, 2024 at 09:21:15PM +1100, Keith Bainbridge wrote:
> 
> On 20/2/24 19:38, to...@tuxteam.de wrote:

[...]

> Tomas, the upgrade failure was earlier than these notes. It has now worked

I see.

> Sorry, but I don't know how to assess the snapshot space usage.

Nor do I -- my question was rather directed at Felix, who seems to
be the only one in this thread with some btrfs experience.

Perhaps it'd be wise to include "btrfs" in the Subject to attract
the attention of btrfs buffs?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: partition reporting full, but not

[Keith Bainbridge]

On 20/2/24 19:38, to...@tuxteam.de wrote:

On Tue, Feb 20, 2024 at 02:42:18AM -0500, Felix Miata wrote:

Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):


I just removed 3 snapshots from my daily driver with no change in used
space reported by df


df doesn't know how to calculate freespace on btrfs. You need to be typing

btrfs filesystem df

if you have not aliased df to btrfs filesystem df.


Still, Keith seems to have a real shortage of file system free space,
otherwise Debian upgrades wouldn't fail.

I don't know much about btrfs, but what would be really helpful (if
you do, and it seems so) would be for you to fill us in on how to
asses the space used up by old snapshots (what seems to be the main
suspect currently).

Cheers


Tomas, the upgrade failure was earlier than these notes. It has now worked

Sorry, but I don't know how to assess the snapshot space usage.

--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
+61 (0)447 667 468

UTC + 10:00

Re: partition reporting full, but not

[Keith Bainbridge]

On 20/2/24 18:42, Felix Miata wrote:

btrfs filesystem df


OK, so please interpret:

  >> btrfs filesystem df -h /
Data, single: total=32.80GiB, used=31.94GiB
System, DUP: total=8.00MiB, used=16.00KiB
Metadata, DUP: total=1.50GiB, used=1.10GiB
GlobalReserve, single: total=71.69MiB, used=0.00B
keith@dell0 $

 Tue 20Feb2024@20:57:45
 :~

  >> btrfs filesystem df -h /mnt/data/
Data, single: total=530.02GiB, used=329.55GiB
System, DUP: total=8.00MiB, used=112.00KiB
Metadata, DUP: total=5.00GiB, used=1.10GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
keith@dell0 $

when cfdisk reports:
 DeviceStartEnd 
Sectors   Size Type
>>  /dev/sda1 2048 1667678207 
1667676160 795.2G Linux filesystem
Free space   1667678208 1785522175 
117843968  56.2G
/dev/sda21785522176 1786245119 
   722944   353M EFI System
/dev/sda31786245120 1933045759 
14680064070G EFI System
/dev/sda41933045760 1953523711 
 20477952   9.8G Linux swap


To clarify
/dev/sda1 is /mnt/dataand I don't understand the 'EFI System' note
/dev/sda3 is /

Perhaps the explanation why the reports from btrfs filesystem df make no 
sense will come when I get into my assignment?


--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
+61 (0)447 667 468

UTC + 10:00

Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem)

[Eike Lantzsch ZP5CGE / KY4PZ]

On Dienstag, 20. Februar 2024 06:58:31 -03 Eike Lantzsch ZP5CGE / KY4PZ
wrote:
> On Montag, 19. Februar 2024 21:48:52 -03 Andy Smith wrote:
> > Hi,
> >
> > On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE /
> > KY4PZ
> wrote:
> > > The notorious red SATA cables - I threw them out long ago. The red
> > > pigment eats up the fine copper threads, changing the impedance of
> > > the cable and eventually making false contact before failing
> > > completely.
> >
> > I've never heard of this. I did a bit of searching around and all I
> > can find is assertions that cable colour doesn't matter for SATA. I
> > can't seem to find anything about red pigment damaging the copper.
> > Have you got a reference so I can learn more?
> >
> > Thanks,
> > Andy
>
> Experience ...
> "notoriously bad" on my work bench.
> Audio cables, SATA cables, even red cables of 1.5mm2 upwards. The
> corrosion can be seen although it takes decades for the thicker cables
> to deteriorate.
> It very much depends on where the cables have been manufactured.
> Never had problems with European made or US made telephone cables with
> wires with red sheeths. But copper cable manufacturing has been
> outsourced to Asia (and Argentina - Pirelli but those are good) many
> decades ago.

If you open the sheeth of the red SATA cable, you will see that at least
three wires have no extra sheeth but are directly embedded into the red
plastic. 4 are shielded. So I guess that those wires are not affected.
There is one naked wire in the middle and two to the right and left.

--
Eike Lantzsch KY4PZ / ZP5CGE

Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem)

[Eike Lantzsch ZP5CGE / KY4PZ]

On Montag, 19. Februar 2024 21:48:52 -03 Andy Smith wrote:
> Hi,
>
> On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ
wrote:
> > The notorious red SATA cables - I threw them out long ago. The red
> > pigment eats up the fine copper threads, changing the impedance of
> > the cable and eventually making false contact before failing
> > completely.
> I've never heard of this. I did a bit of searching around and all I
> can find is assertions that cable colour doesn't matter for SATA. I
> can't seem to find anything about red pigment damaging the copper.
> Have you got a reference so I can learn more?
>
> Thanks,
> Andy

Experience ...
"notoriously bad" on my work bench.
Audio cables, SATA cables, even red cables of 1.5mm2 upwards. The
corrosion can be seen although it takes decades for the thicker cables
to deteriorate.
It very much depends on where the cables have been manufactured.
Never had problems with European made or US made telephone cables with
wires with red sheeths. But copper cable manufacturing has been
outsourced to Asia (and Argentina - Pirelli but those are good) many
decades ago.

--
Eike Lantzsch KY4PZ / ZP5CGE

Re: Erreur nvidia suite upgrade noyau 6.1.0-18

[Patrick ZAJDA]

Le 19/02/2024 à 20:42, ajh-valmer a écrit :

On Monday 19 February 2024 19:17:22 Patrick ZAJDA wrote:
et epsilon

Merci :
  

La mise à jour est déjà disponibles sur les dépôts officiels, si
bookworm-updates est bien dans les listes de sources alors la version
525.147.05-7~deb12u1 devrait être disponible à l'installation

Il semblerait que la mise à jour du kernel 6.1.0-18-amd64,
ne concerne que la version Debian SID.
J'ai retenté un apt update  => apt upgrade en vain,
c'est un échec, ma Debian-12 refuse de dépasser le noyau 6.1.0-17-amd64 :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932

Intéressant que tu dises que ça n'est que pour Sid alors qu'à la fin du 
bug que tu indiques, c'est clairement dit que c'est dispo pour stable...
Et je suis sous Bookworm, pas de Sid du tout chez moi ; mon kernel est 
bien 6.1.0-18. Peut-être que tu devrais revérifier tes listes sources 
(sources.list et autres dans sources.list.d) et si tu ne ferais pas du 
pining qui bloquerait quelque chose...
Utilises-tu apt-listbugs ? J'ai eu quelques surprises par le passé 
niveau pining.



Pour la partie drivers Nvidia :
https://lists.debian.org/debian-stable-announce/2024/02/msg2.html
The following packages have been updated to correct the problem:
Source package Fixed version
nvidia-graphics-drivers525.147.05-7~deb12u1
nvidia-graphics-drivers-tesla  525.147.05-7~deb12u1
nvidia-graphics-drivers-tesla-470  470.223.02-4~deb12u1
nvidia-settings525.147.05-1~deb12u1

Je ne peux rien tester tant que je ne peux upgrader.


Même chose que ce que j'ai dit ci-dessus.

Je crois qu'une (re ?)vérification s'impose de ton côté niveau config de 
apt.


Patrick


Bonne soirée.


$ apt policy nvidia-driver
nvidia-driver:
Installé : 525.147.05-7~deb12u1
Candidat : 525.147.05-7~deb12u1
Table de version :
*** 525.147.05-7~deb12u1 500
500https://deb.debian.org/debian  bookworm-updates/non-free
amd64 Packages
100 /var/lib/dpkg/status
525.147.05-4~deb12u1 500
  500https://deb.debian.org/debian  bookworm/non-free amd64 Packages


--
Patrick ZAJDA

Re: red SATA cables "notoriously bad"?

[David Christensen]

On 2/19/24 18:07, Felix Miata wrote:

My experience with that particular color cables matches Gene's. Cut one open, 
and
out comes a powdery substance instead of clean copper strands. I think most for
gen 1.0 SATA 2 decades ago, so there shouldn't be many still around bogging down
3.0 drives.



About 10 (?) years ago, I seem to recall trouble-shooting a SATA 
connection problem and coming to the conclusion that the (red) SATA 
cable was the problem.  I cannot recall if I had heard Gene's story at 
the time.  I believe I decided to cut off one end, taking a 50% chance 
of getting something I could use as a break-out/ pig tail.  To my 
surprise, there was no copper within the cable, just brownish dust! 
Unfortunately, I did not photograph the cable and it is long gone.



4 or more years ago, I was plagued with SATA III connection issues; 
likely due to old SATA I and SATA II cables and mobile racks.  I bought 
a bunch of black SATA cables marked "6 Gbps" with locking connectors and 
got rid of all of my existing cables (most of which were red).  I later 
retired all of my SATA I and SATA II mobile racks, moved most of my 
drives internal, and bought a few SATA III mobile racks for off-site 
backup drives.  My SATA connection problems are finally resolved.



David

Re: Timer doing apt update

[Michael]

On Tuesday, February 20, 2024 5:23:35 AM CET, Greg Wooledge wrote:

I'm not sure how to interpret this combination of things.  Do these
default settings mean "the update/upgrade script will run, but it won't
actually do anything"?


kind of...

lines 354-360 (on bookworm) of said script (/usr/lib/apt/apt.systemd.daily) 
checks if 'APT::Periodic::Enable' is set to 1. if not, the script exits 
with 0:


 # check if the user really wants to do something
 AutoAptEnable=1  # default is yes
 eval $(apt-config shell AutoAptEnable APT::Periodic::Enable)

 if [ $AutoAptEnable -eq 0 ]; then
 exit 0
 fi

i very much dislike the fact that my systems do things i am not aware of. i 
don't mind if this timer/service exists, but i do not want it to be enabled 
by default. especially if its default setting is to do nothing (useful, 
critical, necessary)! why add complication to a system and waste its 
resources if it defaults to not doing anything? why not add .timer and 
.service, but keep it disabled by default? admin's choice...


imho it is even easier and more intuitive to enable the timer than to add a 
file in which i change/set an option to prevent an already started process 
to exit prematurely having already wasted system resources.


but that's just me. ymmv...

greetings...

Re: Re : Comment remplacer l'utilisateur root pour utiliser le service cron ?

[NoSpam]

Bonjour

Le 20/02/2024 à 05:54, k6dedi...@free.fr a écrit :

Bonjour,
Je découvre ce fil de discussion.
Je ne comprends pas que l'on puisse encore travailler avec CRON.
Alors que ANACRON est indépendant de la période de fonctionnement du PC.
Si on se place d'un point de vue poste de travail. Pour les serveurs, 
aucun intérêt !

Re: utilisation de nis et nfs pour un réseau de 32 postes

[Basile Starynkevitch]

On 2/20/24 08:34, olivier wrote:

Bonjour,

J'ai un réseau totalement avec débian 11 (que je compte mettre à jour 
avec la version 12), constitué d'un serveur avec deux cartes réseau, 
l'une reliée à l’extérieur par la fibre (DHCP) et l'autre carte 
(Adresse IP fixe 192.168.200.0) reliée à un switch. Ce switch est 
relié à 32 postes (avec IP fixe de 192.168.200.10 à 192.168.200.50, 
adresse de la passerelle 192.168.200.0, masque de sous réseau 
255.255.255.0).


Les 32 postes sont utilisés par une classe d'élèves. J'ai 200 élèves à 
gérer, donc 200 profil différent.


Pour que chaque poste accède à internet, j'ai fais

iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

Est ce judicieux ?

J'ai essayé avec NIS avec debian 11, l'authentification à l'air de 
bien fonctionner. Pour l'authentification, NIS est il bien adapté pour 
ce genre de configuration ?



A l'époque déjà lointaine où j'étais sysadmin occasionnel (au CEA) NIS 
fonctionnait bien. C'était avant 2000, sur des stations Sun.



Par contre (et pour avoir enseigné plus récemment Linux à l'IUT d'Orsay) 
je m'interroge sur la pertinence de mettre (en 2024) le /home sur NFS. 
Ça a un inconvenient colossal en 2024: NFS est plus lent que l'accès au 
disque local de chaque poste. Si on compile des sources sur un serveur 
NFS avec le fichier objet sur un serveur NFS (le même), si on lance un 
exécutable ELF sur un serveur NFS, c'est nettement plus lent.


Ca dépend de quels genres d'enseignements il s'agit. S'il s'agit 
d'enseigner à des débutants complets la programmation avec un langage 
compilé (C, C++, Ada, Fortran, Ocaml) j'aurais tendance à :


 * décider avec les autres enseignants si les étudiants peuvent avoir
   accès (ou non) aux fichiers de leurs camarades. A mon avis c'est
   très utile (pour l'entraide, la détection du plagiat, ...).
 * expliquer aux étudiants ce qu'est NFS et un serveur de fichiers.
 * Ne pas monter NFS le /home mais un autre répertoire, par exemple
   /UnivMontp3et annoncer aux étudiants que le /home n'est pas sauvegardé!
 * expliquer aux étudiants ce qu'est un versionneur de fichiers; leur
   recommander (voir imposer) l'utilisation de git: https://git-scm.com/
 * installer un service git sur le serveur.
 * expliquer à tous les étudiants leurs droits et devoirs (comme
   étudiants). Par exemple, ceux (et ils sont nombreux) qui ont un
   ordinateur portable personnel (à eux, pas payé par l'université),
   ont-ils le droit de l'utiliser en TP? de le connecter au réseau? d'y
   installer Linux? d'accéder le serveur de l'université depuis la
   salle de cours ou de leur chambre d'étudiant? d'imprimer sur
   l'imprimante de la classe leurs fichiers source (ou d'autres)?





Par contre au niveau de l'export (NFS), cela rame un peu (je me rend 
compte que j'exporte l'ensemble du home serveur sur tous les clients 
et non celui uniquement de l'utilisateur). Comment faire pour exporter 
sur la machine cliente uniquement le profil de l'utilisateur et non 
tous les utilisateurs ?



Ca doit être possible par une configuration de PAM. 
https://fr.wikipedia.org/wiki/Pluggable_Authentication_Modules mais 
j'ignore les détails! Il y a probablement des universités qui peut-être 
utilisent rsync à la connection de l'étudiant pour recopier sur le 
disque local des fichiers depuis le serveur.




Sur le serveur, j'ai mis à la fin dans le fichier /etc/exports

/home/NFS_Partage 192.168.200.1/24(rw,sync,no_subtree_check)
mais j'hésite avec

/home/NFS_Partage 
192.168.0.0/24(rw,all_squash,anonuid=1000,anongid=1000,sync,no_subtree_check)


Sur le client, j'ai mis à la fin dans le fichier fstab

DomaineNFS:/home/NFS_Partage /home nfs defaults 0 0

On m'a parlé de LDAP, mais je ne sais pas trop comment m'y prendre. 
Est il préférable d'utiliser LDAP ou NIS pour l'authentification ? 
Existe il un petit manuel simple pour créer 200 utilisateurs.



La création de 200 utilisateurs est probablement faisable en GNU bash ou 
Python ou Ocaml ou C++ en quelques dizaines de lignes.




Mon réseau fonctionne, mais rame beaucoup au delà de 4 utilisateurs ? 
et je n'arrive pas à trouver une solution.


A mon avis, NIS pour chaque accès aux fichiers de l'étudiant va ramer 
énormément! Pourquoi pas un /home local à la machine pour l'étudiant, 
qui serait par exemple recopié depuis le serveur NFS au login, et 
recopié (par rsync) vers le serveur NFS puis effacé (localement) au logout?



Variante: l'étudiant liste sur son $HOME/.mes-depots-git (ou dans une 
carte NIS maison?) tous les répertoires git à cloner au login.



A l'IUT d'Orsay il y avait même un applicatif sur le PC de l'enseignant 
qui permettait d'éteindre simultanément tous les PCs (de l'université) 
dans la salle de TP utilisés par les étudiants.




Un grand merci pour votre aide.



Espérant avoir un peu aidé!


Librement





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

Re: partition reporting full, but not

[tomas]

On Tue, Feb 20, 2024 at 02:42:18AM -0500, Felix Miata wrote:
> Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):
> 
> > I just removed 3 snapshots from my daily driver with no change in used 
> > space reported by df
> 
> df doesn't know how to calculate freespace on btrfs. You need to be typing
> 
>   btrfs filesystem df
> 
> if you have not aliased df to btrfs filesystem df.

Still, Keith seems to have a real shortage of file system free space,
otherwise Debian upgrades wouldn't fail.

I don't know much about btrfs, but what would be really helpful (if
you do, and it seems so) would be for you to fill us in on how to
asses the space used up by old snapshots (what seems to be the main
suspect currently).

Cheers
-- 
t


signature.asc
Description: PGP signature

Booten vanaf USB steeds trager

[Paul van der Vlis]

Hallo,

Ik heb een setup waarbij ik boot vanaf USB met grub. Het valt me op dat 
dit steeds trager wordt, op dezelfde machine:


Debian10:  18 seconden
Debian11:  60 seconden
Debian12:  ruim 120 seconden

Wat vooral lang duurt is "loading initial ramdisk", het lichtje is dan 
reuze hard aan het knipperen. Het gaat verder allemaal wel goed.


Op een snellere machine is het wel wat sneller, maar het blijft 
onacceptabel traag.


Ik heb ook al de kernel-optie "debug" gegeven, dan maakt initramfs een 
log. Maar omdat er geen tijden bij staan zegt het me weinig over wat nu 
zo lang duurt. Dmesg geeft wel tijden, maar ik kom er niet uit.


Ik zie hetzelfde ook op andere machines. Overigens niet bij een Debian 
installer of livestick, dat gaat wel goed. Maar als ik echt Debian 
installeer op een USB device start het traag, dezelfde SSD aan SATA gaat 
wel goed. Ik heb al verschillende USB naar SATA kabels geprobeerd, maar 
dat lijkt ook niet het probleem.


Hebben jullie ideeën hoe ik dit booten vanaf USB sneller krijg?

Groet,
Paul



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

Re: GRUB lost graphical terminal mode

[Michael Kjörling]

On 19 Feb 2024 22:44 +0100, from borde...@tutanota.com (Borden):
>> Would you be willing to post your /boot/grub/grub.cfg for a setup
>> where you get the blank screen GRUB?
> 
> Yeah, I probably should have opened with that. Sorry:
> 
> ```
> # If you change this file, run 'update-grub' afterwards to update
> # /boot/grub/grub.cfg.
> # For full documentation of the options in this file, see:
> #   info -f grub -n 'Simple configuration'
> 
> GRUB_DEFAULT=0
[snipped remainder]

If that's your /boot/grub/grub.cfg, it's a miracle that your GRUB
installation is working at all and not dumping you to a grub> rescue
prompt.

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