Re: Debian 11 Termit

[David Wright]

On Sat 12 Nov 2022 at 21:11:45 (-0500), Amn wrote:
> On 2022-11-12 7:36 a.m., Mindaugas wrote:
> > On 11/12/22 00:11, Amn wrote:
> > > Does anyone know how to change the color scheme of Termit in
> > > Debian 11? The files displayed in blue indigo are just too
> > > hard to read for me.
> > > 
> > > Thanks in advance.
> > > 
> > 
> > Hello. Configuration can be changed via $HOME/.config/termit/rc.lua file.
> > 
> 
> Thanks Mindaugas for your response, but Debian 11's HOME/.config does
> not have a 'termit' sub directory, thus it does not have a 'rc.lus'
> file.
> Is there another way to change the indigo colour?

There appear to be eight so-called 'colormaps' in
/etc/xdg/termit/colormaps.lua, viz tango, zenburn, delicate,
mikado, parkerBrothers, fishbone, bright and irc, whatever
these are.

It is of course against Debian policy to install or remove files in
any home directory. The closest approach to this would probably be
for a package to install files in /etc/skel/, which would then be
copied into new users' home directories as they were being created.

Cheers,
David.

Re: Booting problem

[David Wright]

On Sun 13 Nov 2022 at 08:24:11 (+0530), Emilia Maher wrote:
> Hello,
> I have installed NetBeans through snapd process, as explained here:
> 
> https://wiki.debian.org/Netbeans
> 
> But after installation completed, I have faced booting problem.
> Then I have removed the snapd through terminal command as well I followed
> the instructions given here:
> https://wiki.debian.org/ReduceDebian#Remove_unnecessary_kernel_modules
> 
> To clear the unwanted packages but still I am facing the same booting
> problem.
> Please let me know what I can do to fix booting problem.

It might be an idea to explain what the nature of your booting problem is.

Cheers,
David.

Re: initrd sizes mushroomed several months ago

[David Wright]

On Sat 12 Nov 2022 at 01:57:51 (-0500), Felix Miata wrote:
> # grep MODULES= /etc/initramfs-tools/initramfs.conf
> MODULES=dep
> # ls -Ggh /boot/initrd.img-[5,6]*
> -rw-r--r-- 1 6.8M May  8  2022 /boot/initrd.img-5.17.0-1-686
> -rw-r--r-- 1  31M Aug  2 03:06 /boot/initrd.img-5.18.0-3-686
> -rw-r--r-- 1  31M Sep 30 15:43 /boot/initrd.img-5.19.0-2-686
> -rw-r--r-- 1  36M Nov 12 01:36 /boot/initrd.img-6.0.0-3-686
> 
> Does anyone here have an explanation for the mega-change in size of initrds 
> after
> kernel 5.17? My initramfs.conf has had MODULES=dep since before 
> testing/bullseye
> became testing/bookworm.

Can you try running   lsinitramfs  | sort   on each, and
compare what's included, to see whether that differs. (Using
lsinitramfs -l   would need options adding to sort, and some
post-processing, to get much sense out of a diff.)

I have a system that's not fully configured, and is rather old.

drwxr-xr-x 2 root root 4096 Jan  8  2022 efi/
drwxr-xr-x 5 root root 4096 Jan  8  2022 grub/
-rw-r--r-- 1 root root   83 Dec  8  2021 System.map-5.10.0-10-amd64
-rw-r--r-- 1 root root   83 Sep 30  2021 System.map-5.10.0-9-amd64
-rw-r--r-- 1 root root   236056 Dec  8  2021 config-5.10.0-10-amd64
-rw-r--r-- 1 root root   236055 Sep 30  2021 config-5.10.0-9-amd64
-rw-r--r-- 1 root root 29578226 Jan  8  2022 initrd.img-5.10.0-10-amd64
-rw-r--r-- 1 root root 28159235 Jan  8  2022 initrd.img-5.10.0-9-amd64
-rw-r--r-- 1 root root  6841280 Dec  8  2021 vmlinuz-5.10.0-10-amd64
-rw-r--r-- 1 root root  6833568 Sep 30  2021 vmlinuz-5.10.0-9-amd64

However, they'll both be MODULES=most; perhaps I'll boot it sometime
and regenerate them with MODULES=dep.

Currently, this same machine, also MODULES=most, has:

drwx-- 3 root root 4096 Dec 31  1969 efi/
drwxr-xr-x 5 root root 4096 Nov  3 23:26 grub/
-rw-r--r-- 1 root root   83 Sep  2 08:54 System.map-5.10.0-18-amd64
-rw-r--r-- 1 root root   83 Oct 21 15:24 System.map-5.10.0-19-amd64
-rw-r--r-- 1 root root   236286 Sep  2 08:54 config-5.10.0-18-amd64
-rw-r--r-- 1 root root   236275 Oct 21 15:24 config-5.10.0-19-amd64
-rw-r--r-- 1 root root 36946455 Sep 12 15:20 initrd.img-5.10.0-18-amd64
-rw-r--r-- 1 root root 36951179 Nov  4 13:16 initrd.img-5.10.0-19-amd64
-rw-r--r-- 1 root root 36951452 Nov  3 23:21 initrd.img-5.10.0-19-amd64.bak
-rw-r--r-- 1 root root  6962016 Sep  2 08:54 vmlinuz-5.10.0-18-amd64
-rw-r--r-- 1 root root  6963648 Oct 21 15:24 vmlinuz-5.10.0-19-amd64

Cheers,
David.

Booting problem

[Emilia Maher]

Hello,
I have installed NetBeans through snapd process, as explained here:

https://wiki.debian.org/Netbeans

But after installation completed, I have faced booting problem.
Then I have removed the snapd through terminal command as well I followed
the instructions given here:
https://wiki.debian.org/ReduceDebian#Remove_unnecessary_kernel_modules

To clear the unwanted packages but still I am facing the same booting
problem.
Please let me know what I can do to fix booting problem.

Thanks and Regards

Re: Debian 11 Termit

[Greg Wooledge]

On Sat, Nov 12, 2022 at 09:11:45PM -0500, Amn wrote:
> Thanks Mindaugas for your response, but Debian 11's HOME/.config does not
> have a 'termit' sub directory, thus it does not have a 'rc.lus' file.
> Is there another way to change the indigo colour?

I've never used termit, but here's the man page:

