On file systems [was: Image handling in mutt]

On Tue, Dec 12, 2023 at 06:04:04AM +0800, jeremy ardley wrote: [...] > If you look at the NTFS file system [...] > Underneath the hood of a NTFS file is alternate data streams (ADS). That is > a single file can contain main different 'sub files' of completely different > content type. Each ADS h

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

On Tue, 12 Dec 2023 04:15:33 + Tom Furie wrote: > Do we know yet which wifi drivers are "troublesome"? I haven't seen > anything concrete yet anywhere. You can read the gory details at Mr. Price's bug report. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967 -- Does anybody read si

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

Kevin Price writes: > 6.1.0-15 brought not only the ext4-bugfix, but along with it introduced > a terrible new bug: Most computers work fine with -15, except for some > of those that have wifi, depending upon the driver. There was a certain > change in Linux's cfg80211 kernel module, which contro

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

Hey Stella, hey all: Am 11.12.23 um 19:38 schrieb Stella Ashburne: > Thank goodness it only happens once in a blue moon. May I please clarify some basic (mis-)conceptions? There's "linux-image-amd64". This is a metapackage that contains nothing but a constructed dependency upon the latest kernel

Re: Image handling in mutt

On 12/12/23 01:49, Jeremy Nicoll wrote: There's no concept of filetype in file systems used for the MVS side of z/OS systems. (These days there's also Unix/Linux environments & of course they do have more familiar file naming structures.) If you look at the NTFS file system - supported by m

Re: zfs load-key on boot randomly reports wrong password if I type too fast

That is a good pointer, I will start experimenting with kdbrate and see if anything improves. I did come up with the following contraption which helps at least seeing what is going on and so far it seems that the password is 1 char short on invalid attempt and it is usually the last char tha

Stuck Key?

I see this sort of message while booting and it continues to show up in dmesg after booting and after XFCE is up and running: [ 414.569532] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 414.569560] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [

Re: Image handling in mutt

debian-u...@howorth.org.uk wrote: > songbird wrote: >> wrote: >> > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote: >> >> wrote: >> >> there is rarely a need to e-mail me directly. >> >> >> ... >> >> > That's why I cringe when people name executables "foo.sh". What >> >> > do

Re: Thinkpad x13 AMD Ryzen microphone not working in Debian Bookworm

I found out that when I plugin a headset the microphone works. So it seems that this is related only to the internal microphone. *-multimedia:2    description: Audio device    product: Family 17h/19h HD Audio Controller    vendor: Advanced Micro Devices, Inc.

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On 12/11/23, Greg Wooledge wrote: > 1) Many implementations of echo will interpret parts of their argument(s), >in addition to processing options like -n. If you want to print a >variable's contents to standard output without *any* interpretation, >use printf. > > printf %s "$myva

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

On Mon, Dec 11, 2023 at 07:38:02PM +0100, Stella Ashburne wrote: > Please see Greg's reply to my other post (URL: > https://lists.debian.org/debian-user/2023/12/msg00640.html). > > For your convenience, I quote a section of his reply (see below): > > "Yes, because linux-image-amd64 *right now* d

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

Hi Andy > Sent: Monday, December 11, 2023 at 11:25 PM > From: "Andrew M.A. Cater" > To: debian-user@lists.debian.org > Subject: Re: From which kernel should I upgrade my installed Debian to > linux-image-6.1.0-15-amd64? > > > If you're not currently booted into the erroneous 6.1.0-14 - don't boo

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

Albretch Mueller wrote: > echo "abc123" > file.txt > ftype=$(file --brief file.txt) > echo "// __ \$ftype: |${ftype}|" > ftypelen=${#ftype} > echo "// __ \$ftypelen: |${ftypelen}|" > > # removing spaces ... > ftype2=$(echo "${ftype}" | tr --complement --squeeze-repeats > '[A-Za-z0-9.]' '_'); > ec

Re: Image handling in mutt

On Mon, 11 Dec 2023, at 13:16, Greg Wooledge wrote: > 4) File extensions are used by programs on every operating system. Certainly on many OSes, but not all. They're not present on native RISC OS systems (as in ex-Acorn micros). Filetype data IS stored, but it is in files' metadata. There's n

