Couldn't resist.

You sir, are a true subgenius!

Do I need to remove ConsoleKit and udev or any other packages?
I will test you systemd packages.

You'd be best to wait for an official package if one ever comes. Someone already attempted this and the were left with a mess. You'd basically have to rebuilt about 75% of the core system in the /a directory and then bring in other software that isn't in /a as well like dbus and glib as well as other non-essential packages.

Go read the LinuxFromScratch 7.3 systemd book for what all would have to be done. And you'll notice that LFS 7.4 and the SVN books don't have it either.

ReaperX7, can you go somewhere else.
Go read first post.

This post is to test, improve slackbuilds for optimizing systemd on slackware.
its not for telling people what they cant do, its their own discision.

and tuxbg, you dont have to delete ConsoleKit, however you will need to replace udev

upgradepkg udev%systemd

Sorry but selling snake oil doesn't sit well with me. You can do what you please, but if you are so hell bent on making a systemd Slackware, then go make a fork. Slackbuilds are one thing but to actually use systemd it requires rebuilding the core of Slackware. You don't just make a Slackbuild of systemd. You have to rebuild Slackware at the core.

Up till now all you preached is all what Poettering has said, but you repeatedly have failed to even acknowledge that all that you've preached systemd will innovate, improvise, and improve already has been implemented without systemd but using existing toolkits and proper scripting, setup, and administration techniques any admin worth their salt would know, and all less taxing on the system.

You seem to fail to realize that systemd is NOT welcome here especially by those of us who understand Linux and what systemd aims to do to Linux that is not needed nor required.

ReaperX7, I didnt know you talked for every single soul here.
you can talk for yourself, but dont talk for others, if they have an opinion they can express that themself.
and there are already some forums post about systemd where that is being done.
and also there you see that there are a few person that want to test and help testing.

Reaper, you don't speak for me, or anyone else here. I don't like systemd either, but if the guy wants to have a topic to discuss with like minded people his attempt to jimmy systemd into a slackware install then he should be allowed to do so without people coming in and disrupting his thread.

Now, if he ever suggests that systemd be adopted by the official Slackware release then I'll grab my torch and pitchfork and be right there beside you, but until then, leave the guys thread alone! I was actually quite curious to see how it progressed.

Testing is one thing but you can't test the system without a complete rebuild first. You'd basically have to fork the system out.

Again you are creating a presumption that all of what you claim will happen is 100% guaranteed. You really should take heed of what AlienBOB told you. No projects have fully committed to systemd and most have left it optional. If those that do make it a had dependency do so, they might as well cut their own throats as not all distributions will adopt systemd like Lennart wants to dream about. Linux and every other flavour of UNIX out there will use what they've always used.

And I don't need to speak for everyone here. Go do a thorough search of systemd topics here and read first.

You really should just fork Slackware as a whole if you want this so badly.

Yes, this. I'm no fan of systemd, but this flame is unwarranted. Our forums should not be a firing ground.

Reaper,

Can you tell me which packages apart from util-linux and dbus needs to be recompiled according to LFS book.

Perhaps now is the time to take GazL's advice and tone it down a notch and just let the OP get on with it. You don't need to keep telling him stuff like this, in such inflammatory ways.

The point of this thread as far as I can tell is to say, "Here are some SlackBuilds to get systemd up and running. How do they work for you? What have I missed?". Let's just stick to that topic.

Working systemd SlackBuilds are handy for three reasons:

1. So that people can try it out and then make informed opinions in the other threads.
2. As a pre-testing ground just in case systemd ever does come to Slack
3. For those who might actually want a Slack-systemd hybrid. Yes, shock, horror, they may actually exist! :p

If none of those hold water for you, just ignore the thread. If others hold your opnion they will ignore it as well and the thread will die a natural death. You don't need to make it your mission to be the top poster in every single systemd thread. I'm pretty certain people already have a vague idea about your opinion on systemd. :D

As a side note, I don't really care about systemd either but I am very grateful to the OP for actually putting the effort in for those who might want to use it or at least test it.

@ruario

thank you

I have very big problem with systemd.Systemd not mount my /usr .My /usr is on separete directory.Systemd not run dhcpcd.
Also when i type my user name or root i've got this

As far as I know, SystemD does not support /usr being a separate filesystem unless you yourself ensure that it gets mounted before SystemD starts (i.e. you need to mount it in the initrd). See http://freedesktop.org/wiki/Software...usr-is-broken/ for a piece of arrogance barfed up by our favourite Slackware destroyer.

Eric