https://manpages.debian.org/bullseye/termit/termit.1.en.html

If the config file doesn't exist, then perhaps you're expected to create
it yourself.  The man page also points to an example file, which I'm
guessing will be a much more informative starting point.

It looks like the target audience for this particular terminal emulator
is "people who like Lua".  So, you're assumed to know Lua syntax at least.

Re: Sysstemd question

[Amn]

I second that opinion!!!

On 2022-11-12 6:12 p.m., pa...@quillandmouse.com wrote:

On Sat, 12 Nov 2022 11:04:39 -0500
Greg Wooledge  wrote:


On Sat, Nov 12, 2022 at 10:41:15AM -0500, pa...@quillandmouse.com
wrote:

Folks:

I've been reading up on systemd, both from Red Hat's documentation,
Debian's and the man files. One thing I haven't been able to
explain is why systemd has config files in /etc, /lib, /run, and
/usr/lib.

/lib and /usr/lib are the same thing, or will be the same thing in a
future release.  Don't worry about that.

/run is transient.  It's an in-memory file system, created and
populated at boot time, or by running programs.  It's not a place for
configuration.

So really you're looking at /etc vs. /usr/lib.

/usr/lib contains the defaults created by the Debian maintainers or
the upstream authors.  When you install a new package that has a
systemd unit file, that's where it'll go.

/etc contains the overrides and configuration elements that are unique
to your system.  If a service is masked or disabled, it'll be done
here. If you install a locally built service, and write a systemd
unit for it, this is where you'll put it.  If you override part or
all of a package's unit file, you do it here.


Thanks for this excellent explanation. I wish the folks who write docs
would try to explain things in English instead of geek-ese. I'm a
programmer, and I try to keep this in mind whenever I write docs. That
said, though, the Red Hat docs for systemd are pretty good.

Paul

Re: sid - no sound on speakers

[Amn]

Are you promoting violence?

On 2022-11-12 11:30 a.m., Jude DaShiell wrote:



Jude 
"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)

.

On Sun, 13 Nov 2022, David wrote:



On Sat, Nov 12, 2022 at 13:42, Kamil Jo?ca  wrote:


David mailto:curmudg...@telaman.net.au>> writes:


On Sat, Nov 12, 2022 at 09:31, Kamil Jo?ca mailto:kjo...@o2.pl>> wrote:

  Recently I found strange thing: I have no sound on speakers. There is
no problem with usb headphone, or headphone via jack but speakers are
silent. As I almost exclusively use usb headphones I have no idea when this
problem started. In theory is possible that
  speakers are broken but the same thing on completely different
laptpop. I tried to play with: --8<---cut
here---start->8--- options snd-intel-dspcfg
dsp_driver= --8<---cut
here---end--->8---
  but without success. Any hints? During my searching I found

 but I am not sure if
this is related.

  What are you running?
  Stable, Testing, Unstable?

sid on both laptops

devices
on one laptop:
--8<---cut here---start->8---
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High
Definition Audio Controller (rev 01)
--8<---cut here---end--->8---

on second laptop:
--8<---cut here---start->8---
:00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP
Smart Sound Technology Audio Controller (rev 20)
--8<---cut here---end--->8---

I have exactly the opposite problem on an Acer laptop on SID.
No sound through headphones, but I do through speakers.
This since the last install.
The USB headphones can't even be found.
Cheers!

If memory serves, debian has an update-usb utility that can be used to
update information on usb devices.  I think it is a standard install so
everyone got it that installed debian.

Re: Debian 11 Termit

[Amn]

Thanks Mindaugas for your response, but Debian 11's HOME/.config does 
not have a 'termit' sub directory, thus it does not have a 'rc.lus' file.

Is there another way to change the indigo colour?

Thanks in advance.

On 2022-11-12 7:36 a.m., Mindaugas wrote:


On 11/12/22 00:11, Amn wrote:
Does anyone know how to change the color scheme of Termit in Debian 
11? The files displayed in blue indigo are just too hard to read for me.


Thanks in advance.



Hello. Configuration can be changed via $HOME/.config/termit/rc.lua file.

Re: Sysstemd question

[paulf]

On Sat, 12 Nov 2022 11:04:39 -0500
Greg Wooledge  wrote:

> On Sat, Nov 12, 2022 at 10:41:15AM -0500, pa...@quillandmouse.com
> wrote:
> > Folks:
> > 
> > I've been reading up on systemd, both from Red Hat's documentation,
> > Debian's and the man files. One thing I haven't been able to
> > explain is why systemd has config files in /etc, /lib, /run, and
> > /usr/lib.
> 
> /lib and /usr/lib are the same thing, or will be the same thing in a
> future release.  Don't worry about that.
> 
> /run is transient.  It's an in-memory file system, created and
> populated at boot time, or by running programs.  It's not a place for
> configuration.
> 
> So really you're looking at /etc vs. /usr/lib.
> 
> /usr/lib contains the defaults created by the Debian maintainers or
> the upstream authors.  When you install a new package that has a
> systemd unit file, that's where it'll go.
> 
> /etc contains the overrides and configuration elements that are unique
> to your system.  If a service is masked or disabled, it'll be done
> here. If you install a locally built service, and write a systemd
> unit for it, this is where you'll put it.  If you override part or
> all of a package's unit file, you do it here.
> 

Thanks for this excellent explanation. I wish the folks who write docs
would try to explain things in English instead of geek-ese. I'm a
programmer, and I try to keep this in mind whenever I write docs. That
said, though, the Red Hat docs for systemd are pretty good.

Paul

-- 
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster

Re: cifrado de discos en instalación debian 11.5

[JavierDebian]

El 12/11/22 a las 09:56, Luis Miguel R. escribió:

Buenas a todos,
Por defecto, la instalación de debian 11.5, si le dices que quieres LVM cifrado 
no cifra la partición swap no?, la verdad que con esto del LVM no me entero, 
cuando arrancas solo pide la clave de cifrado una vez, en en /etc/cryptsetup 
solo hay una linea con la partición raiz

Saludos



El actual cifrado de LVM, no sé si cifra la swap.
En mis épocas de paranoia, cifraba el disco, y en lugar de usar una 
partición de swap, usaba un archivo en el disco cifrado como swap.


Pero eran las épocas de LUKS.

JAP

Re: MTBF interpretations (Re: ZFS performance)

[Stefan Monnier]

