Posts
268
Following
26
Followers
1255
@pkal Heh ... one could have a *lot* of fun playing with that idea...
1
0
1
@jwf NAK (or NACK) - negative acknowledge - is a curt way of saying that a patch will be rejected.
0
0
3
@brauner I'm digging through the whole Asahi Lina graphics driver story, but it's something I've often thought.
2
0
4

Jonathan Corbet

Edited 4 months ago
The more I dig through kernel mailing list discussions, the more I think that we would do well to end the use of "NAK" entirely. It is an exercise of power that is hurtful to read and gets in the way of an actual discussion of how a patch needs to be improved. I have, in my maintainer role, never said "NAK" to a patch and plan to continue that way.

*Edited* since people are asking: NAK (or NACK) comes (I believe) from the ASCII negative-acknowledge character. In this context, is an abrupt way for a maintainer to reject a patch.
11
34
108
@lina If you approach a large city with a plan to install a shiny new utility system, you will quickly find yourself dealing with a whole range of bureaucrats, some of whom will be more helpful than others. The kernel project resembles that large city in a number of ways. I don't say this is a good thing, but it is a thing.

I believe that the Rust for Linux project is succeeding. Yes, it is slow and painful, but the people pushing this work are doing the right things and making progress.

The city council (the maintainers summit) is meeting on September 17. Rust will be on the agenda, and there should be a couple of Rust for Linux developers there. That would be a good time to have a well-thought-out proposal for process changes that you would like to see.
2
4
20
@lina Extrapolating one developer's words into "this is what kernel maintainers think" is an obvious logical failure and is not the way to advance the Rust cause. The fact that several kernel maintainers spoke out against the "unmerged toy" description makes it clear that it is not a majority opinion. There are a lot of people in the kernel community who support this work.
1
1
9
@jarkko I hate to say it, but I think you are setting an impossible standard here. Is there any subsystem in the kernel, written in any language, that is so well documented that a developer unfamiliar with the implementation language could understand a patch to it?

The kernel's documentation is ... not great ... and it seems to me that the Rust folks are trying to do a little better.
1
0
7

Jonathan Corbet

I'll answer your email soon, honest, but first I have some important meetings to get through...
1
5
40

Jonathan Corbet

@oleksandr Ouch ... it is sad indeed to see a site like that go down. "the market for written tech journalism is not what it once was – nor will it ever be again" - indeed.

RE: https://activitypub.natalenko.name/@oleksandr/statuses/01J6HPBQ5S4S1W6H5R172A6GMT
0
1
4

Jonathan Corbet

This year's COVID vaccine is coming out in the US. Just booked my appointment so I can get jabbed ahead of the fall travel nightmare.
1
1
15
@evan We (LWN - @LWN) maintain an events calendar at https://lwn.net/Calendar/, with an associated call-for-proposals calendar at https://lwn.net/Calendar/Monthly/cfp/ . We're focused on the Linux and free-software worlds, but try to be fairly comprehensive within it.
0
9
11

Jonathan Corbet

If you want to know where the action is in a wildfire, just follow the aircraft. I'm supposed to be getting work done, but its hard, especially when they keep flying over my house.

Hopefully they are starting to get a handle on some of these.
0
0
8

Jonathan Corbet

So there are fires burning up and down the Colorado front range. At least one person has died already. The air inside the house makes my eyes burn. It seems like a good time to be careful.

There are people seriously talking about the possibility of a serial arsonist setting these things off. But, then, some idiots decided that last night would be a good time to go play with fireworks above town and duly set another one. I guess we should not attribute to malice that which can be explained by appalling stupidity.
1
0
9
@basha Most of the crawlers do not even identify themselves as such; they will not consult the robots.txt file. There are no solutions to be found there, unfortunately.
0
0
0

Jonathan Corbet

There are now two fires visible from my house... Slurry bombers overhead. Still a tiny problem compared to what some others are dealing with, but still... this sucks.
1
0
11

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
3
@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/
10
75
73
Show older