| 1 |
Alexis Ballier schrieb: |
| 2 |
> I also fail to see how udev using a new linux ipc would make it require |
| 3 |
> systemd. Quoting Lennart: |
| 4 |
> "You need the userspace code to set up the bus and its policy and handle |
| 5 |
> activation. That's not a trivial task. For us, that's what sytemd does |
| 6 |
> in PID 1. You'd need to come up with an alternative for that." |
| 7 |
> |
| 8 |
> If it's just that, it's not limited to udev, but anything using |
| 9 |
> kdbus/bus1, and would mean openrc/${favorite init system} will have to |
| 10 |
> do the same thing anyway. But again, almost 2 years is extremely |
| 11 |
> old considering all the flux that has been around kbus. |
| 12 |
|
| 13 |
OpenRC itself can for now just ignore kdbus, bus1, or whatever kernel |
| 14 |
IPC system comes next. But if upstream udev makes use of the systemd |
| 15 |
userspace interface to the kernel IPC system, then OpenRC would have to |
| 16 |
implement the same interface in order to have working udev. |
| 17 |
|
| 18 |
Also given the close relationship between systemd and udev, there is no |
| 19 |
guarantee that supporting other users of kdbus/bus1 will make udev |
| 20 |
automagically work. As these two are released together, there is no |
| 21 |
reason to have a stable, public API between them. |
| 22 |
|
| 23 |
|
| 24 |
Best regards, |
| 25 |
Chí-Thanh Christopher Nguyễn |
Archives