>> > Claimed MTBF: 1 million hours. Believe it or not, this is par
>> > for the course for high-end disks.
>> > 
>> > 24 hours a day, 365 days a year: 8760 hours per year.
>> > 100/8760 = 114 years.
>> > 
>> > So, no: MTBF numbers must be presumed to be malicious lies.
>> 
>> With your interpretation every single drive would not be allowed to fail
>> before its MTBF value. That's wrong. MTBF is a mean value for all drives
>> of this type, not a guaranteed minimum value for a single drive. 
>
> No, my interpretation is that the average (mean) lifetime
> between failures should be the listed value. At 114 years, half
> of the population of drives should still be working.

Sadly, that's a misinterpretation.
What you describe would be called something like life expectancy.

The main problem with MTBF is that it's very often misunderstood.
The other problem is that life expectancy is almost never provided as
a data point, contrary to MTBF, whereas for the vast majority of buyers
(who only buy a single item) life expectancy would be the more
meaningful measure.


Stefan

Re: definiing deduplication

[Stefan Monnier]

> It took me a while to find out how the block layer can ensure that a
> snapshot is consistent on the filesystem level. The answer is Linux VFS
> method super_operations.freeze_fs().
>   https://www.kernel.org/doc/html/latest/filesystems/vfs.html
> Without it a snapshot on block level would be similar to a filesystem
> which was not properly unmounted before power-off.

But as I mentioned, higher-layers (the filesystem layer, and the
applications running on top of that) *should* try and make sure that
a hard failure (kernel crash, power failure, ... these and up taking
a snapshot of your block device) can never result in an
inconsistent state.

That's the core of the ext3 improvement over ext2, for example.

> So there might still filesystems in the Linux kernel which do not support
> LVM snapshots in a safe way.

Of course, just like there are still many applications which write files
non-atomically.


Stefan

Re: sid - no sound on speakers

[Jude DaShiell]

Jude 
"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)

.

On Sun, 13 Nov 2022, David wrote:

>
>
> On Sat, Nov 12, 2022 at 13:42, Kamil Jo?ca  wrote:
> >
> >
> > David mailto:curmudg...@telaman.net.au>> writes:
> >
> >> On Sat, Nov 12, 2022 at 09:31, Kamil Jo?ca  >> > wrote:
> >>
> >>  Recently I found strange thing: I have no sound on speakers. There is
> >> no problem with usb headphone, or headphone via jack but speakers are
> >> silent. As I almost exclusively use usb headphones I have no idea when this
> >> problem started. In theory is possible that
> >>  speakers are broken but the same thing on completely different
> >> laptpop. I tried to play with: --8<---cut
> >> here---start->8--- options snd-intel-dspcfg
> >> dsp_driver= --8<---cut
> >> here---end--->8---
> >>  but without success. Any hints? During my searching I found
> >> 
> >>  but I am not sure if
> >> this is related.
> >>
> >>  What are you running?
> >>  Stable, Testing, Unstable?
> >
> > sid on both laptops
> >
> > devices
> > on one laptop:
> > --8<---cut here---start->8---
> > 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High
> > Definition Audio Controller (rev 01)
> > --8<---cut here---end--->8---
> >
> > on second laptop:
> > --8<---cut here---start->8---
> > :00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP
> > Smart Sound Technology Audio Controller (rev 20)
> > --8<---cut here---end--->8---
>
> I have exactly the opposite problem on an Acer laptop on SID.
> No sound through headphones, but I do through speakers.
> This since the last install.
> The USB headphones can't even be found.
> Cheers!
If memory serves, debian has an update-usb utility that can be used to
update information on usb devices.  I think it is a standard install so
everyone got it that installed debian.
>

Re: sid - no sound on speakers

[David]

On Sat, Nov 12, 2022 at 13:42, Kamil Jońca  wrote:



David mailto:curmudg...@telaman.net.au>> 
writes:


 On Sat, Nov 12, 2022 at 09:31, Kamil Jońca > wrote:


 Recently I found strange thing: I have no sound on speakers. 
There is no problem with usb headphone, or headphone via jack but 
speakers are silent. As I almost exclusively use usb headphones I 
have no idea when this problem started. In theory is possible that
 speakers are broken but the same thing on completely different 
laptpop. I tried to play with: --8<---cut 
here---start->8--- options snd-intel-dspcfg 
dsp_driver= --8<---cut 
here---end--->8---
 but without success. Any hints? During my searching I found 
 
 but I am not 
sure if this is related.


 What are you running?
 Stable, Testing, Unstable?


sid on both laptops

devices
on one laptop:
--8<---cut here---start->8---
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake 
PCH-P High Definition Audio Controller (rev 01)

--8<---cut here---end--->8---

on second laptop:
--8<---cut here---start->8---
:00:1f.3 Multimedia audio controller: Intel Corporation Tiger 
Lake-LP Smart Sound Technology Audio Controller (rev 20)

--8<---cut here---end--->8---


I have exactly the opposite problem on an Acer laptop on SID.
No sound through headphones, but I do through speakers.
This since the last install.
The USB headphones can't even be found.
Cheers!

Re: Sysstemd question

[Greg Wooledge]

On Sat, Nov 12, 2022 at 10:41:15AM -0500, pa...@quillandmouse.com wrote:
> Folks:
> 
> I've been reading up on systemd, both from Red Hat's documentation,
> Debian's and the man files. One thing I haven't been able to explain is
> why systemd has config files in /etc, /lib, /run, and /usr/lib.

/lib and /usr/lib are the same thing, or will be the same thing in a
future release.  Don't worry about that.

/run is transient.  It's an in-memory file system, created and populated
at boot time, or by running programs.  It's not a place for configuration.

So really you're looking at /etc vs. /usr/lib.

/usr/lib contains the defaults created by the Debian maintainers or the
upstream authors.  When you install a new package that has a systemd
unit file, that's where it'll go.

/etc contains the overrides and configuration elements that are unique
to your system.  If a service is masked or disabled, it'll be done here.
If you install a locally built service, and write a systemd unit for it,
this is where you'll put it.  If you override part or all of a package's
unit file, you do it here.

Sysstemd question

[paulf]

Folks:

