News for hackers. Stuff that matters.
Re:Varlink – IPC to replace D-Bus gradually in systemd by quotemstr on Sunday September 29, 2024 @11:21PM (#41693235)
Christ almighty, I have seldom seen a technical proposal as bad as this one. I want off Mr. Poettering's wild ride. No 64 bit integers? No file descriptor transport? No message sequence numbers? Just cut it out already. Dbus doesn't do something? Extend dbus. Don't make some other random and worse things.
Re:Varlink – IPC to replace D-Bus gradually in systemd by eviks on Sunday September 29, 2024 @11:51PM (#41693377)
> Extend dbus.

How would you address the issue of dbus unavailability in early boot listed in the presentation via extension?

Re:Varlink – IPC to replace D-Bus gradually in systemd by ahartmetz on Monday September 30, 2024 @06:11AM (#41695449)
How have we survived without such a feature up to now?

It is a common occurrence that whatever Lennart comes up with fulfills several, erm, novel requirements while not fulfilling some old ones that aren't even mentioned. The parallels to binary logging are there. "Fancy" features that no one asked for - check. Simplicity and thoughtful use of existing functionality (the "full exploitation" principle of the Unix design philosophy) - nope.

Re:Varlink – IPC to replace D-Bus gradually in systemd by btreecat on Monday September 30, 2024 @08:39AM (#41696476)
>No 64 bit integers? No file descriptor transport? No message sequence numbers?

Are these required or useful in this context?

>Dbus doesn't do something? Extend dbus.

How are you so certain that this is the best use of resources, do you have personal XP in the problem domain?

> Don't make some other random and worse things.

How did you determine that these changes are "worse" or "random?"

Re:Varlink – IPC to replace D-Bus gradually in systemd by Netch on Monday October 07, 2024 @03:47AM (#41763685)
> Are these required or useful in this context?

At least 64-bit numbers are crucial in any system context.

Re:Varlink – IPC to replace D-Bus gradually in systemd by btreecat on Monday October 07, 2024 @08:02AM (#41765152)
You're saying you can't think of one context where a trade of between largest supported int value vs total bytes of the message is a reasonable one?

I would encourage you to work with either data at scale or embedded hardware for a fresh perspective.

Re:Varlink – IPC to replace D-Bus gradually in systemd by Netch on Tuesday October 08, 2024 @01:15AM (#41774043)
> You're saying you can't think of one context where a trade of between largest supported int value vs total bytes of the message is a reasonable one?

Seems you have pretty misread me. Well, "any system" (where systemd is useful in principle) "context" and not "any" "system context", if I correctly guessed where is your point.

As the whole protocol shall be supporting Linux, in a fully universal manner, support of 64-bit values for pointers (even in crash reports), file offsets (including 32-bit systems), etc. is a must.

> I would encourage you to work with either data at scale or embedded hardware for a fresh perspective.

Thanks, I got used to, different platforms (like ARM) including 32- and 64-bit ones. Also ancient beasts like 6502, PDP-11, and even S/360 (Soviet clones) at good old school times. Beg your pardon, no experience with 8051, 8042, ESP8266 and so on, but they arenʼt in question here. Again, the very topic is full-scale Unix context - more so, closer to desktop/laptop/server, which are nearly always 64-bit now (mainstream distribution vendors deliberately abandoned 32-bit versions for these domains a few years ago), so I donʼt expect much digression.

Re:Varlink – IPC to replace D-Bus gradually in systemd by foul on Monday September 30, 2024 @08:42AM (#41696495)
In json, with their baked in schema, I think that someone may encode a DEC64[1] number as... string, array, or whatever.

[1] https://www.crockford.com/dec64.html