Re: "echo" literally in sh scripts (was: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...)

On Mon, Dec 11, 2023 at 10:16:35AM -0500, Stefan Monnier wrote: > > 1) Many implementations of echo will interpret parts of their argument(s), > >in addition to processing options like -n. If you want to print a > >variable's contents to standard output without *any* interpretation, > >

Re: EIO error - I/O error

On 11 Dec 2023 15:46 +0100, from rachid.oub...@elum-energy.com (Rachid Oubelk): > Dear support team, A clarification; this mailing list is not a "support team". It's a group of people, many of which who share little more than the fact that they use Debian to varying degree, and with varying levels

Re: IMPORTANT: do NOT upgrade to new stable point release

I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and no problems! 2023-12-11, pr, 18:47 Махно rašė: > > I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and > no problems! > > > 2023-12-11, pr, 18:40 Michael Kjörling <2695bd53d...@ewoof.net> rašė: > > > > On 11 D

Re: IMPORTANT: do NOT upgrade to new stable point release

I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and no problems! 2023-12-11, pr, 18:40 Michael Kjörling <2695bd53d...@ewoof.net> rašė: > > On 11 Dec 2023 11:34 -0500, from g...@extremeground.com (Gary Dale): > > Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I

Re: IMPORTANT: do NOT upgrade to new stable point release

On 11 Dec 2023 11:34 -0500, from g...@extremeground.com (Gary Dale): > Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I assume > this is the fixed version. It certainly should be, but some people have reported other issues with the new 12.4 upgrade. See other recent posts to this

Re: IMPORTANT: do NOT upgrade to new stable point release

On 2023-12-09 13:09, Dan Ritter wrote: https://fulda.social/@Ganneff/111551628003050712 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 The new kernel release is reported to contain an ext4 data corruption bug. It's prudent not to upgrade, or if you have started to upgrade, not to re

Re: Image handling in mutt

On Mon 11 Dec 2023 at 10:03:38 (-0500), Pocket wrote: > On 12/11/23 09:52, David Wright wrote: > > On Sun 10 Dec 2023 at 15:51:02 (-0500), Pocket wrote: > > > > On Dec 10, 2023, at 3:05 PM, David Wright wrote: > > > > On Fri 08 Dec 2023 at 16:29:12 (-0500), Paul M Foster wrote: > > > > > > On Fri,

Re: EIO error - I/O error

Am 11.12.2023 um 16:39:47 Uhr schrieb Rachid Oubelk: > We received this message from our software based on the errno utility > (Linux Errors). The Debian used is installed on a controller that has > two serial ports (RTU) and two LAN ports (TCP). When we test these > two serial ports, we notice th

Re: Image handling in mutt

On Mon, Dec 11, 2023 at 10:10:31AM -0500, Stefan Monnier wrote: [...] > I think what you're saying is that it would make sense to use > a dedicated extension for executables, like, say, `.exe`, > since "all users rely on it being" executable. I'd prefer ".com", but hey ;-) > FWIW, I agree, but

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

On Mon, Dec 11, 2023 at 02:25:23PM +0100, Kevin Price wrote: > Am 11.12.23 um 14:16 schrieb Stella Ashburne: > > Suppose I wish to upgrade to linux-image-6.1.0-15-amd64. > > If that were the case, or maybe better to a newer one. > > > Should I do it after booting my device into > > (1) linux-imag

Re: Image handling in mutt

On Mon 11 Dec 2023 at 10:07:28 (+1100), Zenaan Harkness wrote: > > Second, how do I fix this so that mutt uses feh to display images? > > Here is my mailcap entry, which works for me - had to deal with > annoying filename munging by mutt, and getting the "close the viewer" > bit working - this is

