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
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
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
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
On Sun, Dec 10, 2023 at 02:27:38PM -0700, Charles Curley wrote:
> On Sat, 9 Dec 2023 13:09:23 -0500
> 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
On Sat, 9 Dec 2023 13:09:23 -0500
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
> sta
On Sun, Dec 10, 2023 at 01:36:52PM -0600, Nicholas Geovanis wrote:
> On Sun, Dec 10, 2023, 12:47 PM Curt wrote:
[...]
> > It is the notion of simultaneity itself (the now of now) that is
> > relative rather than universal.
> >
>
> I thought metaphysics was off-topic for this group. Moderators!!
On Sun, Dec 10, 2023, 12:47 PM Curt wrote:
> On 2023-12-10, Gary Dale wrote:
> >
> > On 2023-12-10 12:24, Greg Wooledge wrote:
> >> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> >>> On 2023-12-10, Andrew M.A. Cater wrote:
> "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
> >
On 2023-12-10, Gary Dale wrote:
>
> On 2023-12-10 12:24, Greg Wooledge wrote:
>> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
>>> On 2023-12-10, Andrew M.A. Cater wrote:
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
>>> You mean in the Zulu Time Zone (as I am all at sea)?
>>
On 2023-12-10 11:56, Andrew M.A. Cater wrote:
On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote:
On 2023-12-09 14:18, Michael Kjörling wrote:
On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou):
I just upgraded to Bookworm this morning. I did reboot a couple of
times b
On 2023-12-10 12:24, Greg Wooledge wrote:
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
On 2023-12-10, Andrew M.A. Cater wrote:
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
You mean in the Zulu Time Zone (as I am all at sea)?
Use "date -u" to see current UTC time. That sho
Andy writes:
> This fails with leap seconds, potentially, and also TAI astronomical
> time seems to be its own animal.
TAI isn't good enough for the astronomers.
https://en.wikipedia.org/wiki/Terrestrial_Time
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On Sun, Dec 10, 2023 at 05:20:40PM +, Andrew M.A. Cater wrote:
> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> > On 2023-12-10, Andrew M.A. Cater wrote:
> > >
> > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
> >
> > You mean in the Zulu Time Zone (as I am all at sea)?
> >
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> On 2023-12-10, Andrew M.A. Cater wrote:
> >
> > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
>
> You mean in the Zulu Time Zone (as I am all at sea)?
Use "date -u" to see current UTC time. That should be sufficient to
let you know
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> On 2023-12-10, Andrew M.A. Cater wrote:
> >
> > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
>
> You mean in the Zulu Time Zone (as I am all at sea)?
>
> > Andy
> > (amaca...@debian.org)
> >
> >
>
Not this again :) GMT (was) the
On 2023-12-10, Andrew M.A. Cater wrote:
>
> "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
You mean in the Zulu Time Zone (as I am all at sea)?
> Andy
> (amaca...@debian.org)
>
>
On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote:
> On 2023-12-09 14:18, Michael Kjörling wrote:
> > On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou):
> > > I just upgraded to Bookworm this morning. I did reboot a couple of
> > > times but there seems to be no problem (
On 2023-12-09 14:18, Michael Kjörling wrote:
On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou):
I just upgraded to Bookworm this morning. I did reboot a couple of
times but there seems to be no problem (yet). Is there anything I
should look for or do other than rebooting?
If
On 9 Dec 2023, at 19:18, Michael Kjörling wrote:
> If you are on 6.1.55-1 (or earlier), just hold off on
> upgrades for now; and if you need to upgrade something else, take
> great care for now to ensure that no Linux kernel packages get
> upgraded to any version < 6.1.66, and preferably not < 6.1
On Sat, 9 Dec 2023 19:18:20 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou):
> > I just upgraded to Bookworm this morning. I did reboot a couple of
> > times but there seems to be no problem (yet). Is there anything I
>
On 9 Dec 2023 14:26 -0500, from g...@wooledge.org (Greg Wooledge):
>> If you upgraded this morning, then I would expect that you are okay
>> for now.
>
> That doesn't appear to be true.
>
>> Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
>> the bug is present in kernel Debian
Greg Wooledge writes:
> On Sat, Dec 09, 2023 at 07:18:20PM +, Michael Kjörling wrote:
>> If you upgraded this morning, then I would expect that you are okay
>> for now.
>
> That doesn't appear to be true.
>
>> Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
>> the bug is p
On Sat, Dec 09, 2023 at 07:18:20PM +, Michael Kjörling wrote:
> If you upgraded this morning, then I would expect that you are okay
> for now.
That doesn't appear to be true.
> Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
> the bug is present in kernel Debian package ve
On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou):
> I just upgraded to Bookworm this morning. I did reboot a couple of
> times but there seems to be no problem (yet). Is there anything I
> should look for or do other than rebooting?
If you upgraded this morning, then I would ex
On Sat, 2023-12-09 at 13:09 -0500, Dan Ritter wrote:
>
>
> 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 reboot, until a new kernel release
> is prepared.
>
I just upgraded to Bookworm this m
09.12.23, 19:09 +0100, Dan Ritter:
> 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, n
Thanks for the tip. I updated this morning well before any
announcements and having seen this I rebooted into the 6.1.0-12 (6.1.52)
package. Good thing old kernels are kept around.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is t
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 reboot, until a new kernel release
is pre
28 matches
Mail list logo