I've been reading up on systemd, both from Red Hat's documentation,
Debian's and the man files. One thing I haven't been able to explain is
why systemd has config files in /etc, /lib, /run, and /usr/lib.
I also can't find in what order systemd scans these directories. Also,
why it's necessary for there to be symlinks in /etc/systemd/system to
files in /lib/systemd/system. These questions may be a bit too esoteric,
but if anyone could explain, or point me to documentation, I'd
appreciate it.

Paul

-- 
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster

Re: about https://wiki.debian.org/Multimedia

[Thomas Schmitt]

Hi,

Patrice Duroux wrote:
> I have done a little change to its content but then I realized that
> it is written that the list is generated from:
> https://salsa.debian.org/nodiscc2-guest/awesome-linuxaudio
>
> I think that it should be:
> https://salsa.debian.org/nodiscc/awesome-linuxaudio

  https://wiki.debian.org/Multimedia?action=info
indicates that at 2019-08-16 it was nodiscc2-guest/awesome-linuxaudio
and at 2021-10-28  it was nodiscc/awesome-linuxaudio.


> But the page shows currently a certain distance from the git content.
> So is this still true [...] ?

It might be that the three changes in 2022 before yours by GurkanMyczko
caused the deviation.

Looking at the change from git of 2021-10-28
  https://wiki.debian.org/Multimedia?action=diff=102=103
it seems like it erased your previous change of 2020-03-28
  https://wiki.debian.org/Multimedia?action=diff=100=101

Consider to contact the other Editors shown at
  https://wiki.debian.org/Multimedia?action=info
Two of them have personal pages with contact information:
  https://wiki.debian.org/nodiscc
  https://wiki.debian.org/GurkanMyczko

(Maybe create https://wiki.debian.org/PatriceDuroux with at least
your e-mail address for similar occasions.)


> and do my remark the reason explain this distance?

I admit that i don't understand this part of the sentence.


Have a nice day :)

Thomas

about https://wiki.debian.org/Multimedia

[Patrice Duroux]

Hi,

I have done a little change to its content but then I realized that
it is written that the list is generated from: 
https://salsa.debian.org/nodiscc2-guest/awesome-linuxaudio

I think that it should be:
https://salsa.debian.org/nodiscc/awesome-linuxaudio

But the page shows currently a certain distance from the git content.
So is this still true and do my remark the reason explain this distance?

Thanks,
Patrice

Re: exim4 vs. frontier.com

[Curt]

On 2022-11-12, David Wright  wrote:
>
> If and when that works, it should be simple to get exim to send
> to the smarthost in the same manner. It should involve only the
> two files /etc/exim4/{passwd.client,update-exim4.conf.conf} in
> most cases.

https://groups.google.com/g/linux.debian.user/c/bAI10SqfmGA

He asked the same question back in May but with some other data
points, not that it probably makes any difference.

> (Remove the .muttdebug file as it contains password information.
> Certainly don't send it to anybody.)
>
> ¹ The debug file makes up for the fact that there's no log in
>   /var/log/exim4/ because exim doesn't touch it.
>
> Cheers,
> David.


-- 

Re: Problem with card reader on Debian 11

[Claudia Neumann]

Hi Tomas,

mmh, may be it has something to do with cdc_acm.

On Debian 10, where the reading is okay, cdc_acm is inserted in the kernel if I 
insert the
device.

If I 'rmmod cdc_acm' the /dev/ttyACM0 disappears und so I cannot read from the 
device.

Perhaps I have to deactivate the registration of 1f61:0001?

Best regards

Claudia

Am Samstag, 12. November 2022, 11:01:42 CET schrieb to...@tuxteam.de:
> On Sat, Nov 12, 2022 at 09:38:34AM +0100, Claudia Neumann wrote:
> > Am Freitag, 11. November 2022, 19:37:08 CET schrieb to...@tuxteam.de:
> > > On Fri, Nov 11, 2022 at 04:38:21PM +0100, Claudia Neumann wrote:
> > > > Hi Tomas,
> >
> > Hi Tomas,
> >
> > I did as you said. You find the results in the attachments.
> >
> > There is a differenz in udev behaviour on inserting the device. Perhaps it
> > is this Flexocard identification. The device I am using is not a
> > Flexocard device. I don't know if there is a relation between Zemo, the
> > manufacturer of the VML-GK2, and Flexocard.
> Oh, that is interesting: either Zenmo has a Flexocard "heart" or
> they are squatting on their IDs (that would be improbable, but not
> completely unheard of).
>
> > How can I get rid of that Flexocard configuration?
> >
> > I tried
> > stty -F /fev/ttyACM0 115200 parenb -parodd -cstopb
> > which was used in the old times on /dev/ttyS0. But that did not change
> > anything. So it seems to be something with udev??
>
> The way it usually works is that the kernel logs events (new device
> added, removed, etc.) on a socket and the udev daemon listens on them
> and takes any actions (like loading a kernel module, starting a
> user space program, changing inode permissions, etc).
>
> I'll assume this is Debian 11:
> > root@Mediondebn:~# udevadm monitor
> > monitor will print the received events for:
> > UDEV - the event which udev sends out after rule processing
> > KERNEL - the kernel uevent
> >
> > KERNEL[2035.060329] add  /devices/pci:00/:00:14.0/usb1/1-4
> > (usb) KERNEL[2035.067291] add
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb)
> > KERNEL[2035.067318] add
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> > KERNEL[2035.067352] bind /devices/pci:00/:00:14.0/usb1/1-4
> > (usb) UDEV  [2035.079950] add
> > /devices/pci:00/:00:14.0/usb1/1-4 (usb) UDEV  [2035.082479] add
> >/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> > KERNEL[2035.00] bind
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> > KERNEL[2035.088911] add
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
> > KERNEL[2035.088951] bind
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb)
> > KERNEL[2035.088970] add  /bus/usb/drivers/cdc_acm (drivers)
> > KERNEL[2035.088983] add  /module/cdc_acm (module)
> > UDEV  [2035.089029] add
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb) UDEV
> > [2035.089748] add  /bus/usb/drivers/cdc_acm (drivers)
> > UDEV  [2035.090184] add  /module/cdc_acm (module)
> > UDEV  [2035.093556] bind /devices/pci:00/:00:14.0/usb1/1-4
> > (usb) UDEV  [2035.094826] bind
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb) UDEV
> > [2035.095798] add
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty) UDEV
> > [2035.096868] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0
> > (usb)
> >
> > No message on lsof | grep ttyACM
> >
> > root@Mediondebn:~# stty -a < /dev/ttyACM0
> > speed 9600 baud; rows 0; columns 0; line = 0;
>
> [...]
>
> and this Debian 10:
> > root@Mediondebn:~# udevadm monitor
> > monitor will print the received events for:
> > UDEV - the event which udev sends out after rule processing
> > KERNEL - the kernel uevent
> >
> > KERNEL[145.449225] add  /devices/pci:00/:00:14.0/usb1/1-4
> > (usb)
> > KERNEL[145.450616] add
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb)
> > KERNEL[145.450776] add
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
> > KERNEL[145.450800] bind
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb)
> > KERNEL[145.450821] add
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> > KERNEL[145.450844] bind
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> > KERNEL[145.450867] bind /devices/pci:00/:00:14.0/usb1/1-4
> > (usb) UDEV  [145.454702] add
> > /devices/pci:00/:00:14.0/usb1/1-4 (usb) UDEV  [145.455832] add
> >   /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb) UDEV
> > [145.456187] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1
> > (usb) UDEV  [145.456878] bind
> > /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb) UDEV

