Nah, people just started using LLM assisted vuln discovery workflows and having early successes with them.

There will be diminishing returns.

You wrote

Because to you it’s virtually meaningless other than some weird nostalgia

responding to my comment. I didn’t take any side, let alone argued from with nostalgia

Can you not put words into my mouth?

Nobody knows what a “gimp” is supposed to be.

How is arguing for one side of the issue “not seeing the value of anyone else’s opinion”.

Yeah, these people never do their research. Its very easy to find the discussions and reasoning the devs had at the time.

That especially disqualifies the conspiracy idiots who come up with myths about Red Hat or Poettering or Microsoft or so puppeteering Linux into its dooooom

Nah, the issue is accidental corruption, different parsers doing things differently, stuff like that. Happens often with “mostly text but actually some structured data also” formats, doesn’t happen with formats that have well specified framing.

Because most people prefer it. Again: having a minority taste doesn’t mean you’re oppressed when there’s an option to have what you want.

Read. I’m saying that you lied, not that your preferences are bad.

Systemd doesn’t force you to use binlogs.

Can you add more fields? Is there no ambiguity in context switching? No breakage around whitespace?

If so, sure, that’s fine then.

WTF. Saying “it uses binlogs” as if that wasn’t a choice is just a lie. I called it out. Deal with it.

Right, that happened to me too.

And it’s a problem 100% unrelated to systemd, so I wouldn’t count it here.

That old load of bullshit again. You could swap out the logs if you want a shittier, less searchable (but text based) logging system. The rest can be countered in a similarly conclusive way, and has been repeatedly in the last decade or so.

Inform yourself before copy-pasting misinformation and misleading propaganda.

The KDE screenshot application is super nice though, what does flameshot have that it doesn’t?

I really like rolling release. So much better to deal with updates one-by-one than in a giant batch every half year or so.

As said: installing the LTS kernel also works, I think.

And you wouldn’t use Arch for servers, you want something stable (as in “rarely changing”) there.

I agree that it’s be useful, and I think you can just install e.g. the LTS kernel next to the regular one.

But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.

Case in point: I dimensioned the EFI partition too small, so at some point, me using the zen kernel (which comes with a backup kernel image) messed things up and I couldn’t boot a half-written kernel.

then I

1. created and booted a live USB stick,
2. Mounted my / and /boot partitions manually into /mnt/root/ and /mnt/root/boot
3. Bind-mounted the live system’s /dev and /proc into /mnt/root/{dev,proc}
4. chrooted into /mnt/root (resulting in an environment using /dev and /proc from the live system and the rest from my system),
5. Used regular package manager commands to uninstall the zen kernel and install the regular one, and finally
6. rebooted into the now working system.

It’s not crazy, it doesn’t take long, you just need to know how the system works. Upside is that nothing ever breaks permanently, everything is fixable (except hardware failure)

The reason there’s no version in the filename is simply that Arch just doesn’t keep old kernels around.

The vmlinuz-linux just gets replaced whenever you update the linux package and the old one is deleted immediately.

Oh yeah I have to deal with software that noticeably changes multiple times per decade! Spoooooky!

Is that some meme? My system has been rock solid for years.