| 1 |
Hi, |
| 2 |
|
| 3 |
Let's cut the FUD. |
| 4 |
|
| 5 |
On Tue, 2012-08-07 at 08:47 -0400, Sylvain Alain wrote: |
| 6 |
> 1. The SystemD and Udev projetcs are merged now, so what is the impact |
| 7 |
> on the Gentoo on a short term period ? |
| 8 |
|
| 9 |
Only the build system is merged, they're still separate binaries. |
| 10 |
|
| 11 |
> 2. I saw on some lists that Gnome/Kde and Xfce plan to use some |
| 12 |
> SystemD API, so does it means that we will need to install SystemD |
| 13 |
> aside of OpenRC ? |
| 14 |
|
| 15 |
|
| 16 |
The APIs that GNOME is using from systemd are simple, well designed and |
| 17 |
well documented D-Bus APIs [1][2][3]. They are implemented by simple |
| 18 |
binaries separate from the core systemd. Legacy init systems can just |
| 19 |
re-use them as-is. |
| 20 |
|
| 21 |
Also, systemd includes logind, which replaces ConsoleKit with a much |
| 22 |
better design. |
| 23 |
|
| 24 |
> 4. Finally, is there any reason why Gnome/Kde/Xfce wants to add deps |
| 25 |
related to SystemD ? I don't understand why these desktops want to |
| 26 |
depend on a specific Sysint.... |
| 27 |
|
| 28 |
Old versions of GNOME (and KDE, XFCE, etc) had to have distro-specific |
| 29 |
code for a bunch of things, such as changing the timezone, the system |
| 30 |
locale or the hostname. Because these things are in separate places in |
| 31 |
every distribution for historical reason. So every desktop had to |
| 32 |
re-implement these things for every distribution, making a lot of |
| 33 |
duplicated code. The goal is to have a single set of tools using a |
| 34 |
common D-Bus API that you only have to implement once per distribution |
| 35 |
and that every desktop can use. |
| 36 |
|
| 37 |
> 3. In a long term vision, can OpenRC still exist on a Gentoo |
| 38 |
> box(OpenRC might be able to boot the box then give the control to |
| 39 |
> SystemD/Udev for the rest of the boot process) or we will need to |
| 40 |
> migrate to SystemD to be able to use Gnome/Kde or Xfce ? |
| 41 |
|
| 42 |
I expect that in the not so long term, systemd will become an essential |
| 43 |
user-space component of desktop Linux, just like crond, syslog, dbus, |
| 44 |
udev or glibc. Sharing that code just makes sense, that allows |
| 45 |
distributions to focus on their strength instead of having to maintain a |
| 46 |
nightmare of shell scripts. Sure you can do a Android and write your own |
| 47 |
crappier version, but that doesn't gain you anything. |
| 48 |
|
| 49 |
Refs: |
| 50 |
[1] http://www.freedesktop.org/wiki/Software/systemd/hostnamed |
| 51 |
[2] http://www.freedesktop.org/wiki/Software/systemd/timedated |
| 52 |
[3] http://www.freedesktop.org/wiki/Software/systemd/localed |
| 53 |
[4] http://www.freedesktop.org/wiki/Software/systemd/logind |
| 54 |
|
| 55 |
-- |
| 56 |
Olivier Crête |
| 57 |
tester@g.o |
| 58 |
Gentoo Developer |
Archives