Re: MTBF interpretations (Re: ZFS performance)

[Dan Ritter]

hede wrote: 
> On Fri, 11 Nov 2022 14:05:33 -0500 Dan Ritter  wrote:
> 
> > Claimed MTBF: 1 million hours. Believe it or not, this is par
> > for the course for high-end disks.
> > 
> > 24 hours a day, 365 days a year: 8760 hours per year.
> > 100/8760 = 114 years.
> > 
> > So, no: MTBF numbers must be presumed to be malicious lies.
> 
> With your interpretation every single drive would not be allowed to fail 
> before its MTBF value. That's wrong. MTBF is a mean value for all drives of 
> this type, not a guaranteed minimum value for a single drive. 

No, my interpretation is that the average (mean) lifetime
between failures should be the listed value. At 114 years, half
of the population of drives should still be working.

This is obviously not congruent with reality.

> If you have one thousand drives then you have to expect one drive failure for 
> every one thousand hours (MTBF=1,000,000). Statistically you have to expect 
> nearly nine of those drives to fail per year (if I did my math correctly). 
> With higher MTBF values this value will be smaller, with lower MTBF values 
> you'd have to expect more drives to fail.

You are assuming a linear distribution. A normal distribution
would be more likely. A bathtub curve is often hypothesized.

The largest public source of data on disk mortality is from
BackBlaze:

https://www.backblaze.com/blog/backblaze-drive-stats-for-q3-2022/

and what you can work out from their data set is:

* Brands are not meaningful as predictors of longevity
* It is not linearly distributed.
* It is not normally distributed.
* It is not a bathtub distribution.

Some drive models are lucky. Some are unlucky. Overall you
should expect about 1.54% of disks to fail each year in a large
mixed-age population, not quite double what you estimated. But
the range of annualized failure rates is from 0 to 9% -- you
could be lucky, or very unlucky.

-dsr-

cifrado de discos en instalación debian 11.5

[Luis Miguel R.]

Buenas a todos,
Por defecto, la instalación de debian 11.5, si le dices que quieres LVM cifrado 
no cifra la partición swap no?, la verdad que con esto del LVM no me entero, 
cuando arrancas solo pide la clave de cifrado una vez, en en /etc/cryptsetup 
solo hay una linea con la partición raiz

Saludos

Re: sid - no sound on speakers

[Kamil Jońca]

David  writes:

> On Sat, Nov 12, 2022 at 09:31, Kamil Jońca  wrote:
>
> Recently I found strange thing: I have no sound on speakers. There is no 
> problem with usb headphone, or headphone via jack but speakers are silent. As 
> I almost exclusively use usb headphones I have no idea when this problem 
> started. In theory is possible that
> speakers are broken but the same thing on completely different laptpop. I 
> tried to play with: --8<---cut 
> here---start->8--- options snd-intel-dspcfg 
> dsp_driver= --8<---cut here---end--->8---
> but without success. Any hints? During my searching I found 
> https://bbsarchlinux.org/viewtopic.php?id=275061 
> https://bugzilla.kernel.org/show_bug.cgi?id=216139 but I am not sure if this 
> is related.
>
> What are you running?
> Stable, Testing, Unstable?

sid on both laptops

devices
on one laptop:
--8<---cut here---start->8---
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High 
Definition Audio Controller (rev 01)
--8<---cut here---end--->8---

on second laptop:
--8<---cut here---start->8---
:00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart 
Sound Technology Audio Controller (rev 20)
--8<---cut here---end--->8---


KJ

-- 
http://wolnelektury.pl/wesprzyj/teraz/

Re: ZFS performance (was: Re: deduplicating file systems: VDO with Debian?)

[Dan Ritter]

David Christensen wrote: 
> The Intel Optane Memory Series products are designed to be cache devices --
> when using compatible hardware, Windows, and Intel software.  My hardware
> should be compatible (Dell PowerEdge T30), but I am unsure if FreeBSD 12.3-R
> will see the motherboard NVMe slot or an installed Optane Memory Series
> product.
> 
> 
> Intel Optane Memory M10 16 GB PCIe M.2 80mm are US $18.25 on Amazon.
> 
> 
> Intel Optane Memory M.2 2280 32GB PCIe NVMe 3.0 x2 are US $69.95 on Amazon.

Note that the entire product line is discontinued, so if you want this,
assume that you will not be able to get a replacement in future.

-dsr-

Re: Problème de souris (?)

[Dethegeek]

Bonjour,

Avec ce genre de souci, ça peut valoir le coup de simplifier le système.

Est ce que le problème persiste su la souris est branchée sans hub
intermédiaire, directement sur le pc (même port USB) ?

Par extension, si un autre port USB sans hub est disponible, qu'est ce que
ça donne ?

Le sam. 12 nov. 2022 à 13:22, Basile Starynkevitch 
a écrit :