Re: Image handling in mutt

songbird wrote: > wrote: > > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote: > >> wrote: > > there is rarely a need to e-mail me directly. > > >> ... > >> > That's why I cringe when people name executables "foo.sh". What > >> > do you do when you decide to rewrite the thing i

"echo" literally in sh scripts (was: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...)

> 1) Many implementations of echo will interpret parts of their argument(s), >in addition to processing options like -n. If you want to print a >variable's contents to standard output without *any* interpretation, >use printf. > > printf %s "$myvar" > printf '%s\n' "$myvar" In

Re: Image handling in mutt

On 2023-12-11 09:34:09 -0500, Pocket wrote: > On 12/11/23 09:04, Vincent Lefevre wrote: > > On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote: > > > 2) When *receiving* email, mutt will use the sender's MIME type label > > > to decide how to deal with the attachment. > > But the notion of filen

Re: Image handling in mutt

> (Note that I'd even make a difference: where the implementation matters, > e.g. some shell code to be sourced in, I'd be more lenient in calling > the thing ".sh": after all, its users rely on it being shell code. When > you can change the implementation without changing the function, e.g. > a sh

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 09:55:54AM -0500, Greg Wooledge wrote: [...] Greg, your analyses are always impressive. And enjoyable. Thanks for this cheers -- t signature.asc Description: PGP signature

Re: EIO error - I/O error

Am 11.12.2023 um 15:46:03 Uhr schrieb Rachid Oubelk: > Please, we are using Debian GNU/Linux 9.13 (stretch) installed on a > UC-8112-LX controller version 3.4, and it shows the error EIO ( IO > error ). Where does that error message appear? In which application?

Re: Image handling in mutt

On 12/11/23 09:52, David Wright wrote: On Sun 10 Dec 2023 at 15:51:02 (-0500), Pocket wrote: On Dec 10, 2023, at 3:05 PM, David Wright wrote: On Fri 08 Dec 2023 at 16:29:12 (-0500), Paul M Foster wrote: On Fri, Dec 08, 2023 at 11:04:54AM -0600, David Wright wrote: On Fri 08 Dec 2023 at 11:56

EIO error - I/O error

Dear support team, Please, we are using Debian GNU/Linux 9.13 (stretch) installed on a UC-8112-LX controller version 3.4, and it shows the error EIO ( IO error ). Could you please help us understand the cause of this error? Very urgent. Best regards, Rachid OUBELK

Re: Image handling in mutt

On Mon, Dec 11, 2023 at 08:52:37AM -0600, David Wright wrote: > On Sun 10 Dec 2023 at 15:51:02 (-0500), Pocket wrote: [...] > > File names in Linux are a character string of 255 chars. Again there are > > not file extensions in a Linux file name. > > > > People are conflating the issue. > > >

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 02:00:49PM +, Albretch Mueller wrote: > Ach, yes! I forgot echo by default appends a new line character at > the end of every string it spits out. In order to suppress it you need > to use the "n" option: "echo -n ..." > > _FL_TYPE=" abc á é í ó ú ü ñ Á É Í Ó Ú Ü Ñ

Re: Image handling in mutt

On Sun 10 Dec 2023 at 15:51:02 (-0500), Pocket wrote: > > On Dec 10, 2023, at 3:05 PM, David Wright wrote: > > On Fri 08 Dec 2023 at 16:29:12 (-0500), Paul M Foster wrote: > >>> On Fri, Dec 08, 2023 at 11:04:54AM -0600, David Wright wrote: > >>> On Fri 08 Dec 2023 at 11:56:12 (-0500), Paul M Foste

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On 11/12/2023 21:00, Albretch Mueller wrote: // __ $_FL_TYPE: |abc á é í ó ú ü ñ Á É Í Ó Ú Ü Ñ 123 birdie🐦here ¿ ¡ § ASCII ä ö ü ß Ä Ö Ü Text| // __ $_FL_TYPE:|abc_123_birdie_here_ASCII_Text| https://pypi.org/project/Unidecode/ should be more friendly to languages other than English.

Re: Release process notes [WAS Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)]

Hi Greg Thank you for taking the time to explain in detail. > Sent: Monday, December 11, 2023 at 10:16 PM > From: "Greg Wooledge" > To: debian-user@lists.debian.org > Subject: Re: Release process notes [WAS Need clarifications about how to > deal with the installed problematic kernel, linux-im

Re: Image handling in mutt

On 12/11/23 09:34, Vincent Lefevre wrote: On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote: On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote: I do not care about the "microsoft world", and I doubt that this is required there at the low level (what would be the equivalent of

Re: Image handling in mutt

On Mon, Dec 11, 2023 at 03:34:28PM +0100, Vincent Lefevre wrote: > On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote: > > On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote: > > > I do not care about the "microsoft world", and I doubt that this is > > > required there at the low lev

Re: Image handling in mutt

On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote: > On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote: > > I do not care about the "microsoft world", and I doubt that this is > > required there at the low level (what would be the equivalent of the > > Linux kernel) [...] > > This

Re: Image handling in mutt

On 12/11/23 09:04, Vincent Lefevre wrote: On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote: 2) When *receiving* email, mutt will use the sender's MIME type label to decide how to deal with the attachment. But the notion of filename extension is even used in this context too. Quoting the

Re: Image handling in mutt

On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote: [...] > I do not care about the "microsoft world", and I doubt that this is > required there at the low level (what would be the equivalent of the > Linux kernel) [...] This depends: the FAT file system (which still is the lowest c

Re: Release process notes [WAS Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)]

On Mon, Dec 11, 2023 at 02:35:07PM +0100, Stella Ashburne wrote: > Suppose linux-image-6.1.0-15-amd64 is installed successfully and I reboot my > device. > > A few days from now, I decide to remove linux-image-6.1.0-15-amd64 because it > is buggy and so in a terminal, I type the commands: > > s

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

Ach, yes! I forgot echo by default appends a new line character at the end of every string it spits out. In order to suppress it you need to use the "n" option: "echo -n ..." _FL_TYPE=" abc á é í ó ú ü ñ Á É Í Ó Ú Ü Ñ 123 birdie🐦here ¿ ¡ § ASCII ä ö ü ß Ä Ö Ü Text" echo "// __ \$_FL_TYPE:

Re: Image handling in mutt

On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote: > 2) When *receiving* email, mutt will use the sender's MIME type label >to decide how to deal with the attachment. But the notion of filename extension is even used in this context too. Quoting the Mutt manual: --

Re: Image handling in mutt

On 2023-12-11 07:32:30 -0500, Pocket wrote: > > On 12/11/23 07:12, Vincent Lefevre wrote: > > On 2023-12-10 15:51:02 -0500, Pocket wrote: > > > On Dec 10, 2023, at 3:05 PM, David Wright > > > wrote: > > > > ¹ Re the argument raging in this thread about "extension", the > > > > term is clearly

Re: Release process notes [WAS Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)]

