hlyg (12024-07-20):
> Thank David! market share is important though it isn't "reliable
> recommendation for quality": more users attract more programmers, who
> develop more apps,
The programmers who are attracted by market share are not necessarily
the ones who are interested in developing qualit
Thank David! market share is important though it isn't "reliable
recommendation for quality": more users attract more programmers, who
develop more apps, which attract more users. e.g. many vpn providers
support Windows and android, not linux.
linux can get distributed by word
On 2024-07-20, hlyg wrote:
> i wonder if linux is more reliable than Windows
no doubt :)
> according to some statistics linux has only 4% desktop market, 73% for MS, 15%
> for MacOS
Linux is not on the market. I buy M$ but download debian. How can you say
how many people is using deb
onal
> formats, it doesn't come preinstalled on almost every computer you buy:
> offered as the only option, Linux isn't advertised, and probably never
> will be.
All of them good factors. I may add yet another: because in the current
economic ideology, investing in things seems prefer
On Sat, 2024-07-20 at 11:54 +0800, hlyg wrote:
> crowdstrike makes news headlines, many Windows become blue screens
>
> it is evident that many people around still use Windows
>
> i wonder if linux is more reliable than Windows
>
> according to some statistics linux has o
crowdstrike makes news headlines, many Windows become blue screens
it is evident that many people around still use Windows
i wonder if linux is more reliable than Windows
according to some statistics linux has only 4% desktop market, 73% for
MS, 15% for MacOS
why free OS hasn't gained
Hi,
Vijay Kirpalani wrote:
> I am using xorriso to create a bootable Linux ISO and facing some issues.
> Please suggest what i might be doing wrong or missing.
I answered to your identical mail on bug-xorr...@gnu.org . See:
https://lists.gnu.org/archive/html/bug-xorriso/2024-07/msg
On Wed, Jul 17, 2024, 3:10 PM Bret Busby wrote:
> On 18/7/24 01:43, Andrew M.A. Cater wrote:
> > On Wed, Jul 17, 2024 at 05:52:47PM +0200, Aleix Piulachs wrote:
> >> installing w4sp-lab in Kali-linux-2024.2-installer-everything-amd64.iso
> >> gives me an error whe
On 18/7/24 05:22, Andrew M.A. Cater wrote:
On Wed, Jul 17, 2024 at 10:37:38PM +0200, Aleix Piulachs wrote:
I am installing with virtualbox w4sp-lab to
kali-linux-2024.2-installer-everything-amd64.iso and the module (import
w4sp from w4sp_webapp.py ) gives an error: import os import re import
On Wed, Jul 17, 2024 at 10:37:38PM +0200, Aleix Piulachs wrote:
> I am installing with virtualbox w4sp-lab to
> kali-linux-2024.2-installer-everything-amd64.iso and the module (import
> w4sp from w4sp_webapp.py ) gives an error: import os import re import sys
> import pwd import
On 18/7/24 01:43, Andrew M.A. Cater wrote:
On Wed, Jul 17, 2024 at 05:52:47PM +0200, Aleix Piulachs wrote:
installing w4sp-lab in Kali-linux-2024.2-installer-everything-amd64.iso
gives me an error when I press w4sp_webapp.py in python module error:
import w4sp and error in module: from w4sp_app
On Wed, Jul 17, 2024 at 05:52:47PM +0200, Aleix Piulachs wrote:
> installing w4sp-lab in Kali-linux-2024.2-installer-everything-amd64.iso
> gives me an error when I press w4sp_webapp.py in python module error:
> import w4sp and error in module: from w4sp_app import * and I cannot change
&
Prajnanaswaroopa,
What sources are you using to upgrade from?
e.g. what do you see for:
# cat /etc/apt/sources.list
I do not know what Kali Linux might use for non-free firmware.
Debian Bookworm can use something like:
deb https://deb.debian.org/debian/ bookworm main non-free
non-free
On Tue, Jul 16, 2024 at 19:30:20 -, Prajnanaswaroopa wrote:
> Hello,
> I am using a Kali Linux
https://www.google.com/search?q=kali+linux+support
Hello,
I am using a Kali Linux 6.6.9 version. When I tried to update and upgrade, the
terminal shows that the header linux-header-6.8.11-amd64 cannot be installed. I
tried several commands, but all seen to return the same comment. In addition,
the error the terminal shows is as follows
e...@gmx.us wrote:
> On 6/4/24 10:59, songbird wrote:
>> t...@tommiller.us wrote:
>>
>>> Hello!
>>>
>>> last(1) seems to have disappeared following an upgrade from 12.5 to sid.
>> ...
>>
>>i've been using the "more" com
Ash Joubert wrote:
> On 2024-06-05 02:59, songbird wrote:
>> t...@tommiller.us wrote:
>>> last(1) seems to have disappeared following an upgrade from 12.5 to sid.
>>i've been using the "more" command provided by the util-linux
>> package.
>
>
On 2024-06-05 02:59, songbird wrote:
t...@tommiller.us wrote:
last(1) seems to have disappeared following an upgrade from 12.5 to sid.
i've been using the "more" command provided by the util-linux
package.
You might be thinking of less(1), a program similar to more(1). The
On 6/4/24 10:59, songbird wrote:
t...@tommiller.us wrote:
Hello!
last(1) seems to have disappeared following an upgrade from 12.5 to sid.
...
i've been using the "more" command provided by the util-linux
package.
How do you use "more" to do what "last&quo
t...@tommiller.us wrote:
> Hello!
>
> last(1) seems to have disappeared following an upgrade from 12.5 to sid.
...
i've been using the "more" command provided by the util-linux
package.
songbird
subscribed to this list.
>
> Thanks for your help!
>
> Best!
>
> Tom
>
> <8>
>
> # Prior to upgrade, last(1) is present in 12.5
>
> root@lol ~ # cat /etc/debian_version
>
> 12.5
>
> root@lol ~ # which last
>
> /usr/
On 2024-06-04 16:09, t...@tommiller.us wrote:
last(1) seems to have disappeared following an upgrade from 12.5 to sid.
I remember seeing in the NEWS for util-linux that last(1) was moved to
the wtmpdb package:
$ zcat /usr/share/doc/util-linux/NEWS.Debian.gz
util-linux (2.40.1-2) unstable
ior to upgrade, last(1) is present in 12.5
root@lol ~ # cat /etc/debian_version
12.5
root@lol ~ # which last
/usr/bin/last
root@lol ~ # last --version
last from util-linux 2.38.1
root@lol ~ #
# Update, upgrade, and reboot 12.5 to prepare for sid
root@lol ~ # apt-get update && apt-get f
On 4/6/24 16:30, Roy J. Tellason, Sr. wrote:
On Saturday 06 April 2024 11:05:52 am Curt wrote:
On 2024-04-05, John Hasler wrote:
Desktop Linux is widely used in physics and mathematics. NASA uses
Linux extensively, including on Mars and on the ISS. SpaceX uses Linux
on their rockets and
On Saturday 06 April 2024 11:05:52 am Curt wrote:
> On 2024-04-05, John Hasler wrote:
> > Desktop Linux is widely used in physics and mathematics. NASA uses
> > Linux extensively, including on Mars and on the ISS. SpaceX uses Linux
> > on their rockets and spacecraft.
On 2024-04-06, gene heskett wrote:
> On 4/6/24 11:07, Curt wrote:
>> On 2024-04-05, John Hasler wrote:
>>> Desktop Linux is widely used in physics and mathematics. NASA uses
>>> Linux extensively, including on Mars and on the ISS. SpaceX uses Linux
>>> on th
On 4/6/24 11:07, Curt wrote:
On 2024-04-05, John Hasler wrote:
Desktop Linux is widely used in physics and mathematics. NASA uses
Linux extensively, including on Mars and on the ISS. SpaceX uses Linux
on their rockets and spacecraft. Over 90% of the top 1 million Web
servers run Linux
On 2024-04-05, John Hasler wrote:
> Desktop Linux is widely used in physics and mathematics. NASA uses
> Linux extensively, including on Mars and on the ISS. SpaceX uses Linux
> on their rockets and spacecraft. Over 90% of the top 1 million Web
> servers run Linux, including Yahoo,
On 4/6/24 09:15, Thomas Schmitt wrote:
Hi,
Nicholas Geovanis wrote:
But what if next time the back-doored software _does_ build without error?
The initial build problems did not cause suspicion.
It was the CPU load of sshd and an obscure complaint by valgrind which
caused the discovery.
ht
Hi,
Nicholas Geovanis wrote:
> But what if next time the back-doored software _does_ build without error?
The initial build problems did not cause suspicion.
It was the CPU load of sshd and an obscure complaint by valgrind which
caused the discovery.
https://boehs.org/node/everything-i-know-abo
On Fri, Apr 5, 2024, 1:39 PM wrote:
> On Fri, Apr 05, 2024 at 12:27:03PM -0400, Cindy Sue Causey wrote:
> > Hi, All..
> >
> > This just hit my emails seconds ago. It's the most info that I've
> > personally read about the XZ backdoor exploit. I've been following
> > NextGov as a friendly, plain l
On Fri, 5 Apr 2024 13:38:50 -0700
"James H. H. Lampert" wrote:
> Which is why I still have DOS boxes (running IBM PC-DOS 2000,
> with DOSShell, and no WinDoze whatsoever….
You might look into freedos.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.
On 4/5/24 16:42, James H. H. Lampert wrote:
I will note that open source software has, by definition, a lot more
eyes looking at the source. Which is probably why (as Tomas said)
"proprietary software tends to fare significantly worse."
--
JHHL
.
In light of that its worth noting that an M$ e
Cindy Sue Causey wrote:
> Continues to sound like one single perp is destroying the TRUST
> factor that an untold number of future programmers must meet. That's
> heartbreaking.
It has never sounded like a single perp to me. 'Jia Tan' is an obvious
sock puppet as are the other names who pushed L
I will note that open source software has, by definition, a lot more
eyes looking at the source. Which is probably why (as Tomas said)
"proprietary software tends to fare significantly worse."
--
JHHL
On 4/5/24 12:12 PM, Nate Bargmann wrote:
. . .
Most of the time the platform is dictated by the application(s) a
user wants to run. . . .
Indeed. Which is why I still have DOS boxes (running IBM PC-DOS 2000,
with DOSShell, and no WinDoze whatsoever: Xerox Ventura Publisher
(DOS/GEM Edition)
On Fri, Apr 05, 2024 at 08:38:36PM +0200, to...@tuxteam.de wrote:
[...]
> No, on the contrary. First of all, it is great that it has been
> caught /before/ it could cause much harm [...]
...and of course kudos and thans to Andres Freund who spotted
the thing!
Cheers
--
t
signature.asc
Descri
* On 2024 05 Apr 12:37 -0500, William Torrez Corea wrote:
> My colleague uses Windows, another uses Mac OS while I use Debian Gnu/Linux
> 12.
Choice is good.
> The majority of users use Windows while developers and designers use mac os
> but a little of people use Debian Gnu/Linux
* On 2024 05 Apr 11:28 -0500, Cindy Sue Causey wrote:
> Hi, All..
>
> This just hit my emails seconds ago. It's the most info that I've
> personally read about the XZ backdoor exploit. I've been following
> NextGov as a friendly, plain language resource about governm
On 4/5/24 11:35 AM, John Hasler wrote:
Desktop Linux is widely used in physics and mathematics. NASA uses
Linux extensively, including on Mars and on the ISS. SpaceX uses Linux
on their rockets and spacecraft. Over 90% of the top 1 million Web
servers run Linux, including Yahoo, X, and Ebay
On Fri, Apr 05, 2024 at 12:27:03PM -0400, Cindy Sue Causey wrote:
> Hi, All..
>
> This just hit my emails seconds ago. It's the most info that I've
> personally read about the XZ backdoor exploit. I've been following
> NextGov as a friendly, plain language resourc
Desktop Linux is widely used in physics and mathematics. NASA uses
Linux extensively, including on Mars and on the ISS. SpaceX uses Linux
on their rockets and spacecraft. Over 90% of the top 1 million Web
servers run Linux, including Yahoo, X, and Ebay. Almost all
supercomputers use Linux
William Torrez Corea writes:
[...]
> The majority of users use Windows while developers and designers use
> mac os but a little of people use Debian Gnu/Linux 12. So, what is the
> goal of having this distribution?.
Translating from a contemporary italian philosopher, the answe
My colleague uses Windows, another uses Mac OS while I use Debian Gnu/Linux
12.
The majority of users use Windows while developers and designers use mac os
but a little of people use Debian Gnu/Linux 12. So, what is the goal of
having this distribution?.
I use in Debian Gnu/Linux the following
Hi, All..
This just hit my emails seconds ago. It's the most info that I've
personally read about the XZ backdoor exploit. I've been following
NextGov as a friendly, plain language resource about government:
Linux backdoor was a long con, possibly with nation-state support, expert
On Sat, Feb 10, 2024 at 01:21:55PM +, Schwibinger Michael wrote:
> Yes.
>
>
> I found out
> I do use an old kernel.
>
> Can LINUX update a kernel?
>
Hi Sophie,
Yes, of course. As root/sudo user, apt-get update ; apt-get dist-upgrade
But you still don't giv
On Sat, Feb 10, 2024 at 08:45:32AM +0100, Thomas Schmitt wrote:
> Hi,
>
> Greg Wooledge wrote:
> > > The readline library is released under the full GPL, not the LGPL. If
> > > you dynamically link it with a program, then you can only release that
> > > program under terms compatible with the GPL
Hi,
Greg Wooledge wrote:
> > The readline library is released under the full GPL, not the LGPL. If
> > you dynamically link it with a program, then you can only release that
> > program under terms compatible with the GPL. This is an intentional
> > choice.
to...@tuxteam.de wrote:
> Practically
On Fri, Feb 09, 2024 at 06:36:18PM -0500, Greg Wooledge wrote:
[...]
> The readline library is released under the full GPL, not the LGPL. If
> you dynamically link it with a program, then you can only release that
> program under terms compatible with the GPL. This is an intentional
> choice.
>
On Fri, Feb 09, 2024 at 03:20:46PM -0800, Van Snyder wrote:
> On Fri, 2024-02-09 at 17:37 -0500, Greg Wooledge wrote:
> > On Fri, Feb 09, 2024 at 02:30:54PM -0800, Van Snyder wrote:
> > > Years ago, I knew the name of the routines one could use to have some
> > > stdin history and be able to edit i
On Fri, 2024-02-09 at 17:37 -0500, Greg Wooledge wrote:
> On Fri, Feb 09, 2024 at 02:30:54PM -0800, Van Snyder wrote:
> > Years ago, I knew the name of the routines one could use to have some
> > stdin history and be able to edit it, like you can do in XTerm or
> > gnuplot or
> >
> > I can't
Hi,
Van Snyder wrote:
> Years ago, I knew the name of the routines one could use to have some stdin
> history and be able to edit it, like you can do in XTerm or gnuplot or
Sounds like readline:
https://en.wikipedia.org/wiki/GNU_Readline
https://tracker.debian.org/pkg/readline
An altern
On Fri, Feb 09, 2024 at 02:30:54PM -0800, Van Snyder wrote:
> Years ago, I knew the name of the routines one could use to have some
> stdin history and be able to edit it, like you can do in XTerm or
> gnuplot or
>
> I can't remember them now, or find them.
I think you're talking about the r
Years ago, I knew the name of the routines one could use to have some
stdin history and be able to edit it, like you can do in XTerm or
gnuplot or
I can't remember them now, or find them.
Does anybody know the names?
Thanks,
Van Snyder
Hi Sven,
Sven Joachim writes:
> On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
>
>> (Please keep me in CC as I'm not subscribed to the users ML.)
>>
>> Hi,
>>
>> TL;DR I've been experience stuck file system operations on cifs mount on
>> latest
On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
> (Please keep me in CC as I'm not subscribed to the users ML.)
>
> Hi,
>
> TL;DR I've been experience stuck file system operations on cifs mount on
> latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
&
(Please keep me in CC as I'm not subscribed to the users ML.)
Hi,
TL;DR I've been experience stuck file system operations on cifs mount on
latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
like to see if other people are seeing similar issue before actually
fi
On Wed, 24 Jan 2024 07:33:59 +
Tixy wrote:
> On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote:
> [...]
>
> As you've already found out, that's not the latest one, and if I'm not
> mistaken is the one that introduce a wifi bug [1], so that could
> explain it getting stuck in the wif
er kernel. I had recently installed Bookworm from the 12.0
> netinst CD image, so I had the 12.0 kernel, linux-image-6.1.0-9-amd64,
> 6.1.27-1, as my fall-back kernel. I rebooted to that, and was able to
> shut down and boot in quick order.
>
> So I purged the newer kernel, inux-im
On Wed, 24 Jan 2024 09:25:58 +0700
Max Nikulin wrote:
> On 24/01/2024 03:34, Charles Curley wrote:
> > So I purged the newer kernel, inux-image-6.1.0-15-amd64
>
> The current kernel is linux-image-6.1.0-17-amd64
>
> Perhaps you have not restored your sources.list or ap
On 24/01/2024 03:34, Charles Curley wrote:
So I purged the newer kernel, inux-image-6.1.0-15-amd64
The current kernel is linux-image-6.1.0-17-amd64
Perhaps you have not restored your sources.list or apt preferences after
the accidents with kernel bugs. Check that nothing extra is added and
run chromium, I get:
>
> charles@jhegaala:~$ chromium &
> [2] 33609
> charles@jhegaala:~$ libva error:
> /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
>
> charles@jhegaala:~$
I seem to have solved this problem, entirely by accident.
I went to shut down the
On 19/01/2024 04:08, Charles Curley wrote:
charles@jhegaala:~$ chromium chrome://gpu
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
^C
Killed
charles@jhegaala:~$
I did a killall -9 in another window to kill it.
Does it happen in the case of a new system user and a new
On 19/01/2024 04:08, Charles Curley wrote:
On Fri, 19 Jan 2024 00:02:44 +0700
Max Nikulin wrote:
Have you faced real issues namely with hardware acceleration?
Other than this, not that I know of.
I do not think the message concerning iHD is related to any real issue.
I see "oops" in the
itches in
https://peter.sh/experiments/chromium-command-line-switches/, to no
avail.
>
> chrome://gpu may provide more info.
>
Alas, chromium never gets far enough to deliver useful information.
charles@jhegaala:~$ chromium chrome://gpu
libva error: /usr/lib/x86_64-linux-gnu/dri
On 14/01/2024 00:19, Charles Curley wrote:
charles@jhegaala:~$ chromium &
[2] 33609
charles@jhegaala:~$ libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
charles@jhegaala:~$ vainfo
libva info: VA-API version 1.17.0
libva info: Trying to open
/usr/lib/x86_64-linux-gnu
aala:~$ libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
charles@jhegaala:~$ ps
PID TTY TIME CMD
32502 pts/800:00:00 bash
32506 pts/800:00:04 emacs
33609 pts/800:00:00 chromium
33630 pts/800:00:00 chromium
33631 pts/800:00:00 chromium
3
Subject: I have successfully installed Debian Linux 12.4.0 on my refurbished HP
EliteBook 840 G1 laptop on 21 Dec 2023 Thursday
Good day from Singapore,
I have successfully installed Debian Linux 12.4.0 on my refurbished HP
EliteBook 840 G1 laptop on 21 Dec 2023 Thursday. It was done using
server that upgraded. I haven't set any
> special policies on upgrades.
I saw similar here. Of four machines here running Bookworm, three have
kernels:
linux-image-6.1.0-15-amd64 6.1.66-1
linux-image-6.1.0-16-amd64 6.1.67-1
but one has:
linux-image-6.1.0-13-amd64 6.1.55-1
linux-image-6.1
On Thu, Dec 21, 2023 at 09:02:34AM -0500, Gary Dale wrote:
> Several days ago my main server upgraded to kernel 6.1.0-16 but various
> other devices that are also running Bookworm seem stuck at 6.1.0-13. They
> are all using the same architecture. Some are using the same mirror as the
> server that
Several days ago my main server upgraded to kernel 6.1.0-16 but various
other devices that are also running Bookworm seem stuck at 6.1.0-13.
They are all using the same architecture. Some are using the same mirror
as the server that upgraded. I haven't set any special policies on upgrades.
Can
Hi Greg
> Sent: Tuesday, December 12, 2023 at 2:43 AM
> From: "Greg Wooledge"
> 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?
>
> On Mon, Dec 11, 2023 at 07:38:02PM +0100, St
On 11 Dec 2023 21:45 -0700, from charlescur...@charlescurley.com (Charles
Curley):
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967
And from the looks of that bug report thread, message #72 onwards,
there is now a candidate fix.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105796
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
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
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 dependen
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
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 boo
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 d
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
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 ty
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
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 b
On Mon, Dec 11, 2023 at 02:16:39PM +0100, Stella Ashburne wrote:
> (3) doesn't matter which kernel to upgrade from
That.
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
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 le
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, D
e version reported by a program itself.
A lot of the time, something like "current up-to-date Bookworm" or
"Bookworm per " is sufficiently precise, as long as you
have confirmed that this is actually the case.
>>> sudo dpkg -i linux-image-6.1.0-13-amd64
>>&g
fications about how to deal with the installed
> > problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
> >
> >
> > This combination is expected under the circumstances, assuming that
> > you mean /etc/debian_version. Booting into a different kernel does not
>
On Mon, Dec 11, 2023 at 03:32:55AM +0100, Stella Ashburne wrote:
> Hi Greg
>
> > Sent: Sunday, December 10, 2023 at 11:08 PM
> > From: "Greg Wooledge"
> > To: debian-user@lists.debian.org
> > Subject: Re: Need clarifications about how to deal with the
Hi Greg
> Sent: Monday, December 11, 2023 at 11:27 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)
>
>
> Well, th
On Mon, Dec 11, 2023 at 04:31:22AM +0100, Stella Ashburne wrote:
> 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 statement
Hi Michael
> Sent: Sunday, December 10, 2023 at 9:29 PM
> From: "Michael Kjörling" <2695bd53d...@ewoof.net>
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-
On Mon, Dec 11, 2023 at 03:26:16AM +0100, Stella Ashburne wrote:
> What command did you use? Was it
>
> sudo dpkg -i linux-image-amd64_6.1.55-1_amd64.deb
Yes.
On Mon, Dec 11, 2023 at 03:32:55AM +0100, Stella Ashburne wrote:
> As of writing this reply, there's a new poin
Hi Greg
> Sent: Sunday, December 10, 2023 at 11:08 PM
> 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)
>
>
> Note that
Hi Greg
> Sent: Monday, December 11, 2023 at 2:06 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)
>
>
> In order
On Sun, Dec 10, 2023 at 10:08:21AM -0500, Greg Wooledge wrote:
> On Sun, Dec 10, 2023 at 01:41:14PM +, Andrew M.A. Cater wrote:
> > That will work: you might also want to apt-get purge
> > linux-image-6.1.0-14-amd64
> > but you've done the main thing.
>
> Note
On Sun, Dec 10, 2023 at 01:41:14PM +, Andrew M.A. Cater wrote:
> That will work: you might also want to apt-get purge
> linux-image-6.1.0-14-amd64
> but you've done the main thing.
Note that purging 6.1.0-14 will also remove the linux-image-amd64
metapackage, which has a hard
d to my computer many hours ago.
>
> My device upgraded to the latest kernel, linux-image-6.1.0-14-amd64 and
> rebooted.
>
Yes, this was a problem that surfaced properly half way through the release
process. The release team had already put out the main updates: I was involved
with t
On 10 Dec 2023 13:48 +0100, from rewe...@gmx.com (Stella Ashburne):
> I highlight linux-image-6.1.0-13-amd64 and press Enter.
>
> After supply the decryption password and entering my desktop
> environment, I did the following:
>
> cat /etc/debian_user
> *Result* is 12.3, eve
101 - 200 of 22681 matches
Mail list logo