>
> On 11/12/22 12:32, Nicolas FRANCOIS wrote:
> > Bonjour.
> >
> > J'ai un comportement étrange de ma souris de temps en temps, sans
> > pouvoir déterminer ce qui pourrait le causer.
> >
> > C'est une bête souris Logitech sans fil, branchée sur un Hub USB 3.0,
> > lui-même branché sur un desktop Debian 11 avec XFCE4.
> >
> > De temps en temps donc, je remarque des sortes de clics intempestifs :
> > je suis en train de faire autre chose, et je vois l'icône de gestion du
> > volume signaler que j'ai changé le réglage (alors que non...) et me le
> > signaler par un joli "scratch" dans les haut-parleurs. Ou bien je suis
> > en train de faire glisser l’ascenseur des dossiers de Claws Mail, et
> > tout à coup je me retrouve avec un dossier sélectionné et une
> > proposition de transférer les 1200 messages qui se trouvent dedans dans
> > un autre dossier... sans savoir qui veut aller où, ce qui est
> > légèrement préoccupant pour la sanité de mes répertoires.
> >
> > J'ai essayé avec une autre souris (une HP pour portable), même
> > comportement.
> >
> > Je ne sais pas trop quoi faire, et mes recherches sur Google ne m'ont
> > pas vraiment convaincu de l'existence de problèmes similaires autre
> > part.
>
>
> Des utilitaires utiles pour peut-être comprendre le problème (sans
> prétendre le résoudre):
>
> Essayer un autre desktop, par exemple en installant les paquets
> lxde-session lxqt-session unity-session
>
> D'abord, sous root, regarder les fichiers sous /var/log/ notamment
> Xorg.0.log, syslog, kern.log,
>
> Ensuite: regarder et peut-être modifier /etc/X11/xorg.conf (sauvegardez
> le avant, prenez vos précautions, essayer de demarrer le serveur
> graphique avec avec startx et une session convenable, par exemple le
> paquet icewm ...)
>
> Verifier que la souris est bien vue par lsusb
>
> Utiliser xev en ligne de commande (paquet x11-utils)
>
>
> --
> Basile Starynkevitch  
> (only mine opinions / les opinions sont miennes uniquement)
> 92340 Bourg-la-Reine, France
> web page: starynkevitch.net/Basile/
>
>

Re: Debian 11 Termit

[Mindaugas]

On 11/12/22 00:11, Amn wrote:
Does anyone know how to change the color scheme of Termit in Debian 
11? The files displayed in blue indigo are just too hard to read for me.


Thanks in advance.



Hello. Configuration can be changed via $HOME/.config/termit/rc.lua file.

Re: Problème de souris (?)

[Basile Starynkevitch]

On 11/12/22 12:32, Nicolas FRANCOIS wrote:

Bonjour.

J'ai un comportement étrange de ma souris de temps en temps, sans
pouvoir déterminer ce qui pourrait le causer.

C'est une bête souris Logitech sans fil, branchée sur un Hub USB 3.0,
lui-même branché sur un desktop Debian 11 avec XFCE4.

De temps en temps donc, je remarque des sortes de clics intempestifs :
je suis en train de faire autre chose, et je vois l'icône de gestion du
volume signaler que j'ai changé le réglage (alors que non...) et me le
signaler par un joli "scratch" dans les haut-parleurs. Ou bien je suis
en train de faire glisser l’ascenseur des dossiers de Claws Mail, et
tout à coup je me retrouve avec un dossier sélectionné et une
proposition de transférer les 1200 messages qui se trouvent dedans dans
un autre dossier... sans savoir qui veut aller où, ce qui est
légèrement préoccupant pour la sanité de mes répertoires.

J'ai essayé avec une autre souris (une HP pour portable), même
comportement.

Je ne sais pas trop quoi faire, et mes recherches sur Google ne m'ont
pas vraiment convaincu de l'existence de problèmes similaires autre
part.



Des utilitaires utiles pour peut-être comprendre le problème (sans 
prétendre le résoudre):


Essayer un autre desktop, par exemple en installant les paquets 
lxde-session lxqt-session unity-session


D'abord, sous root, regarder les fichiers sous /var/log/ notamment 
Xorg.0.log, syslog, kern.log,


Ensuite: regarder et peut-être modifier /etc/X11/xorg.conf (sauvegardez 
le avant, prenez vos précautions, essayer de demarrer le serveur 
graphique avec avec startx et une session convenable, par exemple le 
paquet icewm ...)


Verifier que la souris est bien vue par lsusb

Utiliser xev en ligne de commande (paquet x11-utils)


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

Problème de souris (?)

[Nicolas FRANCOIS]

Bonjour.

J'ai un comportement étrange de ma souris de temps en temps, sans
pouvoir déterminer ce qui pourrait le causer.

C'est une bête souris Logitech sans fil, branchée sur un Hub USB 3.0,
lui-même branché sur un desktop Debian 11 avec XFCE4.

De temps en temps donc, je remarque des sortes de clics intempestifs :
je suis en train de faire autre chose, et je vois l'icône de gestion du
volume signaler que j'ai changé le réglage (alors que non...) et me le
signaler par un joli "scratch" dans les haut-parleurs. Ou bien je suis
en train de faire glisser l’ascenseur des dossiers de Claws Mail, et
tout à coup je me retrouve avec un dossier sélectionné et une
proposition de transférer les 1200 messages qui se trouvent dedans dans
un autre dossier... sans savoir qui veut aller où, ce qui est
légèrement préoccupant pour la sanité de mes répertoires.

J'ai essayé avec une autre souris (une HP pour portable), même
comportement.

Je ne sais pas trop quoi faire, et mes recherches sur Google ne m'ont
pas vraiment convaincu de l'existence de problèmes similaires autre
part.

Vous avez déjà vu ça ? Vous l'avez réglé comment ? Ou bien, je peux
faire comment pour trouver d'où ça vient ?

D'avance merci pour m'avoir lu jusque là, et pour vos éventuelles
réponses.

\bye

-- 

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

Re: Problem with card reader on Debian 11

[tomas]

On Sat, Nov 12, 2022 at 09:38:34AM +0100, Claudia Neumann wrote:
> Am Freitag, 11. November 2022, 19:37:08 CET schrieb to...@tuxteam.de:
> > On Fri, Nov 11, 2022 at 04:38:21PM +0100, Claudia Neumann wrote:
> > > Hi Tomas,
> > > 
> Hi Tomas,
> 
> I did as you said. You find the results in the attachments. 
> 
> There is a differenz in udev behaviour on inserting the device. Perhaps it is 
> this Flexocard 
> identification. The device I am using is not a Flexocard device. I don't know 
> if there is a 
> relation between Zemo, the manufacturer of the VML-GK2, and Flexocard. 

Oh, that is interesting: either Zenmo has a Flexocard "heart" or
they are squatting on their IDs (that would be improbable, but not
completely unheard of).