Hi Andy > Sent: Monday, December 11, 2023 at 3:13 PM > From: "Andrew M.A. Cater" > To: debian-user@lists.debian.org > Subject: Release process notes [WAS Re: Need clarifications about how to deal > with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)] > > > linux-image-[f

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

Am 11.12.23 um 14:16 schrieb Stella Ashburne: > Suppose I wish to upgrade to linux-image-6.1.0-15-amd64. If that were the case, or maybe better to a newer one. > Should I do it after booting my device into > (1) linux-image-6.1.0-14-amd64 (the problematic kernel) NO. Don't ever boot that as it m

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

On Mon, Dec 11, 2023 at 02:16:39PM +0100, Stella Ashburne wrote: > (3) doesn't matter which kernel to upgrade from That.

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 02:11:46PM +0100, to...@tuxteam.de wrote: > On Mon, Dec 11, 2023 at 07:42:10AM -0500, Greg Wooledge wrote: > > Looks like GNU tr in Debian 12 still doesn't handle multibyte characters > > correctly: > > > > unicorn:~$ echo 'mañana' | tr ñ X > > maXXana > > Hey, you

From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

Hi As of now, I'm quite hesistant to upgrade my installed Debian Bookworm to linux-image-6.1.0-15-amd64 as there are two users who reported they have problems with it (cf. https://lists.debian.org/debian-user/2023/12/msg00570.html and https://lists.debian.org/debian-user/2023/12/msg00607.html)

Re: Image handling in mutt

On Mon, Dec 11, 2023 at 01:41:09PM +0100, Arno Lehmann wrote: > I do not see the relevance of the discussion about file name extensions, > types, suffixes for Debian. Even more so as you are at the stage of > repeating statements without bringing new value. In fact, there seems to be > no goal with

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 07:42:10AM -0500, Greg Wooledge wrote: > On Mon, Dec 11, 2023 at 09:37:42AM +0100, to...@tuxteam.de wrote: > > 2. This is tr, not regexp, so '[A-Za-z0-9.]' isn't doing what you > >think it does. It will match '[', 'A' to 'Z', 'a' to 'z','.' and > >']'. I guess you w

Re: Debian 12.3 image release delayed

Am 11.12.23 um 04:36 schrieb Stella Ashburne: > As for me, I won't be upgrading to the latest kernel just yet because a user, > Kevin Price, reported problems with the latest kernel version (cf. > https://lists.debian.org/debian-user/2023/12/msg00570.html) That _might_ be a good idea. Currently

Re: Image handling in mutt

David writes: > Hi, the filename extension is usually irrelevant on Linux, because > Linux tools typically > use the standard 'file' command to inspect the content of the > fileinstead of relying on > the filename to indicate content. It is very often not irrelevant for files that you might want

Re: Image handling in mutt

On Monday, 11 Dec 2023 at 07:32, Pocket wrote: > No it is microsoft non sense I'm not an MS fanboi but please stop blaming MS for something they did not invent! -- Eric S Fraga via gnus (Emacs 30.0.50 2023-09-14) on Debian 12.2

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 09:37:42AM +0100, to...@tuxteam.de wrote: > 2. This is tr, not regexp, so '[A-Za-z0-9.]' isn't doing what you >think it does. It will match '[', 'A' to 'Z', 'a' to 'z','.' and >']'. I guess you want to say 'A-Za-z0-9.' Well spotted. > 3. As a convenience, tr has

Re: Image handling in mutt

All, I do not see the relevance of the discussion about file name extensions, types, suffixes for Debian. Even more so as you are at the stage of repeating statements without bringing new value. In fact, there seems to be no goal with this thread. I would ask you to continue this discussion

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 11:25:13AM +, Albretch Mueller wrote: > In the case of: "ASCII text" > what should come out of it is: "ASCII_text" > not: "ASCII_text_" > no underscore at the end. That is the question I have. OK, here's my guess. The lines of code that you showed us are not actuall

Re: Image handling in mutt

On 12/11/23 07:12, Vincent Lefevre wrote: On 2023-12-10 15:51:02 -0500, Pocket wrote: On Dec 10, 2023, at 3:05 PM, David Wright wrote: ¹ Re the argument raging in this thread about "extension", the term is clearly appropriate, as a glance at /etc/mime.types demonstrates. The literature is

Re: Image handling in mutt

On 12/11/23 06:39, Vincent Lefevre wrote: On 2023-12-08 17:06:15 -0500, Pocket wrote: On 12/8/23 16:53, David wrote: Hi, the filename extension is usually irrelevant on Linux, because Linux tools typically use the standard 'file' command to inspect the content of the fileinstead of relying on

Re: Image handling in mutt

On 2023-12-10 15:51:02 -0500, Pocket wrote: > On Dec 10, 2023, at 3:05 PM, David Wright wrote: > > ¹ Re the argument raging in this thread about "extension", the > > term is clearly appropriate, as a glance at /etc/mime.types > > demonstrates. The literature is full of the term. > > > > I woul

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 11:25:13AM +, Albretch Mueller wrote: > "tr --complement --squeeze-repeats ..." makes sure that the replaced > characters only appear once (that it doesn't immediately repeat). Say > you have something like " " (two spaces) or "?$|" (three characters) > which will be r

Re: 12.4.0 point release published

On 11/12/2023 01:17, Steve McIntyre wrote: Hi folks, The new 12.4.0 point release is now out. It contains the needed fixes for the ext4 data corruption bug (https://bugs.debian.org/1057843). It's now safe to upgrade as normal, panic over. Many thanks to all the people who spent all of their we

Re: Image handling in mutt

On 2023-12-08 17:06:15 -0500, Pocket wrote: > On 12/8/23 16:53, David wrote: > > Hi, the filename extension is usually irrelevant on Linux, because > > Linux tools typically > > use the standard 'file' command to inspect the content of the > > fileinstead of relying on > > the filename to indicate

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

"tr --complement --squeeze-repeats ..." makes sure that the replaced characters only appear once (that it doesn't immediately repeat). Say you have something like " " (two spaces) or "?$|" (three characters) which will be replaced by just an underscore. In the case of: "ASCII text" what should

Re: 6.1.0-15/6.1.66-1 broken too?

Please see https://bugs.debian.org/1057967 for follow-up. Am 11.12.23 um 06:21 schrieb Stephan Verbücheln: [...] > My hardware is a 2014 Macbook Pro (Intel CPU and graphics). Stephan and all, would you please post your information there? TIA -- Kevin Price

Re: Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)

Hi Andy > Sent: Monday, December 11, 2023 at 3:20 PM > From: "Andrew M.A. Cater" > To: debian-user@lists.debian.org > Subject: Re: Need clarifications about how to deal with the installed > problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) > dpkg is low level: it will work to install o

Re: Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)

Hi Greg > Sent: Monday, December 11, 2023 at 11:40 AM > From: "Greg Wooledge" > To: debian-user@lists.debian.org > Subject: Re: Need clarifications about how to deal with the installed > problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) > > On Mon, Dec 11, 2023 at 04:31:22AM +0100, Stell

Re: 12.4.0 point release published

Hi, On Mon, Dec 11, 2023 at 01:17:19AM +, Steve McIntyre wrote: > Hi folks, > > The new 12.4.0 point release is now out. It contains the needed fixes > for the ext4 data corruption bug (https://bugs.debian.org/1057843). > > It's now safe to upgrade as normal, panic over. > > Many thanks to

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 08:04:06AM +, Albretch Mueller wrote: > On 12/11/23, Greg Wooledge wrote: > > Please tell us ... > > OK, here is what I did as a t-table [...] Your style is confusing, to say the least. Why not play with minimal examples and work your way up from that? > the two st

Re: Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)

On 11 Dec 2023 04:31 +0100, from rewe...@gmx.com (Stella Ashburne): > Someone on a social media platform stated that there are only two > "canonical" [sic] ways to verify the version of Debian installed on > a system. They are: > > uname -a > > /proc/version > > Do you agree with the above state

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On 12/11/23, Greg Wooledge wrote: > Please tell us ... OK, here is what I did as a t-table echo "abc123" > file.txt # obvious text file ftype=$(file --brief file.txt) # got its type as reported by the "file" utility echo "// __ \$ftype: |${ftype}|" ftypelen=${#ftype} # length of the string c