What If .........Slack needs Systemd (Slackbuilds)

enorbet · 02-26-2014, 03:15 PM

Quote:

Originally Posted by ruario

@bartgymnast: Thanks for your continued work on this despite so much negativity. I must admit I have not found the time to play with your SlackBuilds yet but making it easier for others to test this is something I greatly appreciate!

^^ THIS! As one who has taken part in the wailing and gnashing of teeth in threads regarding the philosophy and end-game of systemd, I have to say this is the most "rubber meets the road", useful, and interesting for longterm of them all. Keep up the good work Bartgymnast! Kudos.

Drakeo · 02-28-2014, 01:28 AM

the wonderful thing about OpenSource is it is open. We can see what the Dev's are doing and working on. http://comments.gmane.org/gmane.comp...md.devel/16849
struggles can be helped or thrown away by the community. Stability is the key.

bartgymnast · 03-01-2014, 07:17 AM

After some testing with 209 and 210 I decided to wait a bit more as they are still in the process of including the online state notification of systemd-networkd.
for the kdbus implementation a newer kernel is needed, which is not available on 14.1

as soon as I have new news, I will update it here.

mattyslim · 03-16-2014, 09:58 PM

Hello barygymnaast, Thank you.. I had been wanting to learn this stuff for a while, I am running your slackbuilds of systemd on slackware-current x86 fine. I did it without pam, I had no love from networkmanager and switched back to inet1 and am fine. This is on a lenovo T61, I also had to blacklist mei_me as I had problems with this module on other live systemd distros I tried in the past. Keep up the great work! I even used your slim.service file and found xwmconfig was able to switch me from xfce to kde without a hitch.

ReaperX7 · 03-17-2014, 12:47 AM

Has the Linux Foundation developers even implemented kdbus yet?

bartgymnast · 03-17-2014, 01:45 AM

Hi ReaperX7,

It depends on how you interpreter your line.

1. Q. Is the kdbus code in the kernel yet?
A. NO

2. Q. Is a Linux Foundation Developer working on the project ?
A. Yes (Greg Kroah-Hartman is 1 of the main developers of kdbus)

ReaperX7 · 03-17-2014, 03:36 PM

Thanks Bart, and yes it was Question #1 specifically.

Have you seen, if there is, a time table for it's official deployment, or is that still in speculation?

bartgymnast · 06-21-2014, 01:18 PM

Hi All,

I just want to update everyone with the new status of the project.
I moved the project to sourceforge.

https://sourceforge.net/projects/systemd.dlackware.p/

there are 2 groups for building systemd for slackware
-min: which are minimal required packages
-all: rebuilds of existing slackware packages to convert/work with systemd

Currently I am working on having KDE work with systemd-logind

We intend to make a Gnome based on systemd and Slackbuilds

http://www.dlackware.com (work in progress)

ReaperX7 · 06-21-2014, 02:08 PM

Bart have you found any possible way to install only the init system and udev without journald or is that as minimal as it can get?

bartgymnast · 06-21-2014, 05:25 PM

Quote:

Originally Posted by ReaperX7

Bart have you found any possible way to install only the init system and udev without journald or is that as minimal as it can get?

I have not tried to install it without journald.

jpollard · 06-21-2014, 09:13 PM

Quote:

Originally Posted by bartgymnast

I have not tried to install it without journald.

Even without journald, you still need dbus.

As I understand it, I don't think you can do without journald. Any system logs to be generated are done by systemd - it receives the stdout/stderr and then uses dbus to log them to journald.

ReaperX7 · 06-22-2014, 12:20 AM

If you could find a way to isolate init and udev without dbus you could kill possibly kill journald off and have the only required parts.

jpollard · 06-22-2014, 04:09 AM

Quote:

Originally Posted by ReaperX7

If you could find a way to isolate init and udev without dbus you could kill possibly kill journald off and have the only required parts.

Ummm. I've been using Fedora... and if you remove dbus, the system doesn't run...

Systemd uses dbus to communicate with udev, and from udev back to systemd. And it uses it to communicate with every other "non-forking" service such as NetworkManager for the same reason. There is no other way for these modified services to tell systemd that things are "ready".

I also think dbus is integral to the systemd ability to monitor processes, and stop/restart other processes based on the state reported (via dbus).

aaditya · 06-22-2014, 09:26 AM

Quote:

Originally Posted by jpollard

Ummm. I've been using Fedora... and if you remove dbus, the system doesn't run...

Systemd uses dbus to communicate with udev, and from udev back to systemd. And it uses it to communicate with every other "non-forking" service such as NetworkManager for the same reason. There is no other way for these modified services to tell systemd that things are "ready".

I also think dbus is integral to the systemd ability to monitor processes, and stop/restart other processes based on the state reported (via dbus).

I think thats right, if one removes systemd as udev provider in favour of eudev, some packages may need to be recompiled with the --disable-systemd option.

Some clues: https://aur.archlinux.org/packages/d...stemd/PKGBUILD
https://aur.archlinux.org/packages/?O=0&K=nosystemd

jpollard · 06-22-2014, 03:24 PM

The startup configurations will also have to be changed... as systemd would no longer know when they are ready for use (have to change them all to "forking").

And that may require "readjusting" of the network of services...