> How can I get rid of that Flexocard configuration? 
> 
> I tried 
> stty -F /fev/ttyACM0 115200 parenb -parodd -cstopb
> which was used in the old times on /dev/ttyS0. But that did not change 
> anything. So it 
> seems to be something with udev??

The way it usually works is that the kernel logs events (new device
added, removed, etc.) on a socket and the udev daemon listens on them
and takes any actions (like loading a kernel module, starting a
user space program, changing inode permissions, etc).

I'll assume this is Debian 11:

> root@Mediondebn:~# udevadm monitor
> monitor will print the received events for:
> UDEV - the event which udev sends out after rule processing
> KERNEL - the kernel uevent
> 
> KERNEL[2035.060329] add  /devices/pci:00/:00:14.0/usb1/1-4 (usb)
> KERNEL[2035.067291] add  
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb)
> KERNEL[2035.067318] add  
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> KERNEL[2035.067352] bind /devices/pci:00/:00:14.0/usb1/1-4 (usb)
> UDEV  [2035.079950] add  /devices/pci:00/:00:14.0/usb1/1-4 (usb)
> UDEV  [2035.082479] add  
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> KERNEL[2035.00] bind 
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> KERNEL[2035.088911] add  
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
> KERNEL[2035.088951] bind 
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb)
> KERNEL[2035.088970] add  /bus/usb/drivers/cdc_acm (drivers)
> KERNEL[2035.088983] add  /module/cdc_acm (module)
> UDEV  [2035.089029] add  
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb)
> UDEV  [2035.089748] add  /bus/usb/drivers/cdc_acm (drivers)
> UDEV  [2035.090184] add  /module/cdc_acm (module)
> UDEV  [2035.093556] bind /devices/pci:00/:00:14.0/usb1/1-4 (usb)
> UDEV  [2035.094826] bind 
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 (usb)
> UDEV  [2035.095798] add  
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
> UDEV  [2035.096868] bind 
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 (usb)
> 
> No message on lsof | grep ttyACM

> root@Mediondebn:~# stty -a < /dev/ttyACM0
> speed 9600 baud; rows 0; columns 0; line = 0;
[...]

and this Debian 10:

> root@Mediondebn:~# udevadm monitor
> monitor will print the received events for:
> UDEV - the event which udev sends out after rule processing
> KERNEL - the kernel uevent
> 
> KERNEL[145.449225] add  /devices/pci:00/:00:14.0/usb1/1-4 (usb)
> KERNEL[145.450616] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
> (usb)
> KERNEL[145.450776] add  
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
> KERNEL[145.450800] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
> (usb)
> KERNEL[145.450821] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 
> (usb)
> KERNEL[145.450844] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 
> (usb)
> KERNEL[145.450867] bind /devices/pci:00/:00:14.0/usb1/1-4 (usb)
> UDEV  [145.454702] add  /devices/pci:00/:00:14.0/usb1/1-4 (usb)
> UDEV  [145.455832] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
> (usb)
> UDEV  [145.456187] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 
> (usb)
> UDEV  [145.456878] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 
> (usb)
> UDEV  [145.457303] add  
> /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
> UDEV  [145.458222] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
> (usb)
> UDEV  [145.462165] bind /devices/pci:00/:00:14.0/usb1/1-4 (usb)
> 
> No message on lsof | grep ttyACM0
> 
> root@Mediondebn:~# stty -a < /dev/ttyACM0
> speed 9600 baud; rows 0; columns 0; line = 0;

The main difference seems to be that the first (which I assume to
be Debian 11) adds the kernel module `cdc_acm'. To see whether this
is what makes the difference, you might try `sudo rmmod cdc_acm'
(and double-check with `sudo lsmod | grep cdc_acm'). To be extra
sure, may be try this on both installations and note the differences.

If that is successful, the 

Re: sid - no sound on speakers

[David]

On Sat, Nov 12, 2022 at 09:31, Kamil Jońca  wrote:


Recently I found strange thing: I have no sound on speakers. There is 
no

problem with usb headphone, or headphone via jack but speakers are
silent.
As I almost exclusively use usb headphones I have no idea when this
problem started.
In theory is possible that speakers are broken but the same thing on
completely different laptpop.
I tried to play with:

--8<---cut here---start->8---
options snd-intel-dspcfg dsp_driver=
--8<---cut here---end--->8---

but without success.
Any hints?
During my searching I found


but I am not sure if this is related.


What are you running?
Stable, Testing, Unstable?
Cheers!

sid - no sound on speakers

[Kamil Jońca]

Recently I found strange thing: I have no sound on speakers. There is no
problem with usb headphone, or headphone via jack but speakers are
silent.
As I almost exclusively use usb headphones I have no idea when this
problem started.
In theory is possible that speakers are broken but the same thing on
completely different laptpop.
I tried to play with:

--8<---cut here---start->8---
options snd-intel-dspcfg dsp_driver=
--8<---cut here---end--->8---

but without success.
Any hints?
During my searching I found
https://bbs.archlinux.org/viewtopic.php?id=275061
https://bugzilla.kernel.org/show_bug.cgi?id=216139
but I am not sure if this is related.

KJ

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html

Re: Problem with card reader on Debian 11

[Claudia Neumann]

Am Freitag, 11. November 2022, 19:37:08 CET schrieb to...@tuxteam.de:
> On Fri, Nov 11, 2022 at 04:38:21PM +0100, Claudia Neumann wrote:
> > Hi Tomas,
> > 
Hi Tomas,

I did as you said. You find the results in the attachments. 

There is a differenz in udev behaviour on inserting the device. Perhaps it is 
this Flexocard 
identification. The device I am using is not a Flexocard device. I don't know 
if there is a 
relation between Zemo, the manufacturer of the VML-GK2, and Flexocard. 

How can I get rid of that Flexocard configuration? 

I tried 
stty -F /fev/ttyACM0 115200 parenb -parodd -cstopb
which was used in the old times on /dev/ttyS0. But that did not change 
anything. So it 
seems to be something with udev??

Thanks for the help.

Best regards

Claudia

> > Am Freitag, 11. November 2022, 06:54:36 CET schrieb to...@tuxteam.de:
> > > On Thu, Nov 10, 2022 at 11:21:21PM +0100, Claudia Neumann wrote:
> [...]
> 
> Thanks. The only difference I can see is:
> 
> [Debian 11]
> [...]
> 
> > After:
> [...]
> 
> > Bus 001 Device 008: ID 1f61:0001 Flexocard GmbH VML-GK2 (USB)
> 
> [...]
> 
> >   iManufacturer   1 Flexocard GmbH
> >   iProduct2 VML-GK2 (USB)
> >   iSerial 3 2009002
> 
> [Debian 10];
> [...]
> 
> > After:
> [...]
> 
> > Bus 001 Device 014: ID 1f61:0001
> 
> [...]
> 
> >   iManufacturer   1
> >   iProduct2
> >   iSerial 3
> 
> This would kind of make sense: the newer kernel has a more complete
> USB device database and "knows" the Flexocard device.
> 
> Now I see a couple of possibilities. Either the newer drivers are
> buggy, or some other program (perhaps courtesy of udev) "thinks" it
> has to take care of this USB gadget. To get a clearer idea about the
> second, you might try to run "udevadm monitor" while you insert your
> device.
> 
> Another thing to check is whether any application has /dev/ttyACM0
> (that was its name, wasn't it?) open is to query it with `lsof`.
> 
> Ah, you might also want to see what parameters this pseudo-serial
> interface it has, e.g. `stty -a < /dev/ttyACM0'.
> 
> Sorry: if it seems like I'm poking in the dark, then that' perhaps
> because I am :-)
> 
> Cheers
> --
> tomás


