LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-26-2014, 03:15 PM   #316
enorbet
Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware 14 is Main OpSys on Main PC, 2ndary are OpenSuSe 13 and SolydK
Posts: 693

Rep: Reputation: 296Reputation: 296Reputation: 296

Quote:
Originally Posted by ruario View Post
@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.
 
Old 02-28-2014, 01:28 AM   #317
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,564
Blog Entries: 3

Rep: Reputation: 218Reputation: 218Reputation: 218
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.
 
Old 03-01-2014, 07:17 AM   #318
bartgymnast
Member
 
Registered: Feb 2003
Location: Lelystad, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 258

Original Poster
Rep: Reputation: 87
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.
 
2 members found this post helpful.
Old 03-16-2014, 09:58 PM   #319
mattyslim
LQ Newbie
 
Registered: Mar 2014
Location: FL
Distribution: Slackware,Debian
Posts: 1

Rep: Reputation: Disabled
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.
 
Old 03-17-2014, 12:47 AM   #320
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,214
Blog Entries: 15

Rep: Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831
Has the Linux Foundation developers even implemented kdbus yet?
 
Old 03-17-2014, 01:45 AM   #321
bartgymnast
Member
 
Registered: Feb 2003
Location: Lelystad, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 258

Original Poster
Rep: Reputation: 87
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)
 
Old 03-17-2014, 03:36 PM   #322
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,214
Blog Entries: 15

Rep: Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831
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?
 
Old 06-21-2014, 01:18 PM   #323
bartgymnast
Member
 
Registered: Feb 2003
Location: Lelystad, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 258

Original Poster
Rep: Reputation: 87
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)
 
Old 06-21-2014, 02:08 PM   #324
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,214
Blog Entries: 15

Rep: Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831
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?
 
Old 06-21-2014, 05:25 PM   #325
bartgymnast
Member
 
Registered: Feb 2003
Location: Lelystad, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 258

Original Poster
Rep: Reputation: 87
Quote:
Originally Posted by ReaperX7 View Post
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.
 
Old 06-21-2014, 09:13 PM   #326
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 2,205

Rep: Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569
Quote:
Originally Posted by bartgymnast View Post
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.

Last edited by jpollard; 06-21-2014 at 09:15 PM.
 
Old 06-22-2014, 12:20 AM   #327
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,214
Blog Entries: 15

Rep: Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831Reputation: 831
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.
 
Old 06-22-2014, 04:09 AM   #328
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 2,205

Rep: Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569
Quote:
Originally Posted by ReaperX7 View Post
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).

Last edited by jpollard; 06-22-2014 at 04:12 AM.
 
Old 06-22-2014, 09:26 AM   #329
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 87

Rep: Reputation: Disabled
Quote:
Originally Posted by jpollard View Post
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

Last edited by aaditya; 06-22-2014 at 09:33 AM.
 
Old 06-22-2014, 03:24 PM   #330
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 2,205

Rep: Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569
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...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 09:26 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration