But you don't ever need to do that.

But it's far quicker and more fun if you do.

 

I thought it was called after a gal called Deb ... but whatever ...

she was his girlfriend (according to Wikipedia)

 

she was his girlfriend (according to Wikipedia)

Lol! ... that, I didn't know!

 

Lol! ... that, I didn't know!

Now his wife (according to Wikipedia)

 

Now his wife (according to Wikipedia)

ex-wife!

 

https://lore.kernel.org/lkml/CAHk-=wj2WqpPBwpAXo8bj_Hx-NxKMRVTVMUaQis7+Vm6XLRZiw@mail.gmail.com/T/#u

Linux 7.0
@ 2026-04-12 21:03 Linus Torvalds
0 siblings, 0 replies; only message in thread
From: Linus Torvalds @ 2026-04-12 21:03 UTC (permalink / raw)
To: Linux Kernel Mailing List

The last week of the release continued the same "lots of small fixes"
trend, but it all really does seem pretty benign, so I've tagged the
final 7.0 and pushed it out.

I suspect it's a lot of AI tool use that will keep finding corner
cases for us for a while, so this may be the "new normal" at least for
a while. Only time will tell.

Anyway, this last week was a little bit of everything: networking
(core and drivers), arch fixes, tooling and selftests, and various
random fixes all over the place.

Let's keep testing, and obviously tomorrow the merge window for 7.1
opens. I already have four dozen pull requests pending - thank you to
all the early people.

Linus

 

https://lore.kernel.org/lkml/CAHk-=wj2WqpPBwpAXo8bj_Hx-NxKMRVTVMUaQis7+Vm6XLRZiw@mail.gmail.com/T/#u

Linux 7.0
@ 2026-04-12 21:03 Linus Torvalds
0 siblings, 0 replies; only message in thread
From: Linus Torvalds @ 2026-04-12 21:03 UTC (permalink / raw)
To: Linux Kernel Mailing List

The last week of the release continued the same "lots of small fixes"
trend, but it all really does seem pretty benign, so I've tagged the
final 7.0 and pushed it out.

I suspect it's a lot of AI tool use that will keep finding corner
cases for us for a while, so this may be the "new normal" at least for
a while. Only time will tell.

Anyway, this last week was a little bit of everything: networking
(core and drivers), arch fixes, tooling and selftests, and various
random fixes all over the place.

Let's keep testing, and obviously tomorrow the merge window for 7.1
opens. I already have four dozen pull requests pending - thank you to
all the early people.

Linus

I kinda miss 2.4. Those were the days...

 

I kinda miss 2.4. Those were the days...

I miss the 0.9 days too. I was a lot younger then.

The old kernels are a pain to add new code to, as lots of things that are auto-detected today had to be hard-coded in the kernel static configuration source code.

https://forum.allaboutcircuits.com/threads/a-few-questions-about-an-audio-codec.152269/post-1307454

 

I kinda miss 2.4. Those were the days...

I just realized: I have an old AMD64 laptop still doing daily duty in the production shop running a 2.6 kernel:

 

I just realized: I have an old AMD64 laptop still doing daily duty in the production shop running a 2.6 kernel:

View attachment 366193

​

 

View attachment 366195
​

I used the photo editor on my phone to erase some potentially identifying info. I guess it uses AI to patch up the photo. I didn't realize it watermarks the resulting image -- until you noticed it.

Unintended consequences, and all that.

 

https://lore.kernel.org/linux-cve-announce/2026042214-CVE-2026-31431-3d65@gregkh/T/

Affected and fixed versions
===========================

Issue introduced in 4.14 with commit 72548b093ee38a6d4f2a19e6ef1948ae05c181f7 and fixed in 6.18.22 with commit fafe0fa2995a0f7073c1c358d7d3145bcc9aedd8
Issue introduced in 4.14 with commit 72548b093ee38a6d4f2a19e6ef1948ae05c181f7 and fixed in 6.19.12 with commit ce42ee423e58dffa5ec03524054c9d8bfd4f6237
Issue introduced in 4.14 with commit 72548b093ee38a6d4f2a19e6ef1948ae05c181f7 and fixed in 7.0 with commit a664bf3d603dc3bdcf9ae47cc21e0daec706d7a5

 

https://security-tracker.debian.org/tracker/CVE-2026-31431
Vulnerable and fixed packages
The table below lists information on source packages.

Source Package	Release	Version	Status
linux (PTS)	bullseye	5.10.223-1	vulnerable
	bullseye (security)	5.10.251-3	vulnerable
	bookworm	6.1.159-1	vulnerable
	bookworm (security)	6.1.164-1	vulnerable
	trixie	6.12.73-1	vulnerable
	trixie (security)	6.12.85-1	fixed
	forky	6.19.14-1	fixed
	sid	7.0.3-1	fixed

 

Building up a old SCSI SE system on the spare server to check data on a old SCIS raid box.
I have a old PCI Adaptec AVA-2906, I needed a PCI-E to PCI adapter what would work with the HPE DL360.
https://theretroweb.com/expansioncards/s/adaptec-ava-2906



I also tested a few PCI sound cards.

https://www.philscomputerlab.com/santa-cruz.html



Now that that's working I can dig out the old 8 inch hard-drive chassis for one last check before donating the formatted drives. Don't think it's been powered up for almost 20 years.

 

I had to do something similar for an old HP LTO drive a few years ago.

 

Reminds me of the AH-2940 controllers, I still have a couple of them buried somewhere...

 

https://theretroweb.com/expansioncard/documentation/20738.pdf
https://theretroweb.com/expansioncards/s/adaptec-aaa-131u2

 

Let's see if I can get this old FH 5 1/4 drive set to spin-up one more time.

https://www.seagate.com/staticfiles/support/disc/iguides/scsi/9130a.pdf

 

...one more time.

One more time? Put it in production!

 

One more time? Put it in production!

But that's where it was before retirement!





/dev/sdb is dead and /dev/sdc is giving media errors when I try to assemble the raid.


Will try a low-level format on sdc, partition it for a raid drive and try to add it to a three drive raid. Wake me in a few hours.