root@Mediondebn:~# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[2035.060329] add  /devices/pci:00/:00:14.0/usb1/1-4 (usb)
KERNEL[2035.067291] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
(usb)
KERNEL[2035.067318] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 
(usb)
KERNEL[2035.067352] bind /devices/pci:00/:00:14.0/usb1/1-4 (usb)
UDEV  [2035.079950] add  /devices/pci:00/:00:14.0/usb1/1-4 (usb)
UDEV  [2035.082479] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 
(usb)
KERNEL[2035.00] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 
(usb)
KERNEL[2035.088911] add  
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
KERNEL[2035.088951] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
(usb)
KERNEL[2035.088970] add  /bus/usb/drivers/cdc_acm (drivers)
KERNEL[2035.088983] add  /module/cdc_acm (module)
UDEV  [2035.089029] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
(usb)
UDEV  [2035.089748] add  /bus/usb/drivers/cdc_acm (drivers)
UDEV  [2035.090184] add  /module/cdc_acm (module)
UDEV  [2035.093556] bind /devices/pci:00/:00:14.0/usb1/1-4 (usb)
UDEV  [2035.094826] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1 
(usb)
UDEV  [2035.095798] add  
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
UDEV  [2035.096868] bind /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
(usb)

No message on lsof | grep ttyACM

root@Mediondebn:~# stty -a < /dev/ttyACM0
speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = 
; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase 
= ^W; lnext = ^V; discard = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff 
-iuclc -ixany -imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt 
echoctl echoke -flusho -extproc
root@Mediondebn:~# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[145.449225] add  /devices/pci:00/:00:14.0/usb1/1-4 (usb)
KERNEL[145.450616] add  /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0 
(usb)
KERNEL[145.450776] add  
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/tty/ttyACM0 (tty)
KERNEL[145.450800] bind 

Re: definiing deduplication

[Thomas Schmitt]

Hi,

Stefan Monnier wrote:
> Presumably the "backuper" is the sysadmin, i.e. the same (group of)
> person who chose the filesystem, so I'd say yes the "backuper" is
> to blame.

I rather mean the whole complex of system maintainer, users, and
backup software.
But even if there is a qualified entity to be blamed, this does not help
with potential backup problems, because the backup cannot wait until
the culprit feels responsible and finds a way to fix the shortcommings.


> BTW, I can't think of any filesystem that can't do snapshots.  E.g. I use
> snapshots with ext4: just ask your block layer to do the snapshot rather
> than your filesystem (in my case I use LVM snapshots).

It took me a while to find out how the block layer can ensure that a
snapshot is consistent on the filesystem level. The answer is Linux VFS
method super_operations.freeze_fs().
  https://www.kernel.org/doc/html/latest/filesystems/vfs.html
Without it a snapshot on block level would be similar to a filesystem
which was not properly unmounted before power-off.

So there might still filesystems in the Linux kernel which do not support
LVM snapshots in a safe way.

  https://manpages.debian.org/bullseye/util-linux/fsfreeze.8.en.html
states about filesystems with freeze capability:
  "List of these filesystems include (2016-12-18) btrfs, ext2/3/4, f2fs,
   jfs, nilfs2, reiserfs, and xfs."
That's quite comprehensive, but by far not the full list of writable
Linux fileystems.

One would have to dig in the kernel whether others have gained a .freeze_fs
method meanwhile. I looked in the torvalds git repo at the super_operations
structs of exfat, fat, fuse, and udf. None of them offers the freeze_fs
method.


Have a nice day :)

Thomas

MTBF interpretations (Re: ZFS performance)

[hede]

On Fri, 11 Nov 2022 14:05:33 -0500 Dan Ritter  wrote:

> Claimed MTBF: 1 million hours. Believe it or not, this is par
> for the course for high-end disks.
> 
> 24 hours a day, 365 days a year: 8760 hours per year.
> 100/8760 = 114 years.
> 
> So, no: MTBF numbers must be presumed to be malicious lies.

With your interpretation every single drive would not be allowed to fail before 
its MTBF value. That's wrong. MTBF is a mean value for all drives of this type, 
not a guaranteed minimum value for a single drive. 

If there are one million drives, statistically with every hour one drive will 
fail. That means, even with correctly claiming an MTBF of 1 million hours, one 
of those million drives will statistically(!) run only one hour before it 
fails. 

Some more practical explanation: 

If you have one thousand drives then you have to expect one drive failure for 
every one thousand hours (MTBF=1,000,000). Statistically you have to expect 
nearly nine of those drives to fail per year (if I did my math correctly). With 
higher MTBF values this value will be smaller, with lower MTBF values you'd 
have to expect more drives to fail.

But this is only a pure statistical value. If you are the one of a million, 
your single drive will fail within the first hour...

(and on top there are other details, like: the MTBF is calculated for specific 
environmental conditions; if your environment is more rogue, then you'd have to 
expect a lower MTBF than the one declared by the vendor... and vice versa)

regards
hede