Email or username:

Password:

Forgot your password?
24 posts total
Lennart Poettering

We recently added a new document to the systemd website focussing on one specific facet of the service manager: the fdstore. A concept that people should really use more to facilitate "seamless" service restarts and various other things. Please have a look:

systemd.io/FILE_DESCRIPTOR_STO

Lennart Poettering

Here's a fun new feature we are working on in systemd: userspace-only reboot. In order to reduce grey-out times on image-based OS updates to next to nothing we are making a reboot happen where kernel stays as it is, but userspace shuts down as usual, then possibly transitions into a new rootfs, and starts up again with an initial transaction as it would on a classic system boot. During the transition selected services can pass along their fds and listening sockets, to pass "live" resources…

Lennart Poettering

…from the old system to the new system. This means: super-fast switching from one OS version to the next, with all service code restarted cleanly and comprehensively, but with selected resources passed through untouched, so that they can continue to operate. And it wasn't even that hard to implement: github.com/systemd/systemd/pul

Or in other words: let's not wait for hardware, firmware, boot loader, kernel, initrd to reinitialize on a reboot, let's just focus on userspace alone.

Lennart Poettering

So, we are now living in a world where people generate feature requests based on random ideas AI might have? → github.com/systemd/systemd/iss

And I thought AI was supposed to reduce the workload on humans, not add more on top!

Show previous comments
翠星石
@pid_eins >random ideas AI might have?
The "AI" didn't have the idea, it's just regurgitating a systemd related idea someone wrote about in the text dataset.

The "AI" things are solely dedicated to making things even more proprietary, so more workload on humans pretty much.



Welcome to the *fed*iverse Lennart, we have free software and ですぅ。
@pid_eins >random ideas AI might have?
The "AI" didn't have the idea, it's just regurgitating a systemd related idea someone wrote about in the text dataset.

suiseisekiblinynuts.png
Latte macchiato :blobcoffee: :ablobcat_longlong:

@pid_eins@mastodon.social I especially love how chatgpt just made up some random shit because doing it properly would apparently have been too much work

Lennart Poettering

PSA for C devs: if your library exposes a function that takes a pointer, and you add a "const" to that pointer later on, then yes, that's an API break. Why? Because the prototype of the function changed enough so that anyone taking a pointer of your function won't be able to assign it to the variable they intend to store it in. Yes, C API compat is hard. (libbpf, I am looking at you 👀👀👀, btw)

Show previous comments
Marc-Antoine Perennou

@pid_eins is it considered less critical if it’s provided with a typedef of the fn signature and the typedef gets updated too?

Toke Høiland-Jørgensen
@pid_eins Well, libbpf has always had an... interesting... approach to backwards compatibility. It's supposed to be better going forward, now that it's reached v1.0. I guess time will tell...
Simon Ser

@pid_eins I've just done that with the Pixman API, and honestly, I don't care. Use an explicit cast if you do.

Go Up