Posts
212
Following
23
Followers
1042

Jonathan Corbet

I went to Jasper many years ago and thought it was an amazing place; I've always intended to get back there. Not this year, I guess.

This sucks; we are losing our treasures.

https://www.npr.org/2024/07/25/nx-s1-5052037/jasper-alberta-canada-wildfire
0
0
0
@krans I think it would be a terrible mistake for LWN to do that. LWN is part of the history of the community; walling that off would damage both LWN and (I like to think, at least) the community badly.
0
0
2
@mcdanlj I've attempted such things, but the problem with playing whac-a-mole games is that there is an infinite supply of moles. I've found I can block a lot of subnets and not really make a dent in the problem.

I've started to wonder if some of these people aren't renting botnets to get around blocking, rate limiting, and other defenses.
1
0
2

Jonathan Corbet

The amount of LWN traffic that is just AI bots downloading the same stuff over and over again is staggering; it's increasingly hard to see any sort of human signal in there at all. Something is going to give here at some point...

https://about.readthedocs.com/blog/2024/07/ai-crawlers-abuse/
8
75
64
@gnomon Replacing URLs isn't that hard, whether there's hundreds of them or thousands - a properly written script doesn't care.

I mentioned lore (and the LWN mailing-list archive) in particular because they are based on public-inbox. That is a great piece of software, but it has some interesting design decisions. Behind public-inbox is a Git repository with a single file called "m". Each message added to the archive goes in as a patch to "m". A mailing-list archive is a long series of Git commits to that one file.

What this means is that changing a message in the archive comes down to a rebase operation. Lots of fun in an archive with millions of messages (and thus millions of commits to rebase) in it. It's doable, but it's not fast or easy. It's not what public-inbox was designed to do. Archived emails aren't meant to change.

Changing URLs in an email will also mess with things like DKIM validation, of course.

This is why I think it's unlikely that the linux-kernel archive (or the LWN archive) will be patched; it's a massive job. But perhaps @monsieuricon has a different view of things...?
1
0
1
@vegard Better but still really painful to fix; public-inbox is pretty firmly built around the idea that archived messages do not change.
5
0
5
@albertcardona I am thinking about hacking together a URL-replacement script for LWN. Doing that on lore, though (or the LWN email archive) would be a rather more painful prospect, to say the least. I would honestly be surprised if it actually got done.
0
2
12

Jonathan Corbet

Ah joy ... Google is turning off its URL shortener and breaking every link that ever used it:

https://developers.googleblog.com/en/google-url-shortener-links-will-no-longer-be-available/

A quick search on lore.kernel.org:

https://lore.kernel.org/all/?q=goo.gl%2F

...turns up about 19,000 messages with affected links. That's a lot of history that is going to become harder (or impossible) to find.
81
929
610

Jonathan Corbet

"To better understand how the kernel community views Rust,
we collect the posts about writing Rust drivers from lwn and
ycombinator until 2023/08/05, and use Chatgpt to analyze
them."

I guess that's research in the 2020s... https://www.usenix.org/conference/atc24/presentation/li-hongyu
7
11
13

Jonathan Corbet

Finally managed to ride the Medicine Bow rail trail in Wyoming - definitely worth it!
0
0
16
@gnomon @LWN @jzb I've fixed these, thanks, but that happened by chance. Mastodon is a poor way to report typos in LWN articles; email to lwn@lwn.net is, instead, sure to be seen by somebody.
1
0
2
@cesarb Interesting...the link still works fine for me...
0
0
0

Jonathan Corbet

The end of support for CentOS 7 has gotten a lot of attention — and perhaps caught a lot of people off-guard. But yesterday was also the EOL for Scientific Linux, which is kind of the end of an era. Scientific Linux was the main alternative to CentOS back in the day, and was widely used. FNAL got out of the distribution business and never put out a RHEL 8 clone, so Scientific Linux is now entirely gone. Thanks to FNAL for having supported such a useful distribution for so long!

https://scientificlinux.org/
1
17
17

Jonathan Corbet

I've worked in technology for decades, and am as fond as a nice gadget as any other ... and I like to see Linux everywhere ... but, somehow, a bed that one has to physically hack into to gain root access, and which as a backdoor providing remote shell access to the vendor is a step or three too far...

https://dillan.org/articles/how-to-get-root-access-to-your-sleep-number-bed
5
13
27

Jonathan Corbet

Daniel Bristot de Oliveira passed away a few days ago at far too young an age. Some of his associates have just asked us to publish their memories of him:

https://lwn.net/Articles/979912/

What an incredible loss.
0
16
21
@jalefkowit All credit to @jzb for that one — I'm glad to see that it was appreciated!
1
0
9
@dmarti @Sumocat @asymco The cost of insuring our Bolt is about half the cost of our internal-combustion car that, in theory, is worth less. State Farm, at least, appears to have come to a clear conclusion on that front.
1
0
1

Jonathan Corbet

Folks waiting for the extensible scheduler class will get it in 6.11: https://lwn.net/Articles/978007/
1
8
9

Jonathan Corbet

On the radar: using a large-language model to insert thousands of automatically generated "security checks" into the OpenBSD kernel:

https://marc.info/?l=openbsd-tech&m=171810103406609&w=2

I'm sure that will be received well...
8
9
22

Jonathan Corbet

Dangerous idiocy is not in short supply in the US but still this takes it to a new level.

https://cowboystatedaily.com/2024/06/07/hageman-tells-la-la-land-cities-to-give-up-fossil-fuels-if-theyre-so-evil/

Here in Boulder, I guess we can only bow to this superior logic and start tearing up our streets...
1
0